Ugh.... Being forced to take ooc typos in character. How would you deal with it?

[Qzzrbl]

Alright.... So not too long ago, I made a little typo. I had 'k' aliased to 'kill', because that's just kinda what I'm accustomed to, and is what I used in every other mud I've ever played. Well, when attempting to look at someone, I accidentally hit 'k' and wound up attacking someone. I caught myself in time before even really hurting this person and disengaged, stating OOC that it was a typo and nothing more, and that it would be great if we could just ignore it because it's not something my character would do IC anyway.

WELL! Said statements of typo-ism were seemingly completely ignored, and I was practically forced to take it all IC, and now my character may wind up in ALOT of trouble because of this little typo that I quickly pointed out.

Now.... The above scenario may or may not be completely fictitious, but what I want to know is what would you do in this situation?

[Rhyden]

Don't alias 'k' with kill.
Kiss is embarrassing enough.

[Qzzrbl]

I meant moreso, how would you deal with everyone completely ignoring the obvious and blaring typo, and everyone essentially forcing you to play it off like it was something your character would do?

[Is Friday]

This brings to mind problems with the crim code. Since beginning in last August I've run into 5-6 situations in which the crim code has made people stop and talk about how to react to a situation with the OOC command--because the crim code often acts indepent of logic.

[Gimfalisette]

I meant moreso, how would you deal with everyone completely ignoring the obvious and blaring typo, and everyone essentially forcing you to play it off like it was something your character would do?

You don't get to just retcon a code mistake because it was a mistake. The way YOU deal with this situation is just to deal with it. Just like if you accidentally run right up to bahamet and hit it? You're going to get to deal with that, too. So learn to roll.

[Qzzrbl]

I meant moreso, how would you deal with everyone completely ignoring the obvious and blaring typo, and everyone essentially forcing you to play it off like it was something your character would do?

You don't get to just retcon a code mistake because it was a mistake. The way YOU deal with this situation is just to deal with it. Just like if you accidentally run right up to bahamet and hit it? You're going to get to deal with that, too. So learn to roll.

True enough, but the bahamet is an npc, coded to fight back when attacked accident or otherwise. Another player is a whole different story, who can rationalize the "Agh! That was a typo, had 'k' aliased to 'kill'" in OOC flashing across the screen. Also said player should rationalize, "Ah, shit happens, it was a typo, no big deal.".

So between npcs and PC's, it's entirely different.

[Gimfalisette]

So between npcs and PC's, it's entirely different.

No, you're wanting it to be different, and I'm saying it's not different. If you screw up and get killed by a bahamet, you don't get rezzed. If you screw up by attacking a PC and get killed by HG soldiers, you don't get rezzed. If you screw up by attacking a PC and you get social crap for doing so, you don't get a walk just because it was an error.

Mistakes are part of playing ARM, and you will learn from them and enjoy the outcome...if you roll with it.

[Qzzrbl]

Alright.... Any other opinions on this out there?

[Marauder Moe]

Good lord... you aliased 'k' to 'kill'?  It's so disastrously close to 'L'.  Heck, I'll alias 'k' to 'nothing' just to avoid kissing random strangers.

But anyway, the situation is kinda tricky.  Some OOC mistakes can't be taken back, like the dreaded ">psi I'm going to kill you very slowly, you old fool!" when you meant to ">thinks I'm going to kill you very slowly, you old fool!"  It would be unfair to the receiving player to force them ignore that information in that case.

In your case, though, I personally would have agreed it didn't happen and rested off the damage.  No permanent harm done, no secret information revealed.

I'm not saying the other person was wrong to insist it be dealt with ICly, I'm just saying I wouldn't have done so.

Perhaps you should have wished up and let the staff decide.

Another possible thing to do would be like "Oh!  Sorry dude, I tripped!  Let me buy you a drink..." along with "ooc Ack!  Sorry, accidentally hit an alias!", and thus hopefully the other person will be more likely to have their character let it slide (but not necessarily).  A sort of compromise.

[Is Friday]

I've played a couple mulligans myself. I don't think there's any shame in that, in some situations.

[touringCompl3t3]

Qzzrbl,

I'm not sure how I'd deal with that -- I admit I'd have trouble too.

It's not friendly when people won't cut a little slack for out of game mistakes -- it creates bad out of game vibes.  I wish people wouldn't do this.

[FuSoYa]

I always alias k to key.  It works!

Brandon

[Agent_137]

you guys are idiots.

alias k to keyword. i bet you don't even know what that command does.

as Gimfalisette pointed out, nothing permanent was done, and no secrets revealed, it would have been very easy to just ignore it. So in this case, yes, it sounds like the fellas you were RPing w/ were just being pricks about it. [i know if they may not in fact be pricks if there is more to the story, don't come up here crying. i'm just working w/ the info i have.]

But once you see they're going to ignore your request to ignore,  i don't know what i'd do. You could ignore their ignoring of your request to ignore and pretend like it never happened. But they'll likely keep pretending like it did. Then you can either just let it go, escalate it to staff (which would be a silly waste of their time unless it was a serious character changing issue), or tell them to shove it up their ass and retire. It all depends on how serious the mistake was. Was this a templar you attacked? Or just another soldier? Perhaps the best solution, like someone else suggested, is not to ask for an "ignore" but to quickly provide your own explanation of the event, like tripping.

Any way you slice it though, further interactions with those PCs will be colored poorly by the event, and i'm glad it didn't happen to me.

[FuSoYa]

you guys are idiots.

alias k to keyword. i bet you don't even know what that command does.

Uhmm... that's exactly what I had just said to do.

Brandon

[Mood]

Rofl.

edit: GODDAMNIT WHY IS THE "B" SO CLOSE TO THE "ACKSTAB"!?!?!?!

[manonfire]

when a request is made, you must respect that request and not alter it

in this age of the internets

for the love of the game

don't you bored to always play same game since years with his 'i aim the feet/bird i headshot?'

[Qzzrbl]

you guys are idiots.

alias k to keyword. i bet you don't even know what that command does.

as Gimfalisette pointed out, nothing permanent was done, and no secrets revealed, it would have been very easy to just ignore it. So in this case, yes, it sounds like the fellas you were RPing w/ were just being pricks about it. [i know if they may not in fact be pricks if there is more to the story, don't come up here crying. i'm just working w/ the info i have.]

But once you see they're going to ignore your request to ignore,  i don't know what i'd do. You could ignore their ignoring of your request to ignore and pretend like it never happened. But they'll likely keep pretending like it did. Then you can either just let it go, escalate it to staff (which would be a silly waste of their time unless it was a serious character changing issue), or tell them to shove it up their ass and retire. It all depends on how serious the mistake was. Was this a templar you attacked? Or just another soldier? Perhaps the best solution, like someone else suggested, is not to ask for an "ignore" but to quickly provide your own explanation of the event, like tripping.

Any way you slice it though, further interactions with those PCs will be colored poorly by the event, and i'm glad it didn't happen to me.

Maurader Moe was the one who said nothing permanent was done, etc..... Gimf was the one who said to just suck it up.

[Gimfalisette]

Yeah, Moe is nicer than I am, it was me who said to suck it up And although if I had been there, I probably would have let you redact, I still say you just need to suck it up and soldier on.

To give another, more optimistic perspective on why people might not have honored your request: You did something interesting and dramatic, dude. You created a situation for people to RP around. That is Good Roleplaying (tm). So maybe they went with it because it was more fun than pretending your dumbass mistake never happened.

[Yam]

Anyone who doesn't take an obvious mistake as an out of character mistake is a piece of shit and I would never, ever, ever willingly play anywhere near them again.

I would also send in a player complaint about such a situation.

[Khorm]

Without being able to access my character list right at the moment, I'd guess that I have about 30ish mistakes I wish I could take back.

Shit happens, man.. my best piece of advice is to laugh it off and roll with the punches.

I guess in an ideal world you wouldn't have done something like alias k to kill, and then wouldn't have typed k man, and then wouldn't have had to break IC by explaining your mistake, and then the dude would've forgiven you out of the kindness of his bleeding heart... but..

I think expecting people to behave in a certain fashion after any chain of events is an even bigger mistake then 'kill man'. It's upsetting, but we've probably all lost characters to much more stupid things. Like.. getting super high and passing out, only to die of dehydration in the middle of the desert.

[fourTwenty]

Like.. getting super high and passing out, only to die of dehydration in the middle of the desert.

Does doing this more than once make me a dumbass?

[Mood]

Log in high, characters die.

[RogueGunslinger]

Anyone who doesn't take an obvious mistake as an out of character mistake is a piece of shit and I would never, ever, ever willingly play anywhere near them again.

I would also send in a player complaint about such a situation.

I agree with this.

Log in high, characters die.

I also agree with this.

[psionic fungus]

Speak for yourselves, amateurs! 

[FantasyWriter]

I have a bigger problem with kissking (k) someone when I am trying to look (l) at them.  not too good around strangers.

