Zugg Software :: View topic

Posted: Thu Jul 26, 2012 12:36 am

Running: Windows 7
cMUD 3.34 (as Admin)

I have been running into multiple issues lately. I write all my scripts in Notepad and paste them into the command line. Relying on the package editor for complex and evolving scripts is a little less than ideal, and so it is easier to maintain my scripts in this way.

I have noticed that cMUD likes to add spaces when pasting scripts in via the command line. For example, in an #IF statement, when using OR, it adds two spaces after OR when there was only one originally. The same happens when using %ismember(), between the comma and the stringlist you are matching.

I've also had some scripts that would not work properly for inexplicable reasons, which have required me to use the #KILLALL command to re-paste my scripts into cMUD in order to get them to work. I'm beginning to wonder if cMUD simply has a lot of issues with pasting scripts from the command line.

I've become terrified to use the package editor at times, because twice now it has caused cMUD to crash and corrupt whatever packages I have loaded currently. This is yet another reason why I save my scripts to text files and paste them in via the command line.

Below, I have a script right now that simply will not function and I have no idea why. Maybe someone could give me some insight or advice? I appreciate it.

Posted: Thu Jul 26, 2012 12:39 am

By the way, even if I skip the "vitals" alias all together it will will not fire the "bleeding" alias properly. I've added echoes to various parts of the alias, and the trigger simply will not fire. I have even simplified the "bleeding" alias to be the following, and still it will not work.

#ALIAS bleeding {#IF (@cur_Bleeding > 100) {clot}}

Posted: Thu Jul 26, 2012 12:41 am

Ugh.. I did not mean that the trigger will not fire. It does fire.

What I meant was, the "bleeding" alias will not work through to the end where it sends the "clot" command.

And no, #EXEC {clot} will not work either.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

You've got corruption. Package files (all of them), layouts, mapfiles, and the session database. Use the appropriate methods on all of those (including anything created by CMud) and your problems will likely disappear overnight (or at least however long it takes you to do all the files).

Users such as yourself tend to only fix one set of corruptible data and ignore the rest, which sometimes leads to them thinking the problem is fixed only to have it reappear soon after.

Posted: Thu Jul 26, 2012 7:17 am

What do you mean by appropriate methods? I recently uninstalled and reinstalled cMUD in order to, hopefully, correct some of these issues but to no avail.

I did not however remove all cMUD registry settings, nor did I remove the cMUD directories after uninstalling. I'll try that now, and start fresh using my text files.

Is this what you mean? I appreciate the prompt response.

Posted: Thu Jul 26, 2012 7:43 am

I uninstalled / re-installed cMUD - but did not delete registry information yet. The main cMUD directory was deleted, as well as the session directory or whatever it is, before re-installing cMUD.

I'll have to look into this further tomorrow, but the above script still will not run unless I input the "bleeding" alias directly. Below is the echo, once again, from the alias.

Wizard Joined: 22 Mar 2007 Posts: 2320

Reinstalling Cmud won't get rid of corruption. Corruption takes place in the files in your home directory, not in the Program Files. Cmud does not overwrite the customizable files in your home directory.

Deleting the entire Cmud folder in your My Games folder would certainly be one way to be sure of getting rid of corruption, but rather extreme. The XML export/import procedure is used for your session folders. For a lot of the other files, such as layout and default layout, the usual method is to delete them and let Cmud recreate them from scratch, then customize again.

Matt, I think we really need a sticky on the forum giving the complete detailed procedure for getting rid of corruption. It keeps coming up over and over, and I don't think there is actually a complete procedure currently on the first two pages of discussion here. I don't know the procedure well enough to write it, though.

Posted: Thu Jul 26, 2012 4:09 pm

I deleted the cMUD folder in My Games, as well as the folder in Program Files. I haven't used cMUD enough since to see if the other issues have cleared up, but I'm baffled as to why the above script will not work properly still.

Wizard Joined: 22 Mar 2007 Posts: 2320

Try testing this alias by itself:

Posted: Fri Jul 27, 2012 1:34 am

I had to edit your code to match the variable properly, but this is the edited alias and the results..

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Is your prompt trigger set to Trigger on Newline or Trigger on Prompt? Your original trigger code seems to indicate that it's set to Trigger on Newline, which means the execution waits until a newline is received or generated (Trigger on Prompt means the execution happens as soon as the pattern is matched.)

By the way, regardless of if you stick to a text editor or move back into the Package Editor, you really should write your scripts out in a multiline syntax. CMud doesn't care either way, so writing them in the old, run-on style of ZMud (everything separated by semicolons) is just making it harder for the human to read. CMud will ignore any superfluous/gratuitous whitespace, though you will need to especially mind the formatting of #SWITCH. Also, if you are not using the built-in text editor instead of the command line, you should look into that as well (it's basically a window-sized command line, and is intended for the larger scripts).