Gems From The GDB

Reminds me of a time a friend of mine put in a resurrection request because of an event where a Guild leader attacked someone in the Folly. Apparently the bartender and the back-room guard had their shit straight and assisted the PC guild leader, but the mul decided to join the wrong side of the fight. At this point my friend had already hopped in to support his boss-- but it didn't take long at all for that mul to completely wreck shop.

Friend managed to escape the fray and holed up somewhere for about an RL hour to gather his thoughts and heal up.

Next time he went back to the bar, to shamelessly loot every dead person in there, the mul, bartender, and the back-room guard insta-bashed him when he stepped back in and was promptly aggro'd to death for daring to assist his Guild-vein-wearing-boss.

He put in for resurrection, thinking it may have been a bug that the NPCs hold aggro for so long. Explained the situation, put in logs, etc.

I think it was either Vanth or Adhira that declined the request, giving some half-assed explanation as to how the clan-npc-assist code gets screwy when two members of the same clan initiate combat (even though one was Byn and the other was Guild)-- and then followed up with some drivel that basically amounted to "everyone ICly magically forgets everybody they've ever known when a bar brawl breaks out" or some shit like that.

It was almost like they didn't even read what his request was about.

I'm not sure where I was going with that, but my point stands that broken ranks or no, the derp-ass crim-code made the world react in a way that made no real sense.

Here's another situation. A Byn squad is riding through the Mantis Valley in an RPT. A giant wyvern descends down before them, clearly staff controlled. It emotes out (poorly) and grabs one of the Bynners. The Sargeants realizing that it's staff controlled and therefore it is a 'scene', do not instantly shift to code and are sitting there, thinking on how to deal with this shit. A recruit doesnt have any of those thoughts, he just goes 'kill wyvern'. Unfortunately, there's a few more recruits with him, who jump in on the bandwagon and type 'kill wyvern as well'. Wyvern is ... a wyvern, so it kills everyone who attacked him, before the staffer manages to even react. Staffer is of course at fault, because with experience, he should know that shit like that happens and be twitchy jerky ready to fucking ... kizn sleep everyone, or whatever. But say he didnt react fast enough. Should those recruits be resurrected?

Yeah, crim-code is wonky. It's a text mud. There is no 3-dimensional space, there's no face recognition, there is no artificial intelligence. It's the whole reason why there is such a thing as Desert Training/Tactics lectures in the combat clans schedules. Call your name out if hurt/poisoned/need rescue. Dont just go "Rescue me!" Because it's a mud, and one hooded figure calling out for help does fuck all. Give out a keyword! That's the reality of a mud. Code is ... unwieldly. It's a job of a Sargeant to teach newbs on how to handle this.

I think the way the staff see it is, the code worked the way it was designed to work. Someone attacked a soldier and they got creamed, that's how it works.

I think what you're saying is (if I have my facts straight) it's inconsistent for a half-giant soldier assaulting a templar to goes unaffected by the crim code when a squad of human soldiers (you were all human right?) attack that very same half-giant soldier suffer the full effect of the crimcode as if they weren't even soldiers.

Is this about right?

If so, it would seem like a staff member of screwed up. And since poor judgement on staff's part isn't grounds for resurrection under the currently policy, they choose to enforce the policy rather than change it.

Let me say it again!

If the team really cared about the integrity of the setting and the player experience, there would be a guideline somewhere that says,

If the code acts in a way that threatens the integrity of the setting, it will be ret-conned.

Damn the current policy and the legalese that allows people to pick apart a legitimate case of staff screwing up in order to blame it on the players.

As far as silver-sleek goes, I think he was the aide to Alveron. Not one of my recruits, but still.

MY favorite line from the movie "Interstellar."

Where in your summarization is it the players' fault who lost their characters for what happened?

The day you can convince me that those players deserved the retarded IC consequences for the OOC screw-ups of people far more experienced than them that should have known better, I'll drop the issue. Also, the day you can convince me that I was to blame, like Cavaticus tried, I'll do the same thing.

It's not that I'm angry they lost their character. I'm angry because they lost it for a stupid reason that violated the integrity of the setting. Do you get what I'm trying to say? I don't care who could have done what to prevent it at this point; what I care about is why did the staff team not jump to fix an obvious miscarriage of the scenario.

Yes, things happen that aren't opportune. This falls outside those things entirely. This is the direct result of a staff policy that is not benevolent towards the players; it is instead designed to be an excuse for the staff to do nothing. If these policies are allowed to proliferate, the game will suffer more than it has.

Edit: I'm not going to approach your false equivalency. This is pure apologetics you're doing for the staff's part, whose actions are inexcusable far above and beyond the intricacies of this specific setting you are attempting to trivialize by comparing it to situations which are nothing at all alike.