If you have to press 'C' twice while trying to connect to the game, can you please post the MUD client you are using and what version client you are using?
I am trying to replicate the problem so I can see about getting a fix in place.
Thanks!
Nathvaan
I'm not having that exact problem, but the first command I manually enter per log in session I need to enter twice. This has been happening since everyone else started complaining about the 'C' problem. (I have an autologin thing on my client, so I just skip through all that.)
MUSHclient.
Mudlet does not suffer this problem from my own tests.
I use zMud and I had an autologin trigger. My problem left with your fix though.
I use SimpleMU, and have been experiencing this issue. I will have to look up the version number when I get home.
Quote from: bcw81 on April 29, 2013, 02:38:55 PM
I'm not having that exact problem, but the first command I manually enter per log in session I need to enter twice. This has been happening since everyone else started complaining about the 'C' problem. (I have an autologin thing on my client, so I just skip through all that.)
MUSHclient.
Mudlet does not suffer this problem from my own tests.
This is probably the same issue. Please let me know what version you are running when you get a moment and I will try and reproduce the issue so I can get it resolved.
It's still happening to me too. I'm using Pueblo.
Also, my guys belt and weapons dissapear (although they are still there) And I'm missing people walking (not sneaking) Into and out of rooms. Could this be a related issue? Or should I bug it?
Quote from: Nathvaan on April 29, 2013, 03:29:18 PM
Quote from: bcw81 on April 29, 2013, 02:38:55 PM
I'm not having that exact problem, but the first command I manually enter per log in session I need to enter twice. This has been happening since everyone else started complaining about the 'C' problem. (I have an autologin thing on my client, so I just skip through all that.)
MUSHclient.
Mudlet does not suffer this problem from my own tests.
This is probably the same issue. Please let me know what version you are running when you get a moment and I will try and reproduce the issue so I can get it resolved.
MUSHclient 4.84
Atlantis.
But it was doing this a few days ago.. Stopped today.
Savitar 1.5.2
Happened on and off with MUSHclient 4.73 for...a while now. Can't remember it not doing that every now and then.
I use PortalGT (PC based, not Mac), and still have this issue as well.
Perfect. I am able to reproduce which allows me to test fixes for it!
Savitar 1.5.3
Z-Mud 7.21
It's consistent.
How many of these are new in the last 2 weeks, and how many of them have been around longer than that?
For me, with Savitar, it's definitely new within the past couple of weeks.
Quote from: flurry on April 29, 2013, 10:56:27 PM
For me, with Savitar, it's definitely new within the past couple of weeks.
+1
SimpleMU is new also.
New to me also (PortalGT).
New to me, Mushclient v4.43
Oh, and it is still somewhat random as well...a little more then 50% of the time.
CMUD Pro 3.34 and has been happening consistently since the account error thing people were getting.
Quote from: Morgenes on April 29, 2013, 10:42:42 PM
How many of these are new in the last 2 weeks, and how many of them have been around longer than that?
It had to do it for a long time, I think more than a year. Though I had to press C three times, so the current situation is a definite improvement :P
I even asked about and was told to update my Mush Client which didn't help.
Quote from: Morgenes on April 29, 2013, 10:42:42 PM
How many of these are new in the last 2 weeks, and how many of them have been around longer than that?
It's never stopped doing it since it started for everyone. At least, for me.
Last couple of weeks with Z-Mud.
For MUSHClient users - I'm using 4.73 and having no problems at all. I -did- get that extra C when the issue first cropped up, but it disappeared a couple of days later.
Yeah I get this, plus something a bit more. When I first fire up Arm via Mushclient, it comes up normal but when I hit C, nothing happens. So I have to hit the d/c button, reconnect, comes up normal again, I hit c, invalid option c again, all is well. But I wasn't sure it was Arm, or Mushclient, or my wireless because I've also had weird spurts of lag that seem to be strictly me.
This just now worked correctly, for the first time in a few weeks, for me.
I went back and did it again to make sure, and yeah, it's working right.
Last reboot removed the MSSP code which is why. We are still working on how to do it appropriately.
AlClient (Ashavar's Legacy Client. Yes it's ancient. Yes it's discontinued. Still I'm used to it.)
I don't know for how long the problem was there, I restarted playing only days ago.
I've never encountered this problem. so I assume its gone
It is gone!
Since a crash last night I've been having trouble with this again. Is it just me?
Quote from: Barzalene on June 30, 2013, 10:55:40 AM
Since a crash last night I've been having trouble with this again. Is it just me?
Haven't experienced the C thing again, but today I've had some entered commands not execute properly.
Atlantis and it's been doing this since I started playing 7 years ago and is still doing it (in spite of the fixes).
Using Pueblo client. I had to press C twice, two times today, only when connecting using the IP. When I use the armageddonmud.org 4050 I have no problems. Only noticed this today, never before.
Actually, it's not c. It's the autologin. On both my computers. It hangs after it enters my name. Then when I hit enter it tells me it wants more letters and I have to hit enter and try again. Then it works perfectly.
Quote from: palomar on June 30, 2013, 10:58:52 AM
Quote from: Barzalene on June 30, 2013, 10:55:40 AM
Since a crash last night I've been having trouble with this again. Is it just me?
Haven't experienced the C thing again, but today I've had some entered commands not execute properly.
I would like some more detail about what you experienced when not able to execute commands and if you are able to reproduce this. Can you please send along some more detail?
Please include what client you are using as well.
Thanks!
Nathvaan
It freaks out when I accidentally hit '\' then it hangs for some reason and when I can type again, that command never went through. Usually \ will let me enter multiline stuff.
Quote from: KankWhisperer on July 01, 2013, 12:09:40 AM
It freaks out when I accidentally hit '\' then it hangs for some reason and when I can type again, that command never went through. Usually \ will let me enter multiline stuff.
Thanks, I will have a look at this again shortly!
I don't know if it's my client or not because I've never noticed it. I often use 'L' or 'I' to do look/inventory. Lately these haven't been working and I've been having to use 'look' and 'inv' to get the commands to parse. It doesn't always do this, but it has been doing it lately.
I'm using atlantis for mac os x.
Using the 'use' command in certain cases seems to make the game think I want to brawl, so it doesn't work in most rooms. The command does work in brawl rooms, though. I put in a couple of bug reports about it a few days back.
Quote from: palomar on June 30, 2013, 10:58:52 AM
Quote from: Barzalene on June 30, 2013, 10:55:40 AM
Since a crash last night I've been having trouble with this again. Is it just me?
Haven't experienced the C thing again, but today I've had some entered commands not execute properly.
Just hit this. Mudlet, on Ubuntu 13.04. I was trying to move from one room to another and it took me like 5 or 6 times to get the command though. Shall I send a bug report to you?
Quote from: Cutthroat on July 01, 2013, 08:14:26 AM
Using the 'use' command in certain cases seems to make the game think I want to brawl, so it doesn't work in most rooms. The command does work in brawl rooms, though. I put in a couple of bug reports about it a few days back.
Please bug this in game with as much detail as you can fit on the thing you are trying to use. I will have a look and see if it is related.
Thanks,
Nathvaan
Quote from: Barsook on July 01, 2013, 09:08:31 PM
Quote from: palomar on June 30, 2013, 10:58:52 AM
Quote from: Barzalene on June 30, 2013, 10:55:40 AM
Since a crash last night I've been having trouble with this again. Is it just me?
Haven't experienced the C thing again, but today I've had some entered commands not execute properly.
Just hit this. Mudlet, on Ubuntu 13.04. I was trying to move from one room to another and it took me like 5 or 6 times to get the command though. Shall I send a bug report to you?
Please bug this in game when it is happening. This will allow me to look at the time stamp and ferret out what might be going on at that time for your connection. I'll have a look!
Thanks,
Nathvaan
I will, if it happens again. I have the log to the other one but no time stamp.
This was not happening for a while, but since the reboot this morning it is happening again using Savitar.
Quote from: i can haz mantis on July 08, 2013, 01:44:08 PM
This was not happening for a while, but since the reboot this morning it is happening again using Savitar.
Ditto, except using Mushclient.
Sorry, what was working for some, doesn't work for others. The command eating others were experiencing was far worse. Sorry folks.
Yeah, it's super bad for me, and I wasn't experiencing it before (minimal command eating, but horrendous lag). So weird!
I was having the command eating too. :-\ I'm lose-lose.
Quote from: Barzalene on June 30, 2013, 08:04:41 PM
Actually, it's not c. It's the autologin. On both my computers. It hangs after it enters my name. Then when I hit enter it tells me it wants more letters and I have to hit enter and try again. Then it works perfectly.
I have had both "c" and not accepting the first entry try for my account name for quite a long time now. I use Mushclient 4.84.
This has been happening to me since a few months now.
I'm using CMud 3.33a and have no auto-login trigger set up.
Upon initial connect this is what I get:
Choose thy fate: c
That option is invalid.
Choose thy fate: c
Enter your account name:
Edited to add:
I forgot to mention, upon initial connect, no matter what I input - number, character, alphabet or just simply return, I still get the "That option is invalid" response.
This occurs 100% of the time. No exceptions.
Re-edited to add:
Please disregard my post.
I created a new CMud session and could connect to Arm without any problems.
Obviously there's some miscreant trigger in my existing CMud session that's causing the problem, but for the life of me I can't figure it out.
From what I've gathered from Morgenes this is actually an issue with some new coding and the way it reacts with some clients. I use three different clients depending on where I'm arming from: JMC on a Windows, Savitar on a Mac, BlowTorch on my Android, and it happens on all of them.
They had put in a patch to attempt to fix the code, but it was causing lag and for some users to experience command eating, so they had to take that code patch and those that this is happening to just kind of have to deal with it.
Though after the patch was put in and I was experiencing the command eating, now that it has been removed I am experiencing both issues at the same time but have only noticed both happening using Savitar which is currently my primary client.
Quote from: i can haz mantis on July 25, 2013, 02:29:29 PM
From what I've gathered from Morgenes this is actually an issue with some new coding and the way it reacts with some clients. I use three different clients depending on where I'm arming from: JMC on a Windows, Savitar on a Mac, BlowTorch on my Android, and it happens on all of them.
They had put in a patch to attempt to fix the code, but it was causing lag and for some users to experience command eating, so they had to take that code patch and those that this is happening to just kind of have to deal with it.
Though after the patch was put in and I was experiencing the command eating, now that it has been removed I am experiencing both issues at the same time but have only noticed both happening using Savitar which is currently my primary client.
I am still experiencing some command eating. Its not like it was before at all. This is minor things: emotes, tells, psi, etc. Before look, directional commands, pretty much everything was a problem. I'm using Mudlet. I'm fine with just the emotes, tells, and psi getting eaten. I'm more concerned with the HRPT coming up and the intermittent packet loss issues that have been happening. And even more worried after yesterdays episode of the server not being able to be pinged and MTR showing no routes past the 8th hop when the server is 10 hops away. Seems like that is an issue on Arm's ISP end.
Sorry for bringing this thread alive again, after I upgraded Mudlet to 4.6.2, I started to have this issue again. I think I did the upgrade a month ago. I was on the one that was in the repos of Ubuntu 19.04 and never had the issue on that version. Is this tied to this bug or is there a setting that I need to change?
Quote from: Barsook on April 16, 2020, 11:36:06 AM
Sorry for bringing this thread alive again, after I upgraded Mudlet to 4.6.2, I started to have this issue again. I think I did the upgrade a month ago. I was on the one that was in the repos of Ubuntu 19.04 and never had the issue on that version. Is this tied to this bug or is there a setting that I need to change?
Do you have the Auto clear the input line after you sent text option checked off or on?
It's in Preferences -> Input Line
Nope, didn't help.
Looks like the newest version, 4.10.0, fixed the problem. Maybe?
Nope.
QuoteAugust 22, 2021 (Sunday)
(Tenebrius)
-Fixed issue with not all commands going through for users running Mudlet. (hopefully)
Thank you! I think this fixed the problem.