Keepup can also be disabled or enabled for convenience with tf keepup, tn keepup. Keepups job, as the name implies, is to make sure its defences always stay up - if one goes down for any reason, it’ll put it back up. After defup is done, the system will say Ready for combat!, and defup will be done - it’ll care no more about your defences. Remember that you can tell defup to put up different defences in different modes - that is the difference in modes. When you first switch to a defence mode using vdefs, defup will put up all of the defences that are on its list. The process of putting them up is also in two stages: defup and keepup. The system organizes defences around defence modes, in which you can have it put up different defences. Take time to look through the available options and aliases as well to acquaint yourself with the system. That’s about it! Do make sure that you have all the curatives necessary on you and you should be just fine. Make sure you don’t do config prompt none, because the system does need to see your prompt stats! You should also read up on the aeon/retardation curing and practice with the two modes of it in the arena - since it’s something new and you’ll want to at least have a basic idea of what’s going on. To get a better grasp of the system, I’d recommend that you participate in some combat arena events - free-for-alls, wargames, etc - so you’ll have a little bit better idea of what to do when a real fight comes. You can also view what options have you currently set with vconfig and vconfig2 aliases. Do set it back to 0 when you’re alright, though. If you’re lagging a lot, and the system is double-doing actions because of that and etc, you can set the vconfig lag # option to help alleviate that. When you no longer need it, you can do tf ai (having anti-illusion on means the system will at times will do checks on afflictions before curing them this is slower than just curing them right away). To enable anti-illusion in the system, you can do tn ai or tn anti-illusion. You no longer need to pause the system to sit or sleep, the system lets you do that To pause or unpause the system, you can use the pp alias - using it alone will act as a toggle, but you can also do pp on and pp off. This will have the system both recognize the output, and also has the feature of the aliases being usable at any time - the system will do the action asap for you. You want to use the dv alias to have the system diagnose and df to check your defences. Of course, the system won’t cure if it’s paused, but while it is, it’ll still track all afflictions. The system cures any ailments you get for you automatically - nothing needs to be turned on. More fine-grained control of the system.Adding your own restore / dragonheal / shrugging / rage scenarios.Registering custom tags when Svof is ready.Differences to know if coming from vadi-m.RegisterAnonymousEventHandler("", "win.handleCommChannelText")GMCP enable chat code Local text = ansi2decho(win.stripMXP(.text)). RegisterAnonymousEventHandler("sysLoadEvent", "win.createChat")GMCP Chat Hook code Local influenced = filter_dict(function(x) return x.influenced end, influencable)Ĭecho("Influenced ".#influenced." out of ".#influencable." for this room.\n") Local influencable = filter_dict(function(x) return x.influencable end, mmi.roomnpcs) I love this, so I modified it to do what I most often want: give me a numberĬecho("Influenced ".done." out of ".total." for this room.\n") If long then cecho("".v.longname."\n") else cecho(".") endĮndIn this quick little example I clumsily hacked together, you can choose whether you want to see the names of the denizens in the room by passing in "true" - false, or just nothing, will give you the short version. If long then cecho("".v.longname."\n") else cecho("X") endĮlseif v.influencable and not v.influenced then If anyone else is still using the old M
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |