The !addcommandfull is only usable by me. That just saves me logging into the thin client to add the command manually
The !addcommand command is there to "$$2 = command" and "$$3- being the text to be added to the command".
I've edited the !addcommand, to remove all the following: | { } [ ]
write C:\Users\danie\AppData\Roaming\mIRC\additionalcommands.txt on *:TEXT:! [ $+ [ $2 ] ] [ $+ [ $chr(58) ] ] [ $+ [ $chan ] ] [ $+ [ $chr(58) ] ] [ $+ [ $chr(32) ] ] [ $+ [ $chr(123) ] ] [ $+ [ $chr(32) ] ] .msg # [ $+ [ $chr(32) ] ] [ $+ [ $remove($3,$chr(124),$chr(123),$chr(125),$chr(91),$chr(93)) $chr(32) ] ] [ $+ [ $chr(125) ] ]
This is now removing everything in a command from | - Which will stop the bot breaking at least. With the command forcing a .msg #channel, it'll only post it in their channel anyway.
If I'm checking for a command then, would I be able to do something like this?
on *:TEXT:!removecommand *:#: {
if ($nick != eggfriedcheese) { return }
.msg # ! Removing command: ! $+ $$2 $+ . Please Wait...
var %a $read(additionalcommands.txt,s,$2)
if (%a != $null) write -dl $+ $readn additionalcommands.txt
.timer 1 2 .msg # The bot is reloading the command list, please wait...
.timer 1 3 /reload -rs C:\Users\danie\AppData\Roaming\mIRC\additionalcommands.txt
.timer 1 5 .msg # Command List Refreshed. Command: [ $+ [ $chr(32) $2 ] ] has been removed.
}
This is what gets added to the file, which is the correct format:
on *:TEXT:!command1:#amiretroyet: { .msg #amiretroyet test }
on *:TEXT:!testbar:#amiretroyet: { .msg #amiretroyet test }
However, on testing, this did not work.
