I commonly experience times when i can't get commands into the game. i notice this the most with Say and Emotes. I'll have to spam the thing I was to say, or way, or emote 15-40 times before it will go through.
Anyone else experiencing this? I'm using mudlet, in case that might be it. i don't remember Arm doing this before I took my break. Is there a fix anyone knows of?
I've never experienced that except during lag times. Perhaps it is your DNS server setup? Does it happen if you login from the local Starbucks instead of from home?
You could try connecting to arm using the IP address instead: 206.72.201.199.
I use MUSHClient and have never seen this happen.
Is there lag between these events? Or are those specific commands being eaten but everything else is fine?
maybe there's something with Mudlet and ~ or one of the other special characters?
It's a Mudlet issue. It doesn't happen in any other client from what I can tell.
This used to happened to me in CMUD sometimes. Emotes, says, psis--anything that was a bit on the long side. Stopped happening when I switched to MUSHclient.
thanks for the information!
I use CMud and I experience this on occasion but not so extreme. It seems to be related to using words that are in multiple triggers or other scripts but that is just a hunch.
It's definitely Mudlet. I also have the same issue. What I do is delete the period at the end of my sentence. Type the period back in. Then enter. And so it usually works and I only have to enter my emote/say/whatever twice instead of a bunch of times.
I use Mudlet and can confirm this defo happens to me lots.
And not just emotes.
Sometimes, it happens with simple commands.
Like stand.
And flee.
Happens to me once in awhile in mudlet. Not to the degree most others are complaining about though.
I never get fourty but sometimes I have to put commands through more than once.
Quote from: chrisdcoulombe on November 14, 2017, 11:47:59 PM
I never get fourty but sometimes I have to put commands through more than once.
It might be impatience, and I did fluff the number a bit, but I did count 27 the other day.
mushclient yo
But to have to run Wine to run Mushclient is meh.
I liked Savitar when I was on a mac.
I do not have this problem in MUSHclient on Windows.
I've actually had this issue on Mudlet. It doesn't bother me much. What IS strange is that I've never had it until I started playing Armageddon, specifically.
Is this a DikuMud thing?
tintin for the win.
You can try fiddling around with the settings. Open up the 'Settings' and go to 'Special Options'. Check 'Force telnet GA signal interpretation off'. It may, at least, speed up how quickly Mudlet processes commands.
Also, try adding a new line to the end of your prompt (with the prompt command, you can use '\n' to force a new line) if you use a prompt trigger. That (somewhat) worked for me.
This happens a lot for me, and is really frustrating - it seems that the problem is with both CMUD and mudlet, and it doesn't happen with any others apart from Armageddon :(
Quote from: Sorry on November 19, 2017, 01:30:31 AM
This happens a lot for me, and is really frustrating - it seems that the problem is with both CMUD and mudlet, and it doesn't happen with any others apart from Armageddon :(
zMUD used to gag lines that contained your password, and it genuinely seemed to the victim like the line wasn't getting through. What's your password? (just kidding)
Oh it's not that because emotes and stuff echo back to you, it just doesn't go through a lot of the time - about 5 other people replied on this thread saying they got the same thing, I remember it was happening years back even, anyone picking it up and trying to do emotes will see it happen fairly often
Quote from: chrisdcoulombe on November 14, 2017, 11:47:59 PM
I never get fourty but sometimes I have to put commands through more than once.
Maybe ten to twelve times for me during a play session, usually close together. Then it stops - on mudlet.
Losing the command to cyberspace seems highly correlated to how badly I need to stand up after a carru knocks me off my mount. ::)
It'd be awesome if this could maybe get fixed it's years old now, few people on this thread say CMUD too, hmm, I've noticed it's not just emotes that get lost but Psi too
It's literally any command. And it's only for Arm on some clients.
It doesn't happen on any other MUD that I've played with Mudlet.
Has anyone ever had the problem with CMUD where when you're sending multiple lines (often comes up when writing backgrounds/bios, descs, rumors, drawings, or written materials) and they come out in the wrong order? And it's weird because if you send them again, they'll end up in the exact same wrong order. That was the straw that broke the gwoshi's back for me, and I switched to MUSHclient.
Yeah I've seen that too, it seems to be something about the way armageddon receives text compared to other muds where I've copypasted entire room descriptions in with no problems, I think it must be related to how Arm misses stuff that's sent occasionally maybe?
With CMUD if you CTRL+Shift+Enter you can bring up the editor window and in Options at the top of that window, it has an option to "Send line by line" (also there is a button next to the computer icon to send a single line) instead of the whole chunk of text at once, that might make it easier on whatever is going on with Arm :(
Hm, maybe. I never had the problem again after I switched to MUSHclient. Now that I've figured out how to disable MUSHclient's Autosay, I don't think I'll ever have any reason to go back!
I use MUSHclient, and I've never had this problem.
Does this happen when you're entering commands in rapid succession? Could be you're violating some kind of spam interval and CMUD doesn't stop you. There might be a setting for minimum inter-command delay in your client you could change. Total guess, but it seems plausible.
If you're asking me, no, it never happened when entering commands quickly. It only happened when entering a bunch of long lines of text at the same time. They all got sent, just sometimes in the wrong order. It doesn't really matter unless someone else has this problem, though, since I now use a different client that doesn't do that.
I use kubuntu and can confirm both mudlet and potato mush client were acting rather strangely when trying to play arm. Suppressing output etc. I ended up switching to tintin++ and never looked back. The very rare glitchy output when doing lots of walking but never a problem.