Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD Beta Forum Goto page 1, 2  Next
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Sat Mar 07, 2009 12:19 am   

[3.04] Responses from MUD are displayed on the prompt line
 
Somehow in the new version it is putting responses from the MUD on the same line as the prompt as in:

<I send something>
<prompt> <response from MUD>

It should be like this:

<I send something>
<prompt>
<response from MUD>

I have 'Use GA/EOR for prompt' selected, if that makes any difference. Just started with 3.04.

When it puts the output of the mud on my prompt line it screws up my triggers since all of them start with a regex '^' to anchor them to the start of the line.

Grrr how annoying. This alone is going to make it so I can't use this version for anything important.
Reply with quote
Fang Xianfu
GURU


Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom

PostPosted: Sat Mar 07, 2009 12:44 am   
 
Which MUD are you using this on? "Use GA/EOR for prompt" only works if your MUD is actually sending a prompt with GA/EOR.

Basically the reason this happens is because most MUDs don't terminate their prompts with anything - they just end the packet. When the next packet arrives, CMUD can't tell if it's supposed to be appended to the current line (just as if the packet break was in the middle of a line) or if it's really the end of the prompt - as it would if the MUD was sending GA/EOR. So CMUD has to append it rather than make it a new line, and there's nothing you can really do.

If your MUD really is sending GA/EOR and you're getting this, then there might be a problem here.
_________________
Rorso's syntax colouriser.

- Happy bunny is happy! (1/25)
Reply with quote
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Sat Mar 07, 2009 12:47 am   
 
The MUD is Achaea, and as noted it worked fine on every single version of Cmud and every version of Zmud that I've ever used prior to 3.04. Something changed this version.
Reply with quote
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Sat Mar 07, 2009 1:31 am   
 
Here's the raw data which shows the Codes:

