mudlet-makers team mailing list archive

[Heiko <koehnheiko@xxxxxxxxxxxxxx>]

thanks!

** Changed in: mudlet
       Status: Confirmed => Fix Released

-- 
Documentation error
https://bugs.launchpad.net/bugs/371987
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.

Status in Mudlet the MUD client: Fix Released

Bug description:
I have corrected two errors in the text below. Just paste what I got below over what is in there now.

Using Variables in Mudlet

One of the major design goals in Mudlet was to integrate scripts and variables as seemlessly as possible. The usage of variables in Mudlet is distinctly different from the other major clients, as native Lua scripting has been integrated into Mudlet from the ground up. As scripts are so closely intertwined with the core of Mudlet, variables do not need any special treatment as in other clients. If you define a variable in any given script in Mudlet, be it a trigger, a button, an alias key, an event handler, a free function, etc. It can be used from within any context without any special getVariable() type of function or any special variable symbols, such as @myVar etc.. In Mudlet all variables are native Lua variables. Each session (connection) runs in its own dedicated Lua interpreter. Consequently, all scripts are compiled into the same Lua interpreter and thus their code runs in the same variable space.