Manual:Migrating - Revision history

Kebap: /* From ZMUD */ Link to CMUD

2024-01-18T16:48:06Z

From ZMUD: Link to CMUD

Kebap: /* From Nexus */ Add note on dated instructions

2024-01-18T16:46:11Z

From Nexus: Add note on dated instructions

Vadi: /* From MUSHclient */ mention absolute line numbers

2022-07-09T04:36:36Z

From MUSHclient: mention absolute line numbers

Vadi: /* From MUSHclient */

2022-03-03T15:22:04Z

From MUSHclient

Vadi: /* From MUSHclient */

2021-05-30T07:15:36Z

From MUSHclient

Vadi: /* From CMUD */

2021-02-28T11:44:05Z

From CMUD

OldSchoolMudOS: /* From CMUD */

2020-12-20T06:47:58Z

From CMUD

Vadi: /* From MUSHclient */

2019-11-12T15:26:36Z

From MUSHclient

Vadi: /* From MUSHclient */

2019-11-12T15:22:25Z

From MUSHclient

Kebap: /* From MUSHclient */ transfer MUSH triggers

2019-11-12T08:59:33Z

From MUSHclient: transfer MUSH triggers

← Older revision		Revision as of 16:48, 18 January 2024
Line 693:		Line 693:

	=From zMUD=		=From zMUD=
