| www.ClassicTW.com https://mail.black-squirrel.com/ |
|
| botKit – Remote Access for Corporate Bots https://mail.black-squirrel.com/viewtopic.php?f=15&t=34978 |
Page 1 of 1 |
| Author: | Adept [ Sun Dec 11, 2016 2:30 am ] |
| Post subject: | botKit – Remote Access for Corporate Bots |
botKit – Taking your bot to the next level botKit is a bit of an innovative concept (originally inspired by Cruncher.) After several iterations over the course of many months here is its present form, a virtual toolkit that operates independently form your bot, and allowing corporate members to easily resolve issues with bots while bot owners are AFK for extended periods of time; as well other features are built into botKit. Here is a rundown of features for botKit (External Services): Funtions for both TW2002 v1 and v2. Built in ANSI styled warnings and non-system auto-script termination on TWGS host shutdowns and disconnects, including client disconnect/reconnect warnings. Built in spoof checking (only with exception to Prompt Sentry, which is still in need of modifications, but does function correctly--is just very complex due to the wide variety of prompts and potential circumstances that may occur in TW2002.) setssr {#} - Affords the CEO the ability to quickly switch all inactive bots to a new SSR channel. This function is both a self-contained script and also built into botKit. Automated bot (command access) logins for corporate members, both at startup and when inactive and bot login messages are received. [botname] reboot! - Compels a terminate and restart of a player’s active bot. [botname] bots {#} - Searches through local bot files to manually start bot, via a numerated listing--bot filenames must contain the word ‘bot.’ [botname] sk {#} - Script Killer, provides a method to terminate active scripts via a numerated listing--terminating a targeted script. [botname] prompt - Displays the player’s current prompt. [botname] rollcall - Calls for a check-in of an individual bot. ‘rollcall’ - Calls for a check-in of all available corporate bots; each responding with (this also serves as a ready means to quickly retrieve bot names.): ‘[botname] - Present.’ * The ‘reboot!’ command is intended to resolve issues with send unresponsive or frozen bots. It will search the scripts directory (one folder deep) for the first filename matching the first-in-line active script with the word ‘bot’ in it. * ‘Rollcall’ confirms which bots are actively responsive on comms--SSR. * Comms-Shield silently runs in the background, ensuring that silenced comms are turned back on when it detects a stationary prompt. Using a random timeframe within 2-minutes to test prompts, dynamically resetting upon each mismatch and self-terminating on manual comms reactivation. This is very similar to Z-bot’s Comms Guard, though less intrusive. * Prompt Sentry also runs in the background as a preventative for bots that have been left hanging on non-main prompts. It will attempt to cycle the player back to a main prompt without putting them in harm’s way, e.g., if non-fed-safe at StarDock it should not lift them off the dock. [botname] botkit on|off|status - Turns botKit on, off, or broadcasts its present status. botKit will technically still be running as a script; however, will be completely non-responsive and inactive when set to off--until turned back on. * botKit may be remotely started using (also performs a bot reset): [botname] botkit on Setup instructions: - The zip file provides the file structures for easy copying of files into your Mombot directory (most of these files are included simply to prevent invalid bot command errors.) - Source files are also provided. - Sound files are included as used for certain functions. 1. Copy all included files to their designed directory. 2. botKit is intended to be ran as a daemon through TWX Proxy Setup, simply access: Setup > Auto Run > Add Script > “Scripts/Mombot/Daemons/exter_srvs_monitor.cts” 3. Close and restart TWX Proxy. Important Notes: * botKit requires the default script directory structure as set by TWX Proxy, i.e., ‘Scripts/’ * If any other active scripts have the word ‘bot’ in it, it will cause issues when using certain botKit functions. * botKit will only initialize upon entry/reentry into the game, after having logged in. * 'external_services.ts' will no longer work properly if compiled, there is an issue with corruption of wildcards. (Official release of botKit v1.02) Download botKit
|
|
| Author: | Hammer_2 [ Sun Dec 11, 2016 8:14 am ] |
| Post subject: | Re: botKit – Remote Access for Corporate Bots |
nice one, will check out in due course. I can think of times when I wish I could have re-started someone's bot. I've been known to kill them.. |
|
| Author: | Adept [ Mon Dec 12, 2016 5:44 am ] |
| Post subject: | Re: botKit – Remote Access for Corporate Bots |
lolz Hopefully it can withstand your highly specialized form of abuse. j/k |
|
| Author: | Adept [ Sun Dec 18, 2016 2:04 am ] |
| Post subject: | Re: botKit – Remote Access for Corporate Bots |
Here is a small update to botKit. I fixed a few bugs I found in Prompt Sentry while playing in a test game. Also performed a few maintenance related mods. botKit v1.01 (simply download, copy and paste over the current file in "Scripts/Mombot/Daemons") * Update is in above package now, v1.02 |
|
| Author: | Adept [ Sat Dec 24, 2016 10:58 am ] |
| Post subject: | Re: botKit – Remote Access for Corporate Bots |
Update v1.02 is now posted (link in very first post.) This update resolves an issue with the stop script command, which requires running the script from a completely separate script; so instead of running the script directly through TWXProxy settings tab as an auto-start script, just (remove the 'external_services.ts' script if previously selected) and redirect the script to the newly included script 'exter_srvs_monitor.cts'. (This is essentially the same as before, but just through another file, thus ensuring botKit is always running, unless placed in standby mode--also botKit is bottable, so long that the bot is functioning of course.) |
|
| Page 1 of 1 | All times are UTC - 5 hours |
| Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |
|