Zugg Software :: View topic

Newbie Joined: 20 Mar 2003 Posts: 8

Is it possible to make this go away? :)

Enchanter Joined: 10 Oct 2000 Posts: 656 Location: USA

not that i know of, it happens from time to time. I think it has to do with the mud sending prompts.

Talahaski
Processor PIII 1000
Memory 265MB
Video NVIDIA 64MB
Windows XP
Zmud Version 6.55a
Zmapper Version 1.14

http://www.dartmud.com

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

quote:

not that i know of, it happens from time to time. I think it has to do with the mud sending prompts.

Talahaski
Processor PIII 1000
Memory 265MB
Video NVIDIA 64MB
Windows XP
Zmud Version 6.55a
Zmapper Version 1.14

http://www.dartmud.com

There's a great way to remove them, if you don't mind removing ALL blank lines. Simply create a trigger to match a blank line and place a #GAG command in that trigger. Whenever you gag anything, this trigger will match the resulting blank line and will %99.999 seamlessly remove it without a lot of jumping text.

#trigger {^$} {#gag}

Most people prefer a bit more control over which blank lines get removed, and this can be almost as easily taken care of with state triggers. For instance, if you only want to remove the blank line between name and description in this text:

quote:

[Room name.]

Here is a standard MUD room. There's not much to see in this one. An object, an object, and an object are here.
This room is illuminated.

Some NPCs are here.
Some PCs are here.

Obvious exits: none.

You can create a 4- or 5-state trigger:

#trigger {~[*~]} {}
#cond {$} {#gag}
#cond {^%*$} {}
...

This will ONLY match that particular grouping of text, so there's not as much of a need to do any special parsing of room name and description to weed out false positives.

li'l shmoe of Dragon's Gate MUD