Triggers and scripts use pattern matching on the current telnet line and activate when a match is made. Everything else is triggered from telnet activity that determines which script runs in response. I use timers to pace the bot so that it doesn't spam the server too quickly and to give order to the various tasks that it needs to run repeatedly. Several timers run which cause the bot to send commands to the server and perform several other tasks. Your bot is now running, connected and initialised. If the login works, the Login Successful trigger runs which sets some more flags and sends several commands to the server to gather information such as who are the admins, players, banned players, server settings and more. The server then requests the telnet password which triggers the Login trigger. Mudlet is event driven and the next script that runs is StartupBot which sets up many things including connecting to the databases.
Mudlet table find code#
The code itself is quite easy to read and the main challenge is learning what triggers each code block. There are comments in the LUA code and more is added occasionally. It just sets some control flags, but you could add anything you want to run first here.
When you first run your bot and connect it to your server, the script FirstRun is executed.
It is an odd fit but Mudlet is a telnet client with LUA scripting support and features triggers, timers and scripts which makes it ideal. The bot runs on top of Mudlet (a multi-user dungeon client).
0 kommentar(er)
