Dt192 at 04:49, 10 January 2024

2024-01-10T04:49:25Z

Vadi: Remove translate tags that show up in the normal view

2021-11-08T10:40:53Z

Remove translate tags that show up in the normal view

Vadi: Created page with " Here you can find a long list of all possible Lua functions and programming interfaces (API) that Mudlet offers. Due to the integrated Lua, you can also..."

2021-11-08T10:37:52Z

Created page with "<translate>  Here you can find a long list of all possible Lua functions and programming interfaces (API) that Mudlet offers. Due to the integrated Lua, you can also..."

New page

<translate>

Here you can find a long list of all possible Lua functions and programming interfaces (API) that Mudlet offers. Due to the integrated Lua, you can also use all regular Lua functions. In the following page, we will explain the usage, expected behavior and examples for the functions added in Mudlet.

= Global variables = 
Mudlet defines several global Lua variables that are accessible from anywhere.


{| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | <code>command</code>
|colspan="4" | This variable holds the current user command, i.e. unchanged by any aliases or triggers. This is typically used in alias scripts.
|-
|colspan="2" | <code>line</code>
|colspan="4" | This variable holds the content of the current line as being processed by the trigger engine. The engine runs all triggers on each line as it arrives from the game.
|-
|colspan="2" | <code>matches[n]</code>
|colspan="4" | This Lua table is being used by Mudlet in the context of triggers that use Perl regular expressions.
matches[1] holds the entire match, matches[2] holds the first capture group, matches[n] holds the nth-1 capture group.
If the Perl trigger indicated 'match all' (same effect as the Perl /g switch) to evaluate all possible matches of the given regex within the current line, matches[n+1] will hold the second entire match, matches[n+2] the first capture group of the second match and matches[n+m]
the m-th capture group of the second match.

Since Mudlet 4.11+ it will contain named capturing groups, apart from numeric group matches (named groups count as numeric as well). Each can be access under element with key corresponding to group name.
Eg. if you capture group with name <code>target</code> you can access it via <code>matches["target"]</code> or simply <code>matches.target</code>. You can use <code>mudlet.supports.namedGroups</code> flag to determine whether named groups are supported.
|-
|colspan="2" | <code>multimatches[n][m]</code>
|colspan="4" | This table is being used by Mudlet in the context of multiline triggers that use Perl regular expression. It holds the table matches[n] as described above for each Perl regular expression based condition of the multiline trigger. multimatches[5][4] may hold the 3rd capture group of the 5th regex in the multiline trigger. This way you can examine and process all relevant data within a single script.
|-
|colspan="2" | <code>mudlet.translations</code>
|colspan="4" | Contains translations of some common texts (right now, exit directions only) that are helpful to you in Lua scripting, as well as the current language selected for the user interface. - See [[Special:MyLanguage/Manual:Miscellaneous_Functions#translateTable|translateTable()]]
|-
|colspan="2" | <code>mudlet.key</code>
|colspan="4" | Makes your life easier when creating new keybindings via Lua by translating the key name into the number needed - see [[Special:MyLanguage/Manual:Mudlet_Object_Functions#tempKey|tempKey()]].
|-
|colspan="2" | <code>mudlet.keymodifier</code>
|colspan="4" | Same as <code>mudlet.key</code>, but for keyboard modifiers - Ctrl, Alt, etc.
|-
|colspan="2" | <code>mudlet.supports</code>
|colspan="4" | Lists special functionality that the users Mudlet supports - right now, just <code>mudlet.supports.coroutines</code> & <code>mudlet.supports.namedGroups</code> is listed. Use <code>mudlet.supports</code> to conditionally enable functionality as it's available on the users Mudlet.
|-
|colspan="2" | <code>color_table</code>
|colspan="4" | Color definitions used by Geyser, cecho, and many other functions - see [[Special:MyLanguage/Manual:UI_Functions#showColors|showColors()]]. The profile's color preferences are also accessible under the <code>ansi_</code> keys.
|}

There are other variables that hold the game's MUD-protocol data that are global as well - see [[Special:MyLanguage/Manual:Technical_Manual#Supported_Protocols|Supported Protocols]].
</translate>

[[Category:Mudlet Manual]]
[[Category:Mudlet API]]

@@ Line 6: / Line 6: @@
 <!--T:3-->
-{| border="2" cellpadding="4"
+{| border="2" cellpadding="4" id="built-in-lua-variables"
 !colspan="6" | Built-in Lua Variables
 |-

@@ Line 1: / Line 1: @@
 <!--T:1-->
 Here you can find a long list of all possible Lua functions and programming interfaces (API) that Mudlet offers. Due to the integrated Lua, you can also use all regular Lua functions. In the following page, we will explain the usage, expected behavior and examples for the functions added in Mudlet.
@@ Line 48: / Line 47: @@
 There are other variables that hold the game's MUD-protocol data that are global as well - see [[Special:MyLanguage/Manual:Technical_Manual#Supported_Protocols|Supported Protocols]].
 [[Category:Mudlet Manual]]
 [[Category:Mudlet API]]

Manual:Lua Functions Basics - Revision history

Dt192 at 04:49, 10 January 2024

Vadi: Remove translate tags that show up in the normal view

Vadi: Created page with " Here you can find a long list of all possible Lua functions and programming interfaces (API) that Mudlet offers. Due to the integrated Lua, you can also..."