All translations

Jump to navigation Jump to search

Enter a message name below to show all available translations.

Message

Found 22 translations.

NameCurrent message text
 h Arabic (ar){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h ar-EG (ar-EG){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h German (de){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h Greek (el){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h English (en){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h en-GB (en-GB){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h en-PT (en-PT){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h es-ES (es-ES){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h Finnish (fi){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h French (fr){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h Italian (it){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h Korean (ko){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h Dutch (nl){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h Polish (pl){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h pt-BR (pt-BR){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h pt-PT (pt-PT){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h Russian (ru){| border="2" cellpadding="4"
!colspan="6" | Встроенные переменные Lua
|-
!colspan="2" | Имя переменной
!colspan="4" | Описание
|-
|colspan="2" | command
|colspan="4" | Эта переменная содержит текущую пользовательскую команду. Обычно она используется в скриптах алиасов.
|-
|colspan="2" строка |
|colspan="4" | Эта переменная содержит содержимое текущей строки, которое обрабатывается триггерным движком. Движок запускает все триггеры на каждой строке по мере поступления от MUD.
|-
|colspan="2" | совпадает с[n]
|colspan="4" | Эта таблица Lua используется Mudlet в контексте триггеров, использующих регулярные выражения Perl. 
совпадения[1] содержит полное совпадение, совпадения[2] содержит первую группу захвата, совпадения[n] содержит nth-1 группу захвата.
Если триггер использует переключатель Perl /g для оценки всех возможных совпадений заданного регекса в пределах текущей строки, то matches[n 1] будет удерживать второе полное совпадение, matches[n+2] первой группы захвата второго совпадения и matches[n+m] 
m-я группа захвата второго совпадения.
|-
|colspan="2" | multimatch[n][m]
|colspan="4" | Эта таблица используется Мадлетом в контексте многострочных триггеров, использующих регулярное выражение Perl. Она содержит совпадения таблицы[n] , как описано выше, для каждого регулярного выражения Perl, основанного на условии многострочного триггера. Многострочные триггеры[5][4] могут содержать 3-ю группу захвата 5-го регекса в многострочном триггере. Таким образом, вы можете изучить и обработать все соответствующие данные в рамках одного скрипта. Взгляните на этот пример.
|}
 h sv-SE (sv-SE){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h Turkish (tr){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h yd (yd){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h zh-CN (zh-CN){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
 h zh-TW (zh-TW){| border="2" cellpadding="4"
!colspan="6" | Built-in Lua Variables
|-
!colspan="2" | Variable Name
!colspan="4" | Description
|-
|colspan="2" | comand
|colspan="4" | This variable holds the current user command. This is typically used in alias scripts.
|-
|colspan="2" | line
|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 MUD.
|-
|colspan="2" | matches[n]
|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 trigger uses the Perl style /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.
|-
|colspan="2" | multimatches[n][m]
|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. Have a look at this example.
|}
Retrieved from "https://wiki.mudlet.org/w/Special:Translations"