Mudlet trigger examples5/30/2023 ![]() Once MSDP is enabled, you will need to reconnect to the game so that Mudlet can inform the server it is ready to receive MSDP information. Mudlet can be configured to use MSDP by clicking on the Settings button (or Options->Preferences in the menu, or p). MSDP (Mud Server Data Protocol) is a protocol for game servers to communicate information with game clients in a separate channel from the one which carries all of the text that makes up the game itself. This prevents script A from disabling modules that script B may still be using.Ī good GMCP tutorial that walks you through receiving and sending GMCP data is available here - take a read! If you disable it, it will not be disabled with the server until every user of that module has disabled it. The main difference being that the module will be turned on as soon as you enable it if it is not already enabled. disableModule ( "MyUser", "Module.Name" ) The GMCP data received will be stored in the corresponding field of the gmcp table, which your function will read from. Lastly, define the function - either in this or any other script - and you'll be done. Then, add the GMCP event you'd like the function to fire on under the registered event handlers left. To "trigger" on GMCP messages, you'll need to create an event handler - Mudlet will call it for you whenever relevant GMCP data is received.Īs an example, create a new script and give it a name of the function you'd like to be called when the relevant GMCP message is received. ![]() When working with GMCP on IRE games, this GMCP reference is a useful tool. Enabling the Debug window will show you GMCP events as they are coming in, and to get an idea of what information is currently stored, hit the Statistics button. Generic Mud Communication Protocol, or GMCP, is a protocol for game servers to communicate information with game clients in a separate channel from the one which carries all of the text that makes up the game itself. Mudlet supports CHARSET, GMCP, MSSP, MSP, ATCP, Aardwolfs 102, MSDP, and the MXP Protocol.ĬHARSET, MXP, MSSP, MSP, GMCP and 102 are enabled by default, MSDP can be enabled in settings. 1.10 Adding support for a telnet protocol.1.8.2.2 Advanced example of receiving MXP Data (Server owners).1.8.2.1 Simple example of receiving MXP Data (Server owners).While you can use the original, this should have some added bonuses.Īlso, while it might be tempting to edit this to no longer connect to e621 if the file already exists on your computer locally, it can only determine if you have the file if it connects in the first place. While the original trigger listed before this one functions and is stable, it is lacking a few features (such as multi-line link monitoring). Make the display window actually look nice.SendSequence(0.1, "recall", 3, "o", "b") - recall takes a long time to process, so we wait 3s to let the server process it before moving on the map Recall to Zephyr studies (where you turn in the behavior bounty) as a Quetzalcoatl dedicant: numbers are interpreted as additional wait time : a nested list of commands string to send to the server. interval: the default time to wait between each command, be careful as some commands make the server die more that others.Offset = SendSequence(interval, offset + interval, unpack(tab)) Must be saved in your mudlet "Scripts" Profile Useful to go back to lobby from your home point or to macro together one of your daily routine 5 Alternative e621 Trigger ImplementationĪ LUA function to repeat a series of memorized commands.
0 Comments
Leave a Reply. |