|Thorny 51d96c38ea||4 months ago|
|release||4 months ago|
|src||4 months ago|
|.gitignore||1 year ago|
|README.md||4 months ago|
Multisend has not been rewritten in any meaningful capacity for Ashita4. While the code is hard to read, it should still be functional and compatible with Ashita3 instances running Multisend of the same version for Ashita3. This decision was made to ensure compatibilty during the transition period between Ashita3 and Ashita4. Once Ashita4 has completely replaced Ashita3, Multisend will receive a rewrite as my other plugins have to make the codebase more readable and potentially add new features. At that point, you will no longer be able to use Ashita3 Multisend alongside Ashita4 Multisend.
Multisend is a replacement for servo. No synchronization is needed, just load and go.
Each character receiving or sending data must be on Ashita3 or Ashita4 and have a compatible version of Multisend loaded.
The current version of Multisend is 1.17 for both Ashita3 and Ashita4.
/ms send [command]
Sends a command to all characters.
/ms sendto [character] [command]
/mst [character] [command]
Sends a command to a specific character.
/ms sendgroup [group] [command]
/msg [group] [command]
Sends a command to all characters listed in a group. Groups can be defined in Ashita/Config/MultiSend.xml. See Ashita/docs/multisend/XML Structure file for example.
/ms sendothers [command]
Sends a command to all characters except for the current character.
/ms sendparty [command]
Sends a command to all characters in the current character's party. This includes the current character unless ignoreself is turned on.
/ms sendally [command]
Sends a command to all characters in the current character's alliance. This includes the current character unless ignoreself is turned on.
/ms followmax [#]
Sets a max follow range(in yalms). If follow target is more than this many yalms away, following characters won't move.
-I recommend setting between 30 and 100 to prevent following from trying to use portals.
-Default is 5000, which will be the same behavior as before this setting was added.
/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. Default: OFF.
-Followme can only be enabled by one character. If a second character turns it on, the first character will have it disabled automatically.
/ms follow [on/off]
Enables or disables follow. Any character with follow enabled with follow the player who last activated followme. Default: ON
/ms attemptzone on/off
Enables or disables attempted zoning. When enabled, if the leader zones, the other characters will continue running in the direction they were last running. Default: OFF
-If you are using a home point, survival guide, etc, it will be detected as long as you stand still throughout the process and nobody will run off.
-BUT, if you move after first acting upon the object or sending an uberwarp command, chars may run off.
/ms ignoreself on/off
When enabled, any command that would effect the local character is not executed by the local character. Default: OFF
/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. Default: OFF
Typing this will reload your groups xml.
Typing this will print a list of commands ingame.
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 result in the sending character's data being used.
Using etc.. will result in the receiving character's data being used.
For example, if CharacterA uses /ms sendto CharacterB /ma "Fire IV" [t], then CharacterB will cast Fire IV on CharacterA's target.
However, if CharacterA uses /ms sendto CharacterB /ma "Fire IV" <t>, then CharacterB will cast Fire IV on whatever CharacterB has targeted at the time.