************************************************************
************************************************************
0.0304 | i Achaea <shrine56969 a shrine of Shaitan<CR><LF>
0.0000 | guard270994 a Vertani guard<CR><LF>
0.0000 | Number of objects: 3<CR><LF>
0.0000 | <IAC><SB><200>Char.Vitals<LF>
0.0000 | H:7964/8709 M:8691/8811 E:39090/39090 W:35898/35910 NL:99/100 <IAC><SE><ESC>[32m7964h, <ESC>[37m<ESC>[32m8691m, <ESC>[37m<ESC>[32m39090e, <ESC>[37m<ESC>[32m35898w <ESC>[37mcexdb-<IAC><EOR>
0.0304 | i Achaea >gut guard<CR><LF>
0.1039 | i Achaea <You rip into a Vertani guard with your massive, deadly claws.<CR><LF>
0.0000 | <IAC><SB><200>Char.Vitals<LF>
0.0000 | H:7964/8709 M:8691/8811 E:39050/39090 W:35898/35910 NL:99/100 <IAC><SE><ESC>[32m7964h, <ESC>[37m<ESC>[32m8691m, <ESC>[37m<ESC>[32m39050e, <ESC>[37m<ESC>[32m35898w <ESC>[37mcedb-<IAC><EOR>
0.4122 |
************************************************************
************************************************************

What I see:

************************************************************
************************************************************
7964h, 8691m, 39090e, 35898w cexdb-
shrine56969 a shrine of Shaitan
guard233429 a Vertani guard
guard270994 a Vertani guard
Number of objects: 3
gut guard
7964h, 8691m, 39090e, 35898w cexdb-You rip into a Vertani guard with your massive, deadly claws.
7964h, 8691m, 39050e, 35898w cedb-
************************************************************
************************************************************

The bolded part should be on a new line. It looks like all the prompts end with: <IAC><EOR>
Reply with quote
Vijilante
SubAdmin


Joined: 18 Nov 2001
Posts: 5182

PostPosted: Sat Mar 07, 2009 10:52 am   
 
This is quite expectable when you issue the command before the prompt. The server is depending on the local echo of the command to terminate the prompt line.

Number of objects: 3
gut guard
7964h, 8691m, 39090e, 35898w cexdb-You rip into a Ver
_________________
The only good questions are the ones we have never answered before.
Search the Forums
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Sat Mar 07, 2009 4:51 pm   
 
What the hell does that mean?

I have the same problem, which causes my triggers not to fire.

How can you not send a command before the prompt?

Sorry I am a little irritated because I keep having problems and can't even see what is being sent to the server because zs.send isn't echoing my commands.

3500h, 3810m exkdb-
You are blind.
You are deaf.
You have insomnia, and cannot easily go to sleep.
You are coated in an insulating caloric salve.
You have ingested the kola nut and are feeling extremely energetic.
You are tempered against fire damage.
Your resistance to damage by poison has been increased.
You have accepted a blessing for aid in times of need.
Your sense of time is heightened, and your reactions are speeded.
You are protected from the fangs of serpents.
You are walking on a small cushion of air.
You are protected by 11 defences.
3500h, 3810m xkdb-
You have recovered equilibrium.
3500h, 3850m exkdb-You concentrate on gripping tightly with your hands.
3500h, 3850m exkdb-
On-Defense: Skywatch
3500h, 3850m exkdb-
On-Defense: Resistance
3500h, 3850m exkdb-
On-Defense: Vigilance
3500h, 3850m exkdb-
On-Defense: Third eye
3500h, 3820m exkdb-
On-Defense: Weathering
3500h, 3820m exkdb-
On-Defense: Nightsight
3500h, 3820m exkdb-
You've baffled me!
Reply with quote
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Sat Mar 07, 2009 5:00 pm   
 



Last edited by ReedN on Sat Mar 07, 2009 8:01 pm; edited 1 time in total
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Sat Mar 07, 2009 5:04 pm   
 
And I was all happy and delighted I could finally use Lua too! Laughing
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Sat Mar 07, 2009 5:17 pm   
 
Arghhhhhhhhhhh I'm so pissed off. It is echoing at least part of my commands but with this problem it makes Cmud useless!!


3500h, 3820m cxkdb-
You have recovered equilibrium.
touch mindseye
3500h, 3820m cexkdb-Touching the mindseye tattoo, your senses are suddenly heightened.
3500h, 3820m cxkdb-
You have recovered equilibrium.
touch mindseye
3500h, 3820m cexkdb-Touching the mindseye tattoo, your senses are suddenly heightened.
3500h, 3820m cxkdb-
You have recovered equilibrium.
touch mindseye
3500h, 3820m cexkdb-Touching the mindseye tattoo, your senses are suddenly heightened.
3500h, 3820m cxkdb-
You have recovered equilibrium.
touch mindseye
3500h, 3835m cexkdb-Touching the mindseye tattoo, your senses are suddenly heightened.
3500h, 3835m cxkdb-qq
You grow still and begin to silently pray for preservation of your soul while you are out of the land.

The trigger will never fire to set the mindseye defense to true. At this rate none of my system will work because none of my triggers will work when scripts send the commands immediately LIKE I WANT THEM TO!

Haha sorry I was so looking forward to trying this out this weekend.
Reply with quote
Fizban1216
Apprentice


Joined: 03 Feb 2007
Posts: 170

PostPosted: Sat Mar 07, 2009 5:34 pm   
 
Unless I'm misunderstanding the problem the triggers need to be set to fire on prompt as well as newline. You can set this by clicking on the script, then clicking on the + sign near more at the bottom and checking the box that says Trigger on Prompt.
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Sat Mar 07, 2009 5:34 pm   
 
Anyone have a quick fix for this? Some explanation on how to fix it? Anything? Sad
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Sat Mar 07, 2009 5:37 pm   
 
The prompt trigger is set to trigger on prompt not trigger on new line, otherwise it won't fire half the time.
Reply with quote
Fizban1216
Apprentice


Joined: 03 Feb 2007
Posts: 170

PostPosted: Sat Mar 07, 2009 5:37 pm   
 
The content of this message has been deleted by its author.
Reply with quote
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Sat Mar 07, 2009 5:41 pm   
 
I have a two triggers, one marked for 'prompt' the other marked 'newline'. The prompt one will fire 99% of the time when it receives a prompt. There is like a 1% chance that it will not fire as a prompt when I get a large amount of text from the server and the prompt is embedded inside the packet. In that case the trigger marked with 'newline' will be the only one that will catch that one.

A side-effect of this method is that the 'newline' trigger fires 100% of the time because anytime I get a prompt it fires after it goes to the next line.
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Sat Mar 07, 2009 5:44 pm   
 
Well this doesn't solve the problem anyway. I can't even defup and start testing because I will be touching mindseye all day Laughing

How are the rest of you even able to test or play? Are me and Reed the only people that play Achaea?
Reply with quote
Fizban1216
Apprentice


Joined: 03 Feb 2007
Posts: 170

PostPosted: Sat Mar 07, 2009 6:21 pm   
 
oldguy2 wrote:
Well this doesn't solve the problem anyway. I can't even defup and start testing because I will be touching mindseye all day Laughing

How are the rest of you even able to test or play? Are me and Reed the only people that play Achaea?


Yes, I'd say you probably are. There's only been 9 copies of 3.04 downloaded total. It certainly does not shock me if only 2 of 9 play Achaea considering there are thousands of MUDs.


Last edited by Fizban1216 on Sat Mar 07, 2009 6:26 pm; edited 1 time in total
Reply with quote
Vijilante
SubAdmin


Joined: 18 Nov 2001
Posts: 5182

PostPosted: Sat Mar 07, 2009 6:23 pm   
 
Short quick and dirty workaround. Put "#SHOW" in your prompt trigger.
_________________
The only good questions are the ones we have never answered before.
Search the Forums
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Sat Mar 07, 2009 6:48 pm   
 
Fizban1216 wrote:
oldguy2 wrote:
Well this doesn't solve the problem anyway. I can't even defup and start testing because I will be touching mindseye all day Laughing

How are the rest of you even able to test or play? Are me and Reed the only people that play Achaea?


Yes, I'd say you probably are. There's only been 9 copies of 3.04 downloaded total. It certainly does not shock me if only 2 of 9 play Achaea considering there are thousands of MUDs.


Why don't you quit being a jackass. You've posted smartass remarks twice now telling me something was different from what I said it was. How the hell do you know? It's not my damn computer.

How exactly can we test a beta version when you can't even send a command? Tell me that. There might be thousands of MUDS but most of them are complete crap and generic.

If I have taken your post the wrong way, forgive me. But I'm not in the mood for any bs.
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Sat Mar 07, 2009 7:42 pm   
 
Quote:
Why don't you quit being a jackass.

Everyone just needs to SETTLE DOWN!!!

Obviously this problem is a new bug, related to this entry in the Version History:
Quote:
Fixed problem with extra blank lines appearing after using #PRINT after the MUD has sent an IAC GA MUD prompt


Yes it's a problem, and *maybe* there will be a fix. But everyone needs to remember that this is a BETA VERSION and BETA VERSIONS are for TESTING and not for production playing. You should always have a previous version or backup to fall back to.

Anyone who gets this upset by a bug in a beta version should not be beta testing.

There are a couple of people in this thread who are seriously on the verge of getting banned from this site if this kind of unproductive discussion continues.
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Sat Mar 07, 2009 8:43 pm   
 
I apologize. It is just that it is kind of hard to beta test when this problem prevents you. I'll just go play on 2.37.
Reply with quote
oldguy2
Wizard


Joined: 17 Jun 2006
Posts: 1201

PostPosted: Sun Mar 08, 2009 4:23 am   
 
Vijilante wrote:
Short quick and dirty workaround. Put "#SHOW" in your prompt trigger.


Thanks. That did work somewhat, but it caused all my multiline triggers that require prompts within 1 to break.
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Mon Mar 09, 2009 9:07 pm   
 
Quote:
Sorry I am a little irritated because I keep having problems and can't even see what is being sent to the server because zs.send isn't echoing my commands.

I cannot find any problem with the zs.send command in v3.04. Please post your exact script. I just tested it with this:
Code:
<macro key="F3" language="Lua" id="3">
  <value>zs.send("lua test")</value>
</macro>

and pressing F3 sends "lua test" to the MUD and echoes it to the screen as expected.

I am having a hard time reproducing this problem because I don't know EXACTLY what ReedN means by "<I send something>". Are you typing a command on the command line? Are you sending text with #SEND? Are you using zs.send in Lua like OldGuy? Is it being sent by a trigger (normal or prompt)? (If so, show us the trigger script) You need to remember that there are many different ways to do things in CMUD, so you need to be VERY SPECIFIC about exactly what you are doing.

OldGuy2: You need to post the raw dump from the Script Debugger like ReedN did for me to determine more about this problem.
Reply with quote
ReedN
Wizard


Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon

PostPosted: Mon Mar 09, 2009 9:29 pm   
 
In the example I showed, I'm doing this:

The function @attack() is returning: #return "gut"
$attack = %if( %db( @Repeat, paused), blast, @attack( ))
#exec $attack @target

So it is doing: #exec gut guard

which is what is showed in my log:

0.0304 | i Achaea >gut guard<CR><LF>

In looking at this again I tried typing on the command line, "ih;gut guard" to replicate what was occuring in my log. Of the 12 or so times I tried it, I only saw this bug once. Perhaps this theory: Tthe "ih" sent initially is causing the Mud to return the information about who is in the rooms. As soon as I see a guard in the room, my script executes "#exec gut goard" which interrupts the input coming in to send the command. Perhaps that interruption is the factor that you aren't able to reproduce.
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Mon Mar 09, 2009 10:55 pm   
 
ReedN, that still isn't enough information. Why don't you just post the XML for this? You still haven't told me if your function is getting called by a normal trigger, a prompt trigger, an ATCP trigger, a Oninput trigger, a macro, an alias, or anything else? I can't read your mind. The timing of this is crucial...I need to be able to replicate *exactly* when your "gut guard" is sent to the MUD.

Also, this is yet another case where you should be using #SEND instead of #EXEC. Unless "gut" is some sort of alias you want to "execute", then you should be doing:

#SEND $attack @target

Use EXEC when you want to "execute" a command (which causes it to get parsed, compiled, and executed as a script). Use #SEND when you just want to send commands back to the MUD. But that shouldn't have any effect on this particular bug.
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Mon Mar 09, 2009 11:09 pm   
 
OK, got it. I was able to come up with a script that uses #SHOW to stuff text into the network buffer and then add a #wait delay to simulate a delay in response from the MUD. For other people who want to play with it, here is the test script:
Code:
  <alias name="test" id="1">
    <value>#showprompt "guard270994 a Vertani guard"%{crlf}mcexdb-%char(255)%char(249)
#wait 500
#showprompt "You rip into a Vertani guard with your massive, deadly claws."%{crlf}mcedb-%char(255)%char(249)</value>
  </alias>
  <trigger priority="20" id="2">
    <pattern>Vertani guard$</pattern>
    <value>#exec gut guard</value>
  </trigger>

type "test" to run the alias to show the result. The output I get is:
Code:
guard270994 a Vertani guard
gut guard
mcexdb-You rip into a Vertani guard with your massive, deadly claws.
mcedb-

So now that I have a way to reproduce it, I can hopefully get it fixed in a new release tomorrow.

Edited: Actually, it shows the error even without the #WAIT. The key was to create a trigger that interrupts in the middle of the text input stream.
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD Beta Forum All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net