Started today. Noticing it with other players. Just getting dropped by the host.... Reconnecting... Dropped by host... Reconnecting... Dropped by host... etc, etc, etc...
Fixes?
It seems better now, but I had some as well.
It's not better....
It seems better for me now too.
Then again, it started doing this to me earlier this morning and then 'seemed better' before it started again.
Have noticed when typing an exit that is not valid or if Whira is blowing the sand.
Quote from: whitt on July 03, 2014, 04:44:40 PM
Have noticed when typing an exit that is not valid or if Whira is blowing the sand.
Isn't Whira -always- blowing sand?!
And if you notice it happening when you type an invalid exit...then stop walking into walls and disrupting the game for all of us, whitt!
:P
Quote from: manipura on July 03, 2014, 04:47:24 PM
And if you notice it happening when you type an invalid exit...then stop walking into walls and disrupting the game for all of us, whitt!
:P
Hah. No one tells
me what to do.
Hazards of being an IT person. I can not stop trying to break it now.... must debug....
The fat kid in me read the subject and thought "RANDOM DAIRY QUEENS HAPPENING?!!!"
Quote from: Redheart on July 03, 2014, 05:22:32 PM
The fat kid in me read the subject and thought "RANDOM DAIRY QUEENS HAPPENING?!!!"
Me too. Me too. Now I want a blizzard...
Quote from: Delirium on July 03, 2014, 05:30:34 PM
Quote from: Redheart on July 03, 2014, 05:22:32 PM
The fat kid in me read the subject and thought "RANDOM DAIRY QUEENS HAPPENING?!!!"
Me too. Me too. Now I want a blizzard...
I want a dilly bar
or a Starkiss
Quote from: LauraMars on July 03, 2014, 05:31:56 PM
I want a dilly bar
or a Starkiss
We don't really have DQ in CA, and I don't know what those things are, but a starkiss sounds like it would burn.
I feel like I've been getting almost-timeouts a lot lately, where it won't respond for about 30-45 seconds, and then 4 commands will go through at once. And one of my computers has also decided it would be awesome if MUSHclient would make me connect, freeze, disconnect, connect again, and have to type "c" twice, every single time I play, before it will actually let me log in. I'm pretty sure it will begin to demand tribute soon.
Quote from: James de Monet on July 03, 2014, 05:51:35 PM
have to type "c" twice, every single time I play, before it will actually let me log in. I'm pretty sure it will begin to demand tribute soon.
The "c" issue started a little over a year ago and was affecting several different clients. It was the result of some code change in game. The code was reversed or changed to not affect most clients, but it never went away for me. My guess is that some small tweak was made to the game that is making this happen again and causing these other issues.
Oh, and we don't have DQs here either... well, there's one, but it's like 30 miles away.
Yeah, the weird part is, MUSHclient on my laptop doesn't do any of those things, so it must be version dependent.
Quote from: James de Monet on July 03, 2014, 06:06:57 PM
Yeah, the weird part is, MUSHclient on my laptop doesn't do any of those things, so it must be version dependent.
That particular problem is only 50/50 for me on any given login. I'm on MUSHclient as well.
the double C thing happens for me every time too. Got so annoying I figured out an automatic login sequence that connects me, disconnects me, connects me again, and then logs me in with my username and password
Quote from: RogueGunslinger on July 03, 2014, 06:21:26 PM
Quote from: James de Monet on July 03, 2014, 06:06:57 PM
Yeah, the weird part is, MUSHclient on my laptop doesn't do any of those things, so it must be version dependent.
That particular problem is only 50/50 for me on any given login. I'm on MUSHclient as well.
Wow all this time I thought it was just me.
Here we go again....
Mmmm...
(http://3.bp.blogspot.com/-yPmlS1WvY1w/TiQyLtECP9I/AAAAAAAABms/voNElv1RDxQ/s320/DQ-Blizzard.png)
Quote from: RogueGunslinger on July 03, 2014, 06:21:26 PM
Quote from: James de Monet on July 03, 2014, 06:06:57 PM
Yeah, the weird part is, MUSHclient on my laptop doesn't do any of those things, so it must be version dependent.
That particular problem is only 50/50 for me on any given login. I'm on MUSHclient as well.
On Cmud it is about 50/50 as well. I just have to be vigilant and make sure it has received the first c before I type in the rest.
I remember reading at some point that the server got bumped to the East Coast a while ago. This storm had knocked outbpower twice and I havnt had internet for days. Maybe?
You guys made me go get a Blizzard. I hope you're happy.
Deleted
Quote from: James de Monet on July 04, 2014, 08:20:53 PM
You guys made me go get a Blizzard. I hope you're happy.
Extremely.
;D
y'all some viral marketing motherfuckers
In addition to the "double C" bug James is getting in MushClient, lately I've also been having to reconnect to the Armageddon server when I first open its World in MUSHClient. It stalls out or something before I even get to the mantis.
Quote from: BadSkeelz on July 08, 2014, 02:32:50 PM
In addition to the "double C" bug James is getting in MushClient, lately I've also been having to reconnect to the Armageddon server when I first open its World in MUSHClient. It stalls out or something before I even get to the mantis.
I used to think this happened to me, until I realized that if the screen doesn't scroll to the bottom, it won't accept command input. But if you reduce the size of your window until after you're all logged in, it'll be fine. At least that's how mine works.
Interesting. I'll give that a shot when I get home.
Quote from: valeria on July 08, 2014, 05:58:23 PM
Quote from: BadSkeelz on July 08, 2014, 02:32:50 PM
In addition to the "double C" bug James is getting in MushClient, lately I've also been having to reconnect to the Armageddon server when I first open its World in MUSHClient. It stalls out or something before I even get to the mantis.
I used to think this happened to me, until I realized that if the screen doesn't scroll to the bottom, it won't accept command input. But if you reduce the size of your window until after you're all logged in, it'll be fine. At least that's how mine works.
I've had the double C bug for years - this fixed it. Kind of a pain in the ass to drag the text box up, but it totally works.
Quote from: manonfire on July 08, 2014, 09:25:41 PM
Quote from: valeria on July 08, 2014, 05:58:23 PM
Quote from: BadSkeelz on July 08, 2014, 02:32:50 PM
In addition to the "double C" bug James is getting in MushClient, lately I've also been having to reconnect to the Armageddon server when I first open its World in MUSHClient. It stalls out or something before I even get to the mantis.
I used to think this happened to me, until I realized that if the screen doesn't scroll to the bottom, it won't accept command input. But if you reduce the size of your window until after you're all logged in, it'll be fine. At least that's how mine works.
I've had the double C bug for years - this fixed it. Kind of a pain in the ass to drag the text box up, but it totally works.
Thanks, going to try that.