-FW

[Kronibas]

Like.. getting super high and passing out, only to die of dehydration in the middle of the desert.

Does doing this more than once make me a dumbass?

Shit, I hope not man.

[Zira]

I have a small problem with typos, myself. I'm normally quick to correct, and people seem to just roll with it.

On the other hand, if I accidentally hit the wrong person... well, that would depend. Only time I've even come close to it, they were in the same room, and I started to type the wrong name when sparring. In that situation, I would OOC that it was a mistake on my part, and ask them to ignore it. In what you described, I'd take on a shit happens, and come up with an IC excuse.

But then again, online, I'm a bloody masochist.

[NoteworthyFellow]

Here's the thing.

Randomly hitting someone could be a serious, character-changing mistake.  For example, what if your character is a noble and was in some private business transaction with a high-ranking merchant whom you've had a great business relationship with in the past, some place private where the crim code won't get you--and BAM, he just hauls off and hits you, then disengages and says OOC, "Shit, sorry, meant to hit 'l' for look but had 'k' aliased to kill, total typo, sorry!"  You've got two options:

• Ignore the typo and continue as though it never happened, thus preventing an OOC occurrence from permanently screwing with someone's character.
• Force the player to somehow rationalize why their character would suddenly up and hit a noble because you decided it really did happen, typo or not.

Which one of these would you do?

[Lizzie]

I think it really has to depend on the circumstance. Like Noteworthy Fellow's post would be one, in that case, I'd hope everyone would just realize it's an OOC mistake, take 2 RL minutes for both parties to return to normal HPs, and pretend it never happened.

If it was a drunken dwarf ranger having a talk with a noble's aide in the bar, it'd be easy to assume that the drunken dwarf just tried waving a kank fly out of his face and hit the aide by mistake. So it's easy to pretend it was an IC mistake, and RPed as such.

If it was a noble's aide taking a swing at a drunken mul in the bar, well unless that aide is known for taking swings at people who can kill them with a stare, or is known to have suicidal tendencies, there really is no *reasonable and spontaneous* way to RP that. So hopefully the mul's player would accept the typo and move on from there.

If it was a drunken mul taking a swing at a templar, well you know how those muls can flip out sometimes..and this one was drunk - so unfortunately for the player of the mul, I'd have to say the templar's player can insist on RPing it as a perceived intent (obviously the mul can try to beg forgiveness or whatever but the perception of intent would fall to the templar to decide).

[spicemustflow]

