MQ2ClickMaint is a plugin intended to replace the casting part of maintaining clickies. By tracking the wear-off messages paired with the item to recast a buff, it stores which of your items need to be recast. To monitor this, the ${CMaint} TLO is a boolean that returns true if you have buffs needing to be done, and false if not. I repeat, this plugin does *NOT* automatically maintain buffs. In my opinion, coding that into a plugin to cover every situation would be impossible. As such, the intent is that you can use a macro and the ${CMaint} TLO to activate the command when you want to, or activate it on your own to take the place of a "myclicks.mac" type macro that just refreshes your buffs.
- Specific Usage***
--To use MQ2CM, you must set up an INI as specified below. If you need help with this, either I or someone else can surely do so...hopefully some of the testers will be willing to post their own INI files as examples.
-/doclicks
-"/doclicks" - immediately cast every item waiting to be cast. Will not work if you are invis. -"/doclicks rez" - if you have been rezzed and want an instant-clicky to be in your first slot, this is the command for you. Enter it right after you have been rezzed to cast every item but myItem0. Once the RezEffect slot is gone, simply "/doclicks" to cast the remaining buff and have it land in your first slot! -"/doclicks all" - Cast all items, regardless of which items need to be done. This is also useful for casting items that have no wear-off message. The most effective use is to put a shrink rod in the INI with no wear-off message, then add it to your personal list twice. This will cause the wand never to cast itself except when you do /doclicks all.
-/citem
-On entering this command to start adding an item: -Now entering 'add' sequence. The next 10 lines of chat will be saved and echoed back to you as they come. -Once you see the line that is the wear off msg for your item, /citem #, where # is the line number next to it.
-Once you have done this, the plugin will echo the next 10 lines of chat that it sees, with numbers in front of them. To pick the one that corresponds with the correct wear-off msg for your item, first place the item you wish to cast for that buff on your cursor, then:
-"/citem #", where # is replaced with the correct number from the list.
-If the correct message is not found (adding an item in PoK might be difficult, for example), then:
-"/citem no", which will start the plugin over on reading the next 10 messages.
-/cmaint:
/cmaint -> displays this list
/cmaint help -> Displays this list, and explains how to use the commands.
/cmaint list -> Lists all items defined in INI
/cmaint me -> Lists all of the items plugin is tracking for your character.
/cmaint add #|FileItem# -> Add Item<#> from INI to your character's list. Ex: 'add FileItem5' or 'add 5'
/cmaint remove #-> Remove Item<#> from your character's list. Ex: 'remove myItem0'
/cmaint reload -> Reload items in the INI without having to reload the plugin.
- Summary***
-Plugin does *not* automatically click your buffs. -TLO ${CMaint} -- Returns TRUE if you have buffs waiting to be done -"/doclicks" will do all of the buffs you have waiting to be done. -"/doclicks rez" will do all of your buffs but myItem0, in order to allow you to have an instant click to be set in your first slot after a rez. -"/doclicks all" will refresh all of your buffs -"/cmaint" allows users to tweak settings with the plugin, and adjust which items from the INI are included in their list to maintain. -"/cmaint help" for a list of commands for /cmaint and explanations. -"/citem" allows users to add items to the INI from ingame. Once the message has been saved, put the item you want to click on your cursor, then "/citem #" to specify which msg you want. If the msg did not show up, "/citem no" to the msg-searching over.
- INI setup***
The INI (MQ2ClickMaint.ini) must be structured as follows: [code]
[INI Info]
TotalItems=
[Server_PlayerName]
NumItems=
myItem0=FileItem0
myItem1=FileItem5
myItem2=FileItem22
...
[FileItem0]
ItemName=
BuffOffMsg=
[FileItem1]
...
[/code]
-The [INI Info] section's "Total Items" entry must always be up to date. You can have a [b]MAXIMUM[/b] of 50 items stored in the INI. Remember, your total number of items is NOT the highest FileItem# that you have...it is that number +1, since the counting starts at 0. -You can have information for as many players as you want in the INI. -Make sure the the NumItems entry is always accurate. Remember, your total number of items is NOT the highest myItem# that you have...it is that number +1, since the counting starts at 0.