−	Pretty similar to CMUD - see above.	+	Pretty similar to migrating [[#From CMUD]] - see above.

@@ Line 1: / Line 1: @@
 {{TOC right}}
 =From Nexus=
 '''Trigger patterns'''
-<br>
 Lets start with triggers. For translating Nexus patterns into Mudlet, use the following table below. Make sure to set the pattern type in Mudlet to be perl regex, because the default substring works differently.
 <table border="1" width="100%">
@@ Line 47: / Line 50: @@
 <td>If you just have a pattern with a {<} and {>} and nothing else, copy the pattern over without the {<}{>} and select the exact match pattern type. For example {<}You sit down.{>} in Nexus would become '''You sit down.''' in Mudlet with the pattern type of exact match. This is easier to read and matches way faster!</td>
 </table>
 '''Basic scripting'''
-<br>
 The Nexus way of doing a function is like this: #function stuff it does. In Mudlet, it’s function(stuff it does). Note that if you’d like to give text to a function, you put it inside double or single quotes.
@@ Line 103: / Line 107: @@
 '''Wildcards'''
-<br>
 To use the wildcard variable in Nexus, you’d use $1 for the first match, $2 for the second and so on. In Mudlet, the matches[] table contains the matches - and it starts placing the matches from 2. So the Nexus $1 would be matches[2], $2 would be matches[3].
@@ Line 148: / Line 152: @@
 '''#wait'''
-<br>
 In Nexus, a #wait will freeze the script while it’s executing - such that commands after it are delayed. In Mudlet, we use tempTimer which that works a bit differently - it doesn’t freeze the script, but instead makes it so commands a tempTimer is asked to do will get done in the future.
@@ Line 176: / Line 180: @@
 '''ifs in Mudlet'''
-<br>
 Next are the #if statements. Here’s a table comparing the syntaxes of Nexus and Mudlet:
 <table border="1" width="100%">
@@ Line 309: / Line 313: @@
 </tr>
 </table>
 '''Mudlet equivalents of Nexus functions'''
@@ Line 374: / Line 379: @@
 '''How to call aliases in Mudlet'''
-<br>
 The typical workflow in Nexus is that you’d define the aliases for yourself to use, and also use aliases for system-related things (things like checking if you’d need to eat a herb, etc).

@@ Line 444: / Line 444: @@
 * If you used OnPluginCommandEntered, you can use a "catch all" alias (with a pattern like "^.+") to send all user commands to your script.
 * If you have an existing database you'd like to use and don't want to put it into the profile folder, you can use the standard luaSQL interface to load and use it. Some basic examples can be found at https://keplerproject.github.io/luasql/examples.html
 '''Converting MUSHclient triggers into Mudlet triggers'''

@@ Line 439: / Line 439: @@
 * While MUSHclient uses [https://www.gammon.com.au/scripts/doc.php?function=AnsiNote AnsiNote] to write colorful text, Mudlet offers different ways as well: [[Manual:Lua Functions#cecho|cecho()]] works with the name of a color. You can find lots of predefined colors with [[Manual:Lua Functions#showColors|showColors()]]. You can also style foreground and background seperately with [[Manual:Lua Functions#fg|fg()]] and [[Manual:Lua Functions#bg|bg()]]. To keep your original ANSI colors, use [[Manual:Lua Functions#ansi2decho|ansi2decho()]]. If you need more colors, [[Manual:Lua Functions#decho|decho()]] will take rgb numbers, [[Manual:Lua Functions#hecho|hecho()]] uses hex codes.
 * Mudlet does not offer 'GetConnectDuration()' but you could create a script to connect to the [[Manual:Event_Engine#sysConnectionEvent|connection event]] (and maybe sysDisconnectionEvent) and in that function [[Manual:Mudlet_Object_Functions#createStopWatch|start a stopwatch]] to keep count of how long you've been connected for. See [[Manual:Event Engine]] on how to use events in Mudlet.
-* Mudlet does not have lpeg built-in but you can include the lpeg library installed on your system in your lua code. On Windows, you can choose to put the lpeg.dll file into Mudlet's install folder if that's simpler for you.
+* Mudlet does not have lpeg built-in but you can include the lpeg library installed on your system in your lua code. On Windows, you can choose to put the lpeg.dll file into Mudlet's install folder. On macOS that is not possible due to restrictions placed by Apple.
 * If you used OnPluginPartialLine to match "partial lines" such as prompts, please note that any type of Mudlet triggers should work with such lines so you can just use them for your purpose. For prompts specifically, try tempPromptTrigger.
 * If you used OnPluginTick, you can use a GUI timer in Mudlet for essentially the same functionality.

@@ Line 438: / Line 438: @@
    <syntaxhighlight lang="lua">send("my text", false)</syntaxhighlight>
 * While MUSHclient uses [https://www.gammon.com.au/scripts/doc.php?function=AnsiNote AnsiNote] to write colorful text, Mudlet offers different ways as well: [[Manual:Lua Functions#cecho|cecho()]] works with the name of a color. You can find lots of predefined colors with [[Manual:Lua Functions#showColors|showColors()]]. You can also style foreground and background seperately with [[Manual:Lua Functions#fg|fg()]] and [[Manual:Lua Functions#bg|bg()]]. To keep your original ANSI colors, use [[Manual:Lua Functions#ansi2decho|ansi2decho()]]. If you need more colors, [[Manual:Lua Functions#decho|decho()]] will take rgb numbers, [[Manual:Lua Functions#hecho|hecho()]] uses hex codes.
-* Mudlet does not offer 'GetConnectDuration()' or 'isConnected' but you could create a script to connect to the [[Manual:Event_Engine#sysConnectionEvent|connection event]] (and maybe sysDisconnectionEvent) and in that function [[Manual:Mudlet_Object_Functions#createStopWatch|start a stopwatch]] to keep count of how long you've been connected for. See [[Manual:Event Engine]] on how to use events in Mudlet.
+* Mudlet does not offer 'GetConnectDuration()' but you could create a script to connect to the [[Manual:Event_Engine#sysConnectionEvent|connection event]] (and maybe sysDisconnectionEvent) and in that function [[Manual:Mudlet_Object_Functions#createStopWatch|start a stopwatch]] to keep count of how long you've been connected for. See [[Manual:Event Engine]] on how to use events in Mudlet.
 * Mudlet does not have lpeg built-in but you can include the lpeg library installed on your system in your lua code. On Windows, you can choose to put the lpeg.dll file into Mudlet's install folder if that's simpler for you.
 * If you used OnPluginPartialLine to match "partial lines" such as prompts, please note that any type of Mudlet triggers should work with such lines so you can just use them for your purpose. For prompts specifically, try tempPromptTrigger.

@@ Line 682: / Line 682: @@
 </syntaxhighlight>
 =From zMUD=
 Pretty similar to CMUD - see above.

@@ Line 669: / Line 669: @@
 </syntaxhighlight>
-'''Example #8 - Repeat Commands a number of times''' i.e., #12 kill bug
+'''Example #8 - Repeat Commands a number of times''' with %i functionality, i.e., #12 kill bug %i will send "kill bug 1", "kill bug 2", "kill bug 3"...etc
 <syntaxhighlight lang="lua">
 --Pattern: ^\#(\d+)\s(.+)$
-for i=1, tonumber(matches[2]), 1 do
-   send(matches[3])
+local cmd = matches[3]
 end
 </syntaxhighlight>
 =From zMUD=
 Pretty similar to CMUD - see above.

@@ Line 489: / Line 489: @@
 addMushTrigger(pattern, actions)
-echo("<green>New trigger added")
+cecho("<green>New trigger added")
 </syntaxhighlight>

@@ Line 487: / Line 487: @@
 local actions = matches[3]
-addMushTrigger( pattern, actions)
+addMushTrigger(pattern, actions)
-parsePaste( "<c:text>New trigger added")
+echo("<green>New trigger added")
 </syntaxhighlight>