Jeshin
GDB Superstar
Posts: 1,516
|
Post by Jeshin on Sept 20, 2018 11:17:19 GMT -5
If they reviewed the policy, announced an update, acknowledged that it was an issue in the past but now in the future it will be resolved appropriately. I don't think people will be mad at future rezzes and instead be pleased the staff finally realized it was silly.
EDIT - To clarify I don't think there's any value in arguing about what they should have done. They had a policy. The deaths didn't follow the policy. The issue is they fix the policy to be reasonable but actually grant rezzes when appropriate. Crimcode nonsense should be appropriate. Use dissatisfaction of the past to create a more appealing future.
|
|
jkarr
GDB Superstar
Posts: 2,070
|
Post by jkarr on Sept 20, 2018 12:21:22 GMT -5
EDIT - To clarify I don't think there's any value in arguing about what they should have done. They had a policy. The deaths didn't follow the policy. how did not rezzing them deviate from the policy
|
|
Jeshin
GDB Superstar
Posts: 1,516
|
Post by Jeshin on Sept 20, 2018 12:55:34 GMT -5
They had a policy for rezzes, the deaths didn't qualify for the policy. Saying the storyteller or clan head or even the producer should have recognized that it deserved a rez (in that specific case) doesn't help because it is the policy which needs to be changed per my other posts.
|
|
jkarr
GDB Superstar
Posts: 2,070
|
Post by jkarr on Sept 20, 2018 13:52:36 GMT -5
gotcha now misunderstood what you meant before
the edit helped too
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 21, 2018 3:18:15 GMT -5
Interesting thing happened not too long ago.
A staffer was playing a role. Nobody particularly important, some red storm/rinthi smuggler. A templar ordered him to appear and they met at the gates, where the Templar ordered him to sit down and set his guard to threaten him. They chatted, some money got exchanged, some agreements made. The Templar was pleased and told the smuggler to piss off. The smuggler stood up. The Guard's threaten triggered and he attacked, the gate guards assisted, the smuggler died within one singular second. The templar hide the body so no player sees, or asked a staffer to hide it. I forget. And filed for rez. The staffer probably also filed for rez. There was a conversation between producers/admin and storytellers. Where the entirety of storyteller team were saying, "This death makes 'no' sense. Even the killer is asking to retcon it. The threaten code is clunky and unknown. The admin/producers insisted that it wasnt due to a bug and refused to rez.
Sure, they seemed extra diligent about this case, because they didnt want to show favoritism to a staffer. I dont think they ever said as much, but I think it was pretty clear. The staffer in question, also seemed to not truly care. But it was an interesting difference in a way things got approached. Storytellers main argument was "This death does not fit the story. It would not have happened in real life." While Producers/admin were "We have a policy. This death does not fit the criteria outlined in this policy."
|
|
jkarr
GDB Superstar
Posts: 2,070
|
Post by jkarr on Sept 21, 2018 6:40:58 GMT -5
There was a conversation between producers/admin and storytellers. how did u confirm this as fact its ok to say if u didnt and ur taking someones word for it but its useful for u to establish that difference
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 21, 2018 7:03:32 GMT -5
Hey, dont want to believe me? No problem at all. Your choice.
|
|
|
Post by yourvisiongoesblack on Sept 21, 2018 8:09:51 GMT -5
illumanti confirmed
|
|
|
Post by yourvisiongoesblack on Sept 21, 2018 8:37:40 GMT -5
Random, but once, before the code was produced to make characters' thirst/hunger time stop after they had been idle for so long, I submitted a rez question (I waas playing a PC who had a fairly large clan base that I had built up from the bottom), and it was approved.
The next day, I got an email saying that another Producer disagreed with the decision, and, while the rez would still remain approved, similar circumstances in the future were could not considered.
Fast forward to like 2010 or something. I still take medicine to help me sleep at night (since I have after separating from the USMC) and fall asleep with my 50 day mul/merchant in the Outer Bailey. Wake up to him dead. No rez.
I may be wrong, but I'm glad that staff seemed to put in code to make characters time out. Losing 100+ days of merchants played because of medicine creeping up on you just... sucks. Sure, "dont play Arm if you're taking that kind of medicine" seems like pretty good advice, but it's also one of the ways that I wind down... and sometimes I get sucked into stuff in-game and at times haven't been able to fight it off.
Losing 100+ days of merchant chars who branched armor crafting/before there were extended subguilds is a terrible thought. So is the thought of what happened to Ramir: you've got a badassly-statted char with friends, history with a clan, enemies, have had fun stories and are collaborating actively with other characters whose players have the same schedule as you, when BAM, some newbie troll with a club they bought from the bazaar blows off Ramir out of the water for *no reason whatsoever.*
ArmageddonMUD isn't supposed to be fair ICly. It's a major premise of the game. But if code is present that allows characters to die unrealistically, it should be changed, notices should be made to the help files, and som humanity will required.
After the death of my 50 day mul merchant, I was like, hey staff, I take medicine (I did not say why, that part of the season was that I had been sexually assaulted while working in the military), and their response was:
Look, we don't care and it's not our responsibility to do X.
What I had done in the message was politely ask to, if staff ever noticed me idle like that in the future, to please log me out, again, if they just happened to notice. I didn't order them to. I didn't throw a fit. I merely told them of a recurring OOC problem of mine and asked if they could maybe try to help me, and the response was just kinda unnecessarily rude.
Developed, codified, compassionate rules as far removed from bias or favoritism is what staff should strive for when it comes to rez policies; if the code or staff are at fault in certain situations, alternatives to rezzes, like maybe an expedited special app or stat boost might be in order. Like in Rami's case, it took him 14 IRL days to make that character, only to die in a totally frivolous way. I know they are busy, but it would have taken staff 10 minutes or less to help that player feel better about what had happened.
That's one way staff can do better when it comes to retaining players.
|
|
jkarr
GDB Superstar
Posts: 2,070
|
Post by jkarr on Sept 21, 2018 9:46:28 GMT -5
Hey, dont want to believe me? No problem at all. Your choice. thats fine but how did u confirm this as fact if u dont want to say u can say so u dont have to deflect
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 21, 2018 13:44:28 GMT -5
Random, but once, before the code was produced to make characters' thirst/hunger time stop after they had been idle for so long, I submitted a rez question (I waas playing a PC who had a fairly large clan base that I had built up from the bottom), and it was approved. The next day, I got an email saying that another Producer disagreed with the decision, and, while the rez would still remain approved, similar circumstances in the future were could not considered. Fast forward to like 2010 or something. I still take medicine to help me sleep at night (since I have after separating from the USMC) and fall asleep with my 50 day mul/merchant in the Outer Bailey. Wake up to him dead. No rez. I may be wrong, but I'm glad that staff seemed to put in code to make characters time out. Losing 100+ days of merchants played because of medicine creeping up on you just... sucks. Sure, "dont play Arm if you're taking that kind of medicine" seems like pretty good advice, but it's also one of the ways that I wind down... and sometimes I get sucked into stuff in-game and at times haven't been able to fight it off. Losing 100+ days of merchant chars who branched armor crafting/before there were extended subguilds is a terrible thought. So is the thought of what happened to Ramir: you've got a badassly-statted char with friends, history with a clan, enemies, have had fun stories and are collaborating actively with other characters whose players have the same schedule as you, when BAM, some newbie troll with a club they bought from the bazaar blows off Ramir out of the water for * no reason whatsoever.* ArmageddonMUD isn't supposed to be fair ICly. It's a major premise of the game. But if code is present that allows characters to die unrealistically, it should be changed, notices should be made to the help files, and som humanity will required. After the death of my 50 day mul merchant, I was like, hey staff, I take medicine (I did not say why, that part of the season was that I had been sexually assaulted while working in the military), and their response was: Look, we don't care and it's not our responsibility to do X. What I had done in the message was politely ask to, if staff ever noticed me idle like that in the future, to please log me out, again, if they just happened to notice. I didn't order them to. I didn't throw a fit. I merely told them of a recurring OOC problem of mine and asked if they could maybe try to help me, and the response was just kinda unnecessarily rude. Developed, codified, compassionate rules as far removed from bias or favoritism is what staff should strive for when it comes to rez policies; if the code or staff are at fault in certain situations, alternatives to rezzes, like maybe an expedited special app or stat boost might be in order. Like in Rami's case, it took him 14 IRL days to make that character, only to die in a totally frivolous way. I know they are busy, but it would have taken staff 10 minutes or less to help that player feel better about what had happened. That's one way staff can do better when it comes to retaining players.
This is the kind of thing that makes me wish we had a thread, where people whose identities are already open secret, would post request dialogues. Exposure of conversations like 'these' is what would improve the game. Not code leaks, or plot leaks, or whatever. But out in the open logs/request exchanges of staff being absolute dicks. With identities of which staff is doing it, so everyone could read and know exactly who the asshole is.
|
|
|
Post by lechuck on Sept 21, 2018 16:14:57 GMT -5
They just don't want to do any more work than the absolute minimum necessary. It's the same reason Armageddon Reborn fell apart: if it's something that can't be phoned in, it doesn't get done. Same goes for resurrections. They have literally three things that warrant a rez: staff mistakes, bugs and "OOC collusion." And even within those three stingy items, they'll do whatever they can to avoid it.
You have to die directly from the bug, not as a consequence of events that happened due to a bug (i.e. you died because soldiers killed you, not because a bug caused the soldiers to attack you, so no rez). Basically, the bug itself has to be the direct, immediate cause of death, otherwise they'll tell you that "sometimes soldiers are crooked and will kill for no reason, it's part of le #harsh world."
OOC collusion is virtually impossible to prove, and effortless to whitewash, because you just have to have a brief in-game conversation where you plan to murder someone and now it's no longer OOC. I haven't heard of anyone getting rezzed in this context since Pearl, and... that was Pearl, so enough said. This clause was created for Pearl and probably hasn't been used since.
Besides, how is two players planning a kill on AIM any worse than one player taking it upon himself to grief and troll the game out of spite? What makes communicating a kill worse than deliberately refraining from roleplaying? This is the very first of the game's core rules: Failure to roleplay can result in the removal of your character or banning from the game, but the actions you commit through non-roleplay are apparently sacred as long as you didn't collude with a buddy outside of the game? What kind of priority system is that?
Staff fuckups will be covered up by staff in order to save face--I doubt that anything short of an imm accidentally typing 'slay amos' instead of 'stat amos' would result in a rez. We've seen plenty of examples where a bullshit staff-caused death will be justified by their fellow staff if there's any conceivable way at all to contrive it, and there almost always is. They're a team and the playerbase is a different team.
On Shadows of Isildur and Atonement, I've seen people get resurrected for the following:
- The server lagged out for ten minutes, causing NPCs to kill unresponsive characters who wouldn't normally have died there. - A newly added mob was badly designed and unintentionally one-shotting people. - NPC guard getting stuck while dragging a character to jail, who slowly bleed to death from a non-fatal wound. - Inexperienced staff misjudging combat balance and loading up excessive amounts of mobs during an RPT. - Players abusing broken code to exploit in PvP, e.g. getting horses to guard/rescue them. - Players creating characters to grief-PK their previous PC's enemies as revenge for recent IC events. - Total newbies not understanding that it's a roleplaying game and randomly spraying machineguns at people in the starting area.
And many other similar things. None of these would have warranted a rez on Armageddon. You know what negative consequences there were to these rezzes? None whatsoever. Absolutely zero problems were caused by retconning absurd deaths that should not have happened and were only made possible by flawed code or non-roleplay. Letting those deaths stand is objectively worse than the brief, miniscule lapse in immersion of seeing someone die in some nonsensical way and be returned to life with an OOC explanation.
On Armageddon, I've seen people denied a resurrection in the following cases, and many others like them:
- Killed by archery spam from two rooms away in a blinding sandstorm. It was deemed plausible. - Multiplaying griefer using throwaway PCs to kill several random people in Allanak for no reason at all. - Brainfarting clanlead typing 'kick man' when trying to kick the man from a clan, causing man's death by NPC gangbang. - Templar forgetting to pardon a guy before removing him from jail and releasing subdue in front of soldiers who promptly kill him. - Starving to death while linkdead, with food in inventory. - PC A kills PC B who is still under the 2 hour grace period and respawns, speedwalks back, kills the wounded PC A.
What possible purpose is served by letting such deaths stand? Obviously if you request a rez two days later and people have held a funeral for your character, that's one thing; but how often does that really happen? Staff will routinely deny a rez on the grounds of IC integrity even when there has been no reaction yet and the death was something that would literally not have been possible in reality. Even if you get hold of staff immediately and there's ample time to move the corpse and assess the situation before anyone else has so much as entered the room, you will almost certainly be informed that you're out of luck for some arbitrary nonsense reason.
They act as if the rules are some kind of untouchable thing, and sometimes they've even acknowledged that a death was wrong but they still can't do anything because the circumstances weren't covered by these three ancient criteria written in like 1998 by people who probably don't even have anything to do with the game anymore. These rules were written before there was such a thing as VPNs, but they haven't thought to add a clause like "if the killer is multiplaying in order to mask their actions..." so when that happens, they shrug and point to the fact that it isn't covered by the rules. Or even just something simple like "if a player wilfully breaks the game's core rules while carrying out an action, the action can be retconned." Why do they act as if the resurrection rules are outside their power to change or interpret?
If I message Bob and tell him to log in because the planned hit on Joe's character will happen today, Joe will get a rez. If I log on with a different IP, create a new account, make a throwaway character and beeline to kill Joe's character, Joe will not get a rez. What?!
|
|
Deleted
Deleted Member
Posts: 0
|
Clan Caps
Sept 21, 2018 16:33:47 GMT -5
via mobile
Post by Deleted on Sept 21, 2018 16:33:47 GMT -5
Hrm.
Does anyone have any succesful rez stories that they can recall?
Last one that I can think of was a resurrection of a bynner HG.
He climbed up the shield wall, where a bug that heramided people was stuck. The idea was that he would engage it and they both would drop down the shield wall, where the rest of byn/aod were waiting.
Instead the bug didnt drop and when the HG went KO from heramide, he didnt drop either.
That HG got a rez.
|
|
|
Post by shakes on Sept 21, 2018 17:49:44 GMT -5
I think the rez rules are better stated as "You're not going to get one. Don't ask."
|
|
faroukel
Displaced Tuluki
What's a story without a villain?
Posts: 201
|
Post by faroukel on Sept 28, 2018 13:51:20 GMT -5
I find the idea of clan caps to be ass backwards when it comes to common sense.
The belief that nerfing something that's clearly 'successful' in the hope of supporting other initiatives is dumb.
Liken it to sports.
Team A is very popular and has a massive stadium that sits 50,000 people.
Team B is mediocre and has a massive stadium that sits 50,000 people.
The League decides to support Team B, by limiting the amount of fans that can attend Team A's games, limiting the amount of tickets available to put on sale to 40,000.
...
Do those 10,000 people decide, whelp, guess I better buy Team B's jersey and find me some tickets?
No. They don't. There's a variety of reasons. Team B is in a different city. Team B is shit and always loses. Team B has wack team colours. Team B is full of toxic players. Whatever.
If the League was smart, they'd look at things Team A is doing, and try to build that into the culture/make-up of Team B. If the League was really spot on, they'd look at building more teams like Team A, and moving/changing shit like Team B.
|
|