Zugg Software :: View topic - Idea ([1.09]): A "Show scripts with errors" button

Wizard Joined: 14 Aug 2004 Posts: 1269

Rather than having CMUD "crash" (throw an exception) when it encounters a trigger pattern that the compiler doesn't like, or having it spew out raw script to the MUD when a script that can't be compiled is executed, which on my MUD slows down gameplay, as there is a limit to how many commands per time frame you can send, plus I believe that CMUD slows down a lot when it tries to execute a script that it doesn't understand, I have an idea...

How about a menu option from the Settings Editor to show all triggers and scripts that can't be compiled? It will be like the filtered (search) view, but show all triggers with patterns that aren't understood by the compiler, and all settings with scripts in that are not understood too. This will make finding problems with the compiler or one's scripts a LOT easier.

In addition, there is the idea, that I think Zugg thought of before, to send scripts that don't compile to him like the Send Feedback button, but right out of the Settings Editor for that script.

Also, I think that instead of spewing uncompiled scripts to the MUD, it would be far better if when the scripts are executed, they are instead echoed via the #SAY command, prefixed with something like 'CMUD Script Problem in: ' ...
This will mean that it won't interfere with my mudding so much. :-)

Plus, it might be cool, and probably necessary anyway for the "Show scripts with errors" button, to have a "Compile all scripts" button. I believe that CMUD only compiles scripts when it needs to. This is fine usually when all your settings work, but means that if you have some settings that don't work, you only find out when they either "crash" CMUD (throw an exception) or spew their contents out to the MUD. With the Compile all scripts button, it may be possible to force an exception to be thrown when you are in a safe place or even not connected to the MUD. Also, I've noticed that CMUD uses a reasonable amount of CPU on my machine even when it is not doing anything (no MUD input or output, no user interaction, no tick timer, no alarms), and can use 100% when it is unhappy about a script (and doesn't throw an exception).

Posted: Mon Oct 09, 2006 5:00 pm

Seb, those are all good ideas. I'll try to implement those in upcoming versions.

If CMUD is using CPU time when nothing is happening, then make sure you don't have some background scripts, like #wait or #alarms that might be running. There might be some processing in the background when CMUD saves your setting changes to the database file, but that shouldn't be a continuous CPU usage. If you find a way to reproduce the CPU usage, let me know.

Wizard Joined: 14 Aug 2004 Posts: 1269

OK, I will let you know in a different thread though about the CPU.