Lolwutt
7 years ago
1 changed files with 16 additions and 1 deletions
@ -1,3 +1,18 @@
@@ -1,3 +1,18 @@
|
||||
# MultiSend |
||||
|
||||
To be updated later. |
||||
Multisend is a replacement for servo. No synchronization is needed, just load and go. |
||||
Commands are as follows(all can be prefixed with /ms or /multisend): |
||||
|
||||
/ms send [command] - Sends the command to all characters with MultiSend loaded. |
||||
/ms sendto CharName [command] - Sends the command to a specific character, if they have MultiSend loaded. |
||||
/ms sendgroup GroupName [command] - Sends the command to all characters listed in a group. Groups can be defined in Ashita/Config/MultiSend.xml. See XML Structure file for example. |
||||
/ms followme on/off - Enables or disables followme. When followme is enabled, any characters with follow enabled will follow the player who last activated followme. |
||||
/ms follow on/off - Enables or disables follow. Any character with follow enabled with follow the player who last activated followme. |
||||
/ms ignoreself on/off - When enabled, any command that would effect the local character is not executed by the local character. |
||||
/ms debug on/off - When enabled, all received commands are printed to log and any character with followme updated will spam log with position updates. For debug purposes, obviously. |
||||
/ms reload - Will reload groups xml. |
||||
/ms help - Print an ingame reference. |
||||
|
||||
You may use [t] [me] or [p0] [p1] [p2] [p3] [p4] [p5] to replace the <> equivalents, if you wish to resolve them on local character. This will replace them with the appropriate server IDs, allowing the command to resolve on receiving character. |
||||
|
||||
Example: Typing /ms send /ma "Fire IV" [t] will make all characters with multisend loaded cast Fire IV on the character who typed the command's target, rather than their own current target. |
Loading…
Reference in new issue