Existing players used to logging in with their character name and moo password must signup for a website account.
- Crooknose 2s
- Fay 8m
- SmokePotion 42s Right or wrong, I'm getting high.
- Yizhi 1m
- Sivartas 1h
- BlackSoul 1m
- Rillem 22s Make it personal.
- hex 5m
- xXShadowSlayerXx 8m
And 19 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

echoing commands? CPU possesion?

ok… i just had the -most- confusing thing happen and i'd like someone to try and explain what happened and if it was on my end or a moo thing. (i'm mostly sure it was on my end because my laptop crashed after this whole thing, but if anyone can explain just what happened it it would be nice :P)
ok here goes.

a) i had to reconnect in the middle of a session because of computer issues.
b) everything was going fine after i connected again, i was standing in one spot using the SIC and everything seemed peachy
c) however, whatever i typed after my 1st 'look' command appeared delayed. i thought the moo was lagged till i realised the commands where, 'stacked' for lack of a better term.
when i typed the next command the one before it would execute.

for example
i typed the 1st look and only got the room name
"Ashlin Street Station"
knowing that moving out of a room sometimes fixes lag for me (not sure why) i typed 'n' but didn't move -and- got the rest of the room description (it seems to be at the exact moment the Sindy script started up)
"This station seems semi-well kept […] colorful graffiti.
The rails beyond the turnstiles sit empty, waiting for a Mag-Lev to arrive.
Sindy the Weathergirl is standing here. �
There are exits to the north (n), shuttle (s), up (u)."
and as soon as that appeared i got the message
"Sindy the Weathergirl appears beside you, smiling brightly as an unseen breeze gently shifts your hair around your naked torso."

i still thought it was lag at this point.

typed 'n' -again- and this time i moved north. i typed 'n' a few times wanting to move off the streets and @quit for the night. i thought that for lag i was moving strangely quickly, as SOON as i typed 'n' i'd get the room description. no delay, not even a 'normal' walking delay. to test my nagging suspicions i waited a bit, nothign happened so i typed 'go s s s' and boom. i move north (the last command) then move south -twice- i typed another command and moved south once… are we seeing the pattern?

to make a long and confusing post longer, say every time i typed 'look' i'd get ONLY the name of the room then i'd type 'u' then 'd' '@who' 'n' '@ooc'
'u' would give me what 'look' should have, 'd' would make me go up, @who would make me go down, AND give me the @who list, 'n' would give me the @who list and @ooc would make me move north while the next command would take me OOC, the 1st @ic command was as if i had typed 'look' in the OOC lounge while the 2nd @ic took me IC...
lost you yet? since it was hard to move anywhere and get my char to safety, i thought reconnecting would reset things (don't yell at me, i know we arn't supposed to but i needed to log off and my computer was making strange noises) ... @quit made the last command happen -and- then made me quit the game. (i'm glad this was going on when no one was around :P)
so i reconnected to find the same same thing. stacked commands, plus i was still RPing on the SIC, i -seemed- to send out double SIC messages (sorry to the player i was SICing with if you where confused, (it was one of those days where i was close to using the SIC OOCly))

then my computer crashed.

then i rebooted, reconnected and everything was fine.

yesh i xhelped at one point but i'm not sure that even went through because it moved me north.

so uhm... is my computer possesed, have i been doing too much acid again or what?
at this point if you say 'moo gremlins' i'll just accept it :biggrin:

(Edited by Bias at 1:27 am on May 16, 2003)

I can't really give you a full explination for exactly what happened without getting terribly complicated, but let me try and make a general broad conjecture:

Your computers whole job is to remember and deal with a ton of numbers. Numbers make up the information you see, and more importantly, numbers point to where the information is.

When these numbers changed in the wrong way (are added instead of subtracted) or some change while others don't, or they're simply misplaced or swaped in goofy ways, or zeroed out, the entire system get's out of sync.

An 'out of sync system' (this is me trying to talk laymen terms) can manifest itself is a varity of ways ranging from minor things like graphic errors to strange things like what you experienced tonight.

When the severity is 'margianal' enough, to allow you to continue, it's possible that doing other things can have a kind of cascading effect as things get more out of sync.

Eventually what enivetibly happens is you get a 'page fault'; an aptempt by one program to access another program's 'memory', or information. Windows is suposed to deny this, and close the program.

But when WINDOWS itself has the affected 'out of sync' pieces… bad thing occur, and POOF, it's now managed put your PROCESSOR in an invalid state.

Your CPU is of course designed to not allow this type of primitave behavior on your part and promptly responds by rebooting. It knows when the software has stoped talking to the processor. It unfortunately can't tell the difference between the software running nicely and the software running correctly on the CPU, but incorrectly for you. That would be nice... but were still a little ways away from that level of sophistication.

-Kevlar

Genuinely not trying to deliberately contradict you on this one Kev, merely posting something of a related anecdote that -may- or may not be of interest.

Back when I was admin I experienced what Bias is describing on several occasions, always under the same conditions, after losing connection and reconnecting, usually if the connection was lost while commands were being processed. It was possible to increase and decrease the number of commands stacked before the top one would be processed, even to the extent of being over a dozen commands behind what I was keying. In these extreme cases I'd sometimes have to cycle my connection several times to get the commands I entered in sync with the one being processed, the amount of commands apparently "buffered" decreasing with each subsequent reconnection. It's hard to accurately describe and quite bizarre to experience. Personally I believed it to be a server side quirk, especially given that I could recreate the anomoly irrespective of computer or client being used and also, by vary the method, control the extent of the anomoly. Something quirky in the buffer of commands to be executed for a given connection or something, never got round to delving into the cause or possible solution given the infrequency of happening.

Dunno if that helps any, but I must stress that I'm really REALLY not posting it to contradict Kevlar's post, this all immediately sprang to mind as I was reading Bias' post, before I got to his explanation.

thank you both for trying to explain the strangeness, both explenations sound logical to me, knowing what a POS my computer is -and- knowing what stacked commands are.

if something like that happens again i'll make sure to try more xhelping during it so it can be looked at.

Personally I believed it to be a server side quirk, especially given that I could recreate the anomoly irrespective of computer or client being used and also, by vary the method, control the extent of the anomoly.

I've personally seen the same thing on the client side, but never on the server side. However the MOO does support buffered client output, so it's certianly a posibility.

While it's not something I can argue with or rule out, the hint for me was her computer rebooted immideately afterwords.

Like many mysteries, we may never know the truth about this one. Si la vie.

-Kevlar

I can't for the life of me remember what I used to do to cause it to happen… it'd be interesting to recreate it and see what you made of it, I hate niggling little puzzlers like that going un-answered.
Its an -input- problem from the sounds of it, not output.

Try the .flush command (if it is still usable).

hurr hurr.  like a toilet.  :biggrin: