Workaround option to disable Telnet Go-Ahead, in case the game server is not working correctly Workaround option to disable MCCP compression, in case the game server is not working correctly Remove extra linebreaks from output (mostly for IRE servers) Workaround option to use strict UNIX line endings for sending commands This may be a string or an array of strings. Particular option to retrieve - see list below for available ones. Note: It is important to ensure that in Mudlet 4.0.0 and beyond the text data only contains characters that can be encoded in the current Game Server encoding, from 4.2.0 the content is checked that it can successfully be converted from the UTF-8 that the Mudlet Lua subsystem uses internally into that particular encoding and if it cannot the function call will fail and not pass any of the data, this will be significant if the text component contains any characters that are not plain ASCII. true on success, nil and an error message if the text contains characters that cannot be conveyed by the current Game Server encoding.Preventing the automatic conversion can be useful to Mudlet developers testing things, or possibly to those who are creating handlers for Telnet protocols within the Lua subsystem, who need to avoid the transcoding of individual protocol bytes, when they might otherwise be seen as extended ASCII characters.) Returns (available in Mudlet 4.2+) It will then be automatically converted to the currently selected game server encoding. (Encoding could involve using the Lua string character escaping mechanism of \ and a base 10 number for character codes from \1 up to \255 at maximum) Since Mudlet 4.0 it is assumed that the text is UTF-8 encoded. (Before Mudlet 4.0 the text had to be encoded directly in whatever encoding the setting in the preferences was set to. Set this to false, if you need pre-Mudlet 4.0 behavior. dataIsUtf8Encoded (available in Mudlet 4.2+):.This string must be byte encoded in a manner to match the currently selected Server Encoding. String which is sent to the trigger processing system almost as if it came from the game server.
The built-in `echo alias provides this functionality as well. Note: Since Mudlet 3.17.1 the optional second argument to echo the command on screen will be ineffective whilst the game server has negotiated the telnet ECHO option to provide the echoing of text we send to him.ĮxpandAlias ( "t rat" ) - don't echo the command expandAlias ( "t rat", false ) feedTriggers feedTriggers(text) This function will have Mudlet parse the given text as if it came from the game - one great application is trigger testing. local oldmatches = matches before calling expandAlias, since expandAlias will overwrite it after using it again. Note: If you want to be using the matches table after calling expandAlias, you should save it first, as, e.g. See Manual:Functions_vs_expandAlias for details and examples. The recommendation is to use lua functions instead. Note: Using expandAlias is not recommended anymore as it is not very robust and may lead to problems down the road. (optional) If false, the command will not be echoed back in your buffer. Text of the command you want to send to the game. See also: removeFileWatch()Īvailable in Mudlet 4.8 + expandAlias expandAlias(command, ) Runs the command as if it was from the command line - so aliases are checked and if none match, it's sent to the game unchanged. Every change in that file (or directory) will raise sysPathChanged event.
Miscellaneous Functions addFileWatch addFileWatch(path) Adds file watch on directory or file.
0 kommentar(er)