I think not accepting the explanation that it was an unintentional typo (if it is clear that the action wouldn't make sense) and forcing the player to suffer the (harsh) consequences is just sheer malice on the other player's part who wants an excuse to do some PKing.

[Tisiphone]

I'm surprised nobody's mentioned this, but what if they just plain didn't believe you?

Look at it from the other person's perspective. How likely is it you actually aliased k to kill? I mean, that's just plain stupid. It might easily have looked to them like you attacked them, chickened out, and tried to blame it on OOC crap, and that has happened before.

[spicemustflow]

Well, before, when I typed for example k s, instead of l s (wanting to look in the south direction), there's nobody by that name here, so I assumed ok, it's for kill. Quite the surprise when I kissed a gortok, i tell you. It is inconvenient to have kill and look so close, but you never know it might suit for some players and if the player is so lame to get out of the fight that isn't going well of him by blaming it on the typo, then I'm sure the oozing trail of his general twinkery would be noticed by some imm sooner or later. In short, I'd give the player the benefit of the doubt, especially if I'm a noble, templar or a braxat...

[Nyr]

A typo is one thing.
Aliasing "k" to "kill" and typoing "l" can be avoided, in the OP's case.

[spicemustflow]

Yes, and I'm sure he will avoid it in the future, but does he have to punished by losing a char for a stupid mistake? The near death experience would do just fine, IMO.

[Shoka Windrunner]

There is a reason k = kiss.

Because if you accidentally kiss someone...it's embarrassing, but your probably not going to get ganked for it.

Unless it's a templar or a noble.

If the other players took it as happening, well, then it happened.  Sorry.  That's the way of it.  And personally...I'd have to say that if anyone tried to tell me, ooc: oops I tried to type l and typed k...sorry.  I'd have a hard time believing them...because I know k is set to kiss.  For the very reason that L and K are close together.

[spicemustflow]

That's the thing that bugged me too, what is the need for the kiss command anyway? Mudsex? You emote most of it. So why isn't the k button left empty? Where is the button for 'grab ass', then?

[Tisiphone]

'kiss' is left in because our MUD likes partial commands, and we needed something for 'k' that wasn't 'kill' or 'kick'.

[Nyr]

Yes, and I'm sure he will avoid it in the future, but does he have to punished by losing a char for a stupid mistake? The near death experience would do just fine, IMO.

The following response is only directed to the OP's hypothetical case in question:

I'm sorry, but if someone has aliased a single letter to a combat command, they are asking for a typo to happen.  And it will happen.
That seems very irresponsible to me as a staffer.  Was it an accident?  Surely.  Was it a mistake?  Yes.  Would I recommend keeping that alias?  I would not!
What if you didn't notice the typo until it was too late?  Getting a resurrection for another character you errantly killed based on this typo will be next to impossible.
Explaining yourself after making this mistake with a quick OOC:  "I typed K instead of l, sorry" would likely result in no one believing you.

In every other case, it would have to be determined on a case by case basis by whatever parties are present.  
Were I playing a character, I would give someone the benefit of the doubt except in the OP's case (which I would find to be a very, very big exception to the norm).

That's the thing that bugged me too, what is the need for the kiss command anyway? Mudsex? You emote most of it. So why isn't the k button left empty? Where is the button for 'grab ass', then?

The "kiss" command is necessary (at least at this time). 
Otherwise, the way that the shortening of commands works would result in you typing "k" and getting either "kick" or "kill" as your command.
"ki" would get you "kick" or "kill" as well.  If you type "kic" then you will get kick.  If you type "kil" you will get kill.
This is done very specifically (I would say) to prevent situations like this from happening.

And while I was writing all of that, players have already answered with shorter answers.  Well, now you have the long explanation also.

[Tisiphone]

Also-also, I'd like to justify it being 'kiss' rather than some theoretical useful command:

When people see 'so and so kisses so and so' they know someone just typoed somehow, without exception. How do they know? They know because Armageddon doesn't use socials. Socials are out of place here. Were it something else...wait...

Why can't 'k' just default to 'keyword'?

[Gimfalisette]

Why can't 'k' just default to 'keyword'?

Because you'd still have the problem of "ki" needing to default to something.

[spicemustflow]

I was never too big on the code aspect so this was very informative, thanks Nyr and others.

[Rahnevyn]

We could always delete the "kiss" command and code two commands "kil" and "kic" that just say "If you want to KILL (or kick) someone, type out the full command."

IIRC, the way the DIKU command interpreter works is that all commands are in a list, which is searched from first to last to find a command string that matches input. This is why "l" goes to "look" and not "listen" -- look is given higher precedence in the list.

I don't mind that we have a kiss command. I wouldn't cry any tears if it went away. On the other hand, I think it would be hilarious to see players playing out intimate scenes using nothing but coded commands.

---

Back on topic of the thread, I would say it's always nice to be forgiving and flexible with your fellow players, but at the same time, you can't expect someone to ignore an action because you OOC asking them to.

[NoteworthyFellow]

How about making 'ki' actually just be a command that has the exact same function as 'look'?

[Gimfalisette]

I don't mind that we have a kiss command. I wouldn't cry any tears if it went away. On the other hand, I think it would be hilarious to see players playing out intimate scenes using nothing but coded commands.

Does "kiss" accept command emotes?

[Tisiphone]

Why can't 'k' just default to 'keyword'?

Because you'd still have the problem of "ki" needing to default to something.

Oh, hey, those letters ARE right next to each other.

[Rahnevyn]

To avoid further derailment, please move all talk about commands, typos and abbreviations to here: http://www.zalanthas.org/gdb/index.php/topic,31226.0.html

This thread can return to discussion about how to roleplay around other players' OOC mistakes.

[Mood]

I'm surprised nobody's mentioned this, but what if they just plain didn't believe you?

Look at it from the other person's perspective. How likely is it you actually aliased k to kill? I mean, that's just plain stupid. It might easily have looked to them like you attacked them, chickened out, and tried to blame it on OOC crap, and that has happened before.

I think this is the most likely explanation.

[Qzzrbl]

For the record, the possibly fictitious person in the hypothetical situation in the original post, who may or may not have accidentally attacked someone when typoing 'k' for 'l' when 'k' was aliased to 'kill', has, in fact re-aliased 'k' to "aidjaflisfjasli" and will probably never re-alias 'k' again to avoid this happening ever again in his hypothetical little future.

[Bebop]

Hmm.

We are playing a game here people.

IMO typos happen.  There is a big difference between being in a tense situation getting in someone's face and then typing kill or languidly sitting around at the bar and suddenly hitting kill and going oh shit sorry!  I've actually done this like a fucking moron.  I have NO idea why but I was trying to KICK someone out of a clan and I was doing it urgently instead of hitting dump I put kick so and so, and I was like oh damn.  It happens.  Use your discretion.  But I would assume if someone was sitting around shooting the shit with someone else and accidentially attacks them, immediately disengages and says oh sorry typo!  There is no reason to launch into a full scale assault that will ultimately make the person lose their character over such a small slip.  We are playing a game.  Like wise I have emoted peeing into someone's eyes instead of peering.  Sure there was no coded reinforcement but if that person had been like OMG OMG you totally peed in my eyes, I would have been like ... wow you are retarded.  Typo's happen.  It's a game.

[Agent_137]

I'm surprised nobody's mentioned this, but what if they just plain didn't believe you?

Look at it from the other person's perspective. How likely is it you actually aliased k to kill? I mean, that's just plain stupid. It might easily have looked to them like you attacked them, chickened out, and tried to blame it on OOC crap, and that has happened before.

I think this is the most likely explanation.

If the target didn't die, and the attacker immediately fled and said OOCly that it was a mistake, why would the target not believe the attacker? What would he be trying to achieve by attacking and fleeing? There's no motive.

[Shoka Windrunner]

I'm surprised nobody's mentioned this, but what if they just plain didn't believe you?

Look at it from the other person's perspective. How likely is it you actually aliased k to kill? I mean, that's just plain stupid. It might easily have looked to them like you attacked them, chickened out, and tried to blame it on OOC crap, and that has happened before.

I think this is the most likely explanation.

If the target didn't die, and the attacker immediately fled and said OOCly that it was a mistake, why would the target not believe the attacker? What would he be trying to achieve by attacking and fleeing? There's no motive.

Say they don't know each other?  And attacking someone out of nowhere?  That means your a maniac.  Maybe he's a maniac.  And like I said, I would not believe someone who does this and says oh I hit k instead of l.  Because K is kiss.  My opinion.  Suck it up.  Or file a player complaint.  It's perfectly in your right to do so.  Let the Imm's handle it.  If they think it went to far because of your typo, they will email or talk to those players.

People mess up in game all the time.  And who says he died?  Evidently he wasn't in a populated area with guards.  Or the CODE would have killed him.  It's silly to say otherwise.  I'd say if his character -is- still alive.  He got off lucky.  That's the trade off of doing aliases like that in my book.  Sure you can type kill gith faster...that if I type it out...but well...if you typo...that's you.  Personally I just deal with the mess ups.  And I type the commands out.  That way if I mess up...I mess up.

I've had a warrior who tried to cast a spell because I had an alias I accidentally typed.  I explained it off...and everything was fine.

EDIT: And I mean I explained it IC.

[Bebop]

I'm surprised nobody's mentioned this, but what if they just plain didn't believe you?

Look at it from the other person's perspective. How likely is it you actually aliased k to kill? I mean, that's just plain stupid. It might easily have looked to them like you attacked them, chickened out, and tried to blame it on OOC crap, and that has happened before.

I think this is the most likely explanation.

If the target didn't die, and the attacker immediately fled and said OOCly that it was a mistake, why would the target not believe the attacker? What would he be trying to achieve by attacking and fleeing? There's no motive.

Say they don't know each other?  And attacking someone out of nowhere?  That means your a maniac.  Maybe he's a maniac.  And like I said, I would not believe someone who does this and says oh I hit k instead of l.  Because K is kiss.  My opinion.  Suck it up.  Or file a player complaint.  It's perfectly in your right to do so.  Let the Imm's handle it.  If they think it went to far because of your typo, they will email or talk to those players.

People mess up in game all the time.  And who says he died?  Evidently he wasn't in a populated area with guards.  Or the CODE would have killed him.  It's silly to say otherwise.  I'd say if his character -is- still alive.  He got off lucky.  That's the trade off of doing aliases like that in my book.  Sure you can type kill gith faster...that if I type it out...but well...if you typo...that's you.  Personally I just deal with the mess ups.  And I type the commands out.  That way if I mess up...I mess up.

I've had a warrior who tried to cast a spell because I had an alias I accidentally typed.  I explained it off...and everything was fine.

EDIT: And I mean I explained it IC.

lol That is like saying that I could walk up right now and and start shooting at you point blank "on accident."  I could not unintentionally just walk up to you and start hitting you and over and over and over again, shouting FLEE FLEE.  IG the code makes this possible.  It makes it possible for someone to unintentionally cause coded damage due to input by a keyboard.

This is a game.  Yes, it is perfeclyt feasably in a game to make an out of character mistake.  An out of character mistake should have nothing to do with IC reprecussions.

If a character accidentially unarmed hits someone doing so completely out of character, disengages and comes back and says whoa so sorry.  That is a typo and has nothing to do with any kind of role play.  If you choose to take an OOC type and turn it into an IC reprecussion because you just want to.  That's lame.

Yes, if you make an IC blunder like fucking someone over or pissing someone off or role playing attacking someone role play accordingly.  But your character has nothing to do with things that are not role played, like a typo on a keyboard.  You should not enact IC consequences over an OOC error.  Leave IC consequences for IC errors.  Just because something happens codedly doesn't mean that all OOC understanding should be lost on the situation because it can be.

[Twilight]

People like to compare Arm to a book.  Its a book without editing.  IMO if it happens in game, unless it is an obvious bug, or there is some sort of immortal intervention, or you are interacting with an immortal, it happened.

Maybe I'm just jaded because I've played Gamma DIKU for about 15 years.  But k doesn't do kill anymore for a reason.  The Imms changed it to avoid these situations, specifically.  If you bypass this safety feature, you are, IMHO, agreeing to what happens to you in the game because of it.

[Rhyden]

Tough call.

I've seen and made several ooc mistakes before. Some people roll with them, others make clear their mistakes. Either way is cool. I say, when in doubt, give the benefit of the doubt to the other player.

[Barzalene]

Some ooc mistakes like psiing or talking instead of thinking I'll role with. But something that has no ic explanation I'd ooc Sorry. I would say ooc this is an ooc occurrance. Please disregard.

[Shoka Windrunner]

Some ooc mistakes like psiing or talking instead of thinking I'll role with. But something that has no ic explanation I'd ooc Sorry. I would say ooc this is an ooc occurrance. Please disregard.

I'd agree with you.  With if he had kissed whoever he was talking to.

Or pissed instead of whatever.

But if you attack someone...the problem with that...is you don't know someone's IC explanation for it.  Or their OOC explanation for it.  So you can either assume they are not really trying to kill you...or you can sit there and wonder if they were, but they forgot to draw their weapons.

So...there you go.

[Malken]

I felt bad for the OP and was ready to side with him until I read that he aliased K to 'Kill', I mean.. COME ON.

[Synthesis]

As a newb, I accidentally backstabbed my Sergeant's inix while attempting to backstab a yompar lizard.

If I had been forced to deal with the IC consequences of attempting to shank my boss's mount in the middle of a mission, I probably would've told everyone involved to go fuck themselves, and I probably wouldn't still be playing this game.

If someone goes OOC and claims that something was a typo (e.g. k instead of l), a misdirect (e.g. wrong hooded figure), or a temporary lapse in judgment (e.g. "Whoops, this character doesn't really know the difference between an Al'Seik and a Jul Tavan."), I always give them the benefit of the doubt.

I expect the same in return.  If someone were to insist upon pursuing a storyline initiated by such a mistake, I would be sorely, sorely tempted to come up with an equally implausible IC justification for stabbing them in the face.

[Nyr]

I think most players should/will be reasonable about this and won't expect someone to roleplay something unrealistically.

If a player makes a COMMAND typo that affects the game and acknowledges it and corrects it (let's say they hit someone, stole something), then they should be given the benefit of the doubt.  If you have a problem with this, wish up with specific details--and if no response within the matter of time detailed by "help wish," use the request tool and file a player complaint.  We'll look at it, and it's usually more obvious to staff members what actually went on.

If a player makes an emoted/spoken typo and it looks obvious, give the player the benefit of the doubt, even if they don't notice they wrote something wrong.  Anyone getting uppity over "emote pees into your eyes deeply" should chill unless the emote was preceded by pants removal or followed by an offer to clean your character's face for a few 'sid.

If a player ends up killing another player's character over a typo, resurrection requests will not be granted. 
You will have to deal with THIS particular breed of OOC mistake IC, unfortunately.

When characters die in Armageddon MUD, there is no resurrection. Only if at least two senior staff members agree that the death occurred directly as the result of some major bug, or other exceptional circumstances, can the character be resurrected. Deaths caused by link-loss, lag, typos, the callousness of other players, and rampant stupidity do NOT fall into the category of exceptional circumstances.

[Rahnevyn]

Not to contradict Nyr, but don't worry, I do believe resurrections can be requested in situations where players do things like accidentally invoke the crim code and get someone stomped by a horde of half giant soldiers (which is sort of just another kind of typo).

[Nyr]

Indeed--I had forgotten about crimcode deaths like that. 

EDIT:  It really, really, really depends on exceptional circumstances, as defined in the helpfile. 
I can't go over every scenario and why it probably would or would not be granted (both because I am not a senior staffer that would weigh in and because I do not have the time).

[Tisiphone]

Not to contradict Nyr, but don't worry, I do believe resurrections can be requested in situations where players do things like accidentally invoke the crim code and get someone stomped by a horde of half giant soldiers (which is sort of just another kind of typo).

Is this a change in policy? Because...I've wished up for just that reason specifically, and the res request was denied.

[Rahnevyn]

Not to contradict Nyr, but don't worry, I do believe resurrections can be requested in situations where players do things like accidentally invoke the crim code and get someone stomped by a horde of half giant soldiers (which is sort of just another kind of typo).

Is this a change in policy? Because...I've wished up for just that reason specifically, and the res request was denied.

The policy hasn't changed - it depends on circumstances. It takes an Overlord and an HL together to approve a resurrection, so as an ST I don't feel comfortable stating policy on it; all I wanted to clarify with my post was that you can request one in such situations and we'll look at it. I didn't want anyone to get discouraged or scared of losing their PC to a totally unintentional or OOC death.

[Tisiphone]

Hmm. Okay.

[Qzzrbl]

Some ooc mistakes like psiing or talking instead of thinking I'll role with. But something that has no ic explanation I'd ooc Sorry. I would say ooc this is an ooc occurrance. Please disregard.

I'd agree with you.  With if he had kissed whoever he was talking to.

Or pissed instead of whatever.

But if you attack someone...the problem with that...is you don't know someone's IC explanation for it.  Or their OOC explanation for it.  So you can either assume they are not really trying to kill you...or you can sit there and wonder if they were, but they forgot to draw their weapons.

So...there you go.

Which is why it was cleared up in the OOC Channel with something along the lines of, "wtf omg bbqkitten, that was a typo, had 'k' aliased to 'kill' like an idiot and missed the 'l' a little.".

So.... Their character has no IC explanation for it, because it simply wasn't meant to happen. So since it's an accident, I wouldn't imagine you'd need an IC explanation for it. And their OOC explanation was right there. A mistake. If you really need any more explanation for it than that then just.... Jeeze.

[Maybe42or54]

My own personal feelings if you accidently attacked me, then said OOC "you didn't mean to do that." Then I would agree with you. I am not an NPC. The "Code" is not logical. I am. I am a human. Humans Make Errors. I'm not going to hold you accountable when you wanted to kiss me in the dark room, but you accidently killed me.

[Zalanthan]

Considering I've lost a character to another player's typo I don't have much sympathy for someone incurring harm through their own typo. 

[Yam]

Considering I've lost a character to another player's typo I don't have much sympathy for someone incurring harm through their own typo. 

Marked for termination. Expect response squad within 1-3 business days.

[Bluefae]

     Ah, the ol' "typo" issue, how I love thee.  In the three or so years I've played here, I've never had anyone NOT accept an OOC "Sorry, mis-target." on emotes, followed by a quick correction.  Perhaps "kill", having hard-coded consequences, is more difficult to deal with?  Your hypothetical, Q., would be one of those situations where I really wouldn't know what to do, and would look to other (presumably senior) players for guidance if they happened to be there.
     My instinct is to say OOC mistakes are an OOC event, and ergo shouldn't be part of our shared IC reality.  However, after a situation eerily reminiscent of this:

Not to contradict Nyr, but don't worry, I do believe resurrections can be requested in situations where players do things like accidentally invoke the crim code and get someone stomped by a horde of half giant soldiers (which is sort of just another kind of typo).

Is this a change in policy? Because...I've wished up for just that reason specifically, and the res request was denied.

The policy hasn't changed - it depends on circumstances. It takes an Overlord and an HL together to approve a resurrection, so as an ST I don't feel comfortable stating policy on it; all I wanted to clarify with my post was that you can request one in such situations and we'll look at it. I didn't want anyone to get discouraged or scared of losing their PC to a totally unintentional or OOC death.

     - I'm now torn.  It was explained to me that the event would stand, just as if I had typed "hit kank" instead of "hitc kank".  I came up with an IC justification for the unfortunate event (schizophrenic episode) and reluctantly moved on.
     I know this post doesn't provide an answer, because I don't have a good one.  In fact, I don't know that there -is- a blanket answer.  I'm a big believer in building up trust with other players, so that you and them can emote out all those cool scenes that are pretty much impossible if all that's going on is 'flee;flee;flee' or the like.  I guess a case-by-case evaluation is the best I can come up with.
     In any event, I hope it works out for ya!   

[Maso]

"emote pees into your eyes deeply"

Oh Krath. I can't stop laughing. I want to see this happen IG.

[Reissata]

I'm guilty of accidentally punching an NPC. Got beat up for it.

But hey! Do what I did and make a cover-up story, an excuse. Go with it. That's how I solved it. Now my PC is known as the girl who accidentally falls into people fist-first.

I just figure those kind of typos are just things we all have to deal with. I'm not the first to say it.

[Tuannon]

Depends on the nature of the Typo..

A command typo like kill, simply roll with it. If you can ICly convince whatever you hit by accident that you weren't trying to kill them, lucky you.

If it is something like spoiling a command emote or mispelling a name, I just ignore it and play on.

Even sitting at the wrong table is usually okay if you are quick about getting back up.. _I_ have a small 'notice timer' on things that my character is not actively looking for.

[Barzalene]

If it's a command typo like kill and you hit someone that you would never hit, for no reason, why are you rolling with it?

[Karo]

I've got it!

'kiss' could be changed to 'kitten' so if you did 'k' or 'ki' by mistake, you could simply get a message only for you along the lines of 'thinking of kitten again?'

It would be very funny, and would prevent odd situations by typoing k instead of l.

On the other hand people could simply learn to type.  I've yet to ever type 'k <thing>' instead of 'l <thing>' in my sevenish years of playing MUDs.

As for the OP.  If you stopped -really- quickly I'd personally take it as a mistake, and get on with life.  It sucks that the person forced it to IC, and you could easily get a staff involved and point to the lack of IC reason or background support for the action.  Of course I really like the whole 'I tripped and hit you by mistake' IC option.

And as for the OP's -actual- question, I hate it when OOC things get translated to IC things.  Likely the most common one that affects me is logging off.  I hate having to come up with some IC reason to log off when in the middle of something big (Like a clan hunt or some such).  This really sucks if your in a military type clan (like Byn) and they ICly treat it as you being lazy or slacking or some such because you have a life OOC.

[Tisiphone]

And as for the OP's -actual- question, I hate it when OOC things get translated to IC things.  Likely the most common one that affects me is logging off.  I hate having to come up with some IC reason to log off when in the middle of something big (Like a clan hunt or some such).  This really sucks if your in a military type clan (like Byn) and they ICly treat it as you being lazy or slacking or some such because you have a life OOC.

Underline mine.

The underlined part should never happen. I would treat it as valid reason to complain to staff; it has been stated NUMEROUS times that people should not be penalized for logging off unless obviously doing it for IG benefits, and even that's hazy.

[Lakota]

If something of this nature really did happen to you OP, then I feel for ya. Personally, I wouldn't mind rolling back the clock over a mistake of this nature. We'd get a laugh out of it and continue as we were. However, since your mistake was revolves around the code, and not specifically a typo in, for instance, a 'say,' I think it prudent to leave it up to the player on the other end of the screen until staff weighs in.

As a couple others have said, roll with it - you might be surprised, and highly entertained, at the results.

[Karo]

And as for the OP's -actual- question, I hate it when OOC things get translated to IC things.  Likely the most common one that affects me is logging off.  I hate having to come up with some IC reason to log off when in the middle of something big (Like a clan hunt or some such).  This really sucks if your in a military type clan (like Byn) and they ICly treat it as you being lazy or slacking or some such because you have a life OOC.

Underline mine.

The underlined part should never happen. I would treat it as valid reason to complain to staff; it has been stated NUMEROUS times that people should not be penalized for logging off unless obviously doing it for IG benefits, and even that's hazy.

Hehe, you mixed up underline and strikethrough.

I think one of the biggest problems is coming up with why no one has seen you in an IG month.  Always annoying when people ask IG 'so where have you been the past month' and you want to say 'well, I had to work late, go to a movie, and spend time with family, so I haven't been on Arm' and instead you have to come up with something like 'I was... in a tavern besides the one you where in.'  Once again especially becomes odd when your in a military organization and you just randomly wandered off for a month.

On that note, I decided to make a new thread instead of derail this one more.  http://www.zalanthas.org/gdb/index.php/topic,31498.0.html

[jcljules]

This is even worse when its an NPC forcing you to take typos IC.... NPCs are unreasonable twink-killers