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

[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.