![[OPEN SOURCE] Betabot](https://user-assets.v3rm.net/resource_icons/0/184.jpg?1722644798){kind=icon}
Betabot is a Open Source and extendable bot script.
It has 23 commands (you can easily find out how many commands you have by running >cmds, or just find the occurances of Betabot.API.CommandAPI.CreateCommand, but if the Command Script is obfuscated, that won't work, but there are no obfuscated command scripts that I know of, and I hope that everyone will release their source code of their command scripts).
You can extend Betabot using Luau scripts, if you want these scripts to be executed whenever you run Betabot, you can put them in the Betabot/Commands folder.
Betabot should support all executors, including the ones with no filesystem support (see polyfills.lua, example executor is Codex Android, but I'm not sure because that was only tested like 8 months ago (in February)), although then the functionality for things like auto-exec for command scripts won't work.
Keep in mind that this is an Open Source script, so you can do anything you want, as long as you don't violate the license (the license is AGPL v3, the gist of it is that network use counts as distribution, the licensee (in this case, me) can't be held liable for damages, and the licensee doesn't provide warranty, you must disclose the source code, a copy of the license must be included in the material, you can't change the license, and your changes to the licensed material (in this case, my bot script or any other script in that repository) must be documented (e.g. VCS commit(s))).
It has 23 commands (you can easily find out how many commands you have by running >cmds, or just find the occurances of Betabot.API.CommandAPI.CreateCommand, but if the Command Script is obfuscated, that won't work, but there are no obfuscated command scripts that I know of, and I hope that everyone will release their source code of their command scripts).
You can extend Betabot using Luau scripts, if you want these scripts to be executed whenever you run Betabot, you can put them in the Betabot/Commands folder.
Betabot should support all executors, including the ones with no filesystem support (see polyfills.lua, example executor is Codex Android, but I'm not sure because that was only tested like 8 months ago (in February)), although then the functionality for things like auto-exec for command scripts won't work.
Keep in mind that this is an Open Source script, so you can do anything you want, as long as you don't violate the license (the license is AGPL v3, the gist of it is that network use counts as distribution, the licensee (in this case, me) can't be held liable for damages, and the licensee doesn't provide warranty, you must disclose the source code, a copy of the license must be included in the material, you can't change the license, and your changes to the licensed material (in this case, my bot script or any other script in that repository) must be documented (e.g. VCS commit(s))).
