Well, all staff members are part of the review team and submitters are entitled to an appeal (it's in the submission rules) if something is rejected, so I don't really see the problem with Wes stepping in if he's asked to. Should definitely be the last resort, 'cause he's a busy dude, but we shouldn't be saying that Wes shouldn't be involved in NTSE.Wes shouldn't have to step in, and especially if a submitter is not getting their way. It defeats the purpose of having an NTSE mod to begin with.
I mean he did make SARP.we shouldn't be saying that Wes shouldn't be involved in NTSE.
I thought much like you did when I joined, but I've come to realize that such line of reasoning leaves resentment and hostility that broods like a cancer.I mean he did make SARP.
Again, I'm not...really qualified for this discussion. I only jumped in to attempt to be a voice of reason, but I unfortunately was not effective, as I realized this discussion was far beyond what I perceived it as. I'd like to say I know much about SARP's logistics and history both IC and OOC, but unfortunately my knowledge is near zero. I'm trying to pitch suggestions at a planetary core mining operation and I've barely scratched the bedrock layer in my own.I thought much like you did when I joined, but I've come to realize that such line of reasoning leaves resentment and hostility that broods like a cancer.
It's the difference between treating site members as a community rather than a commodity.
I'll say though, chucking myself at this brick wall has helped in that. XDIt takes time man. Lots of time and practice.
Outsource to space where no one is? Really? Almost the entire width of Yamatai away from them?@Legix , it's the NTSE Mod's job to look past those excuses and beyond the rules in order to really give the submission a proper review. If you think there's something wrong, or something is being overlooked, you bring it up like FrostJaeger is doing in the Indigo submission thread. He's posting in bricks which is a headache for me in that one, but I'm currently deliberating what options are on the table because he's brought up good points to consider. Though drama is a concern, bringing up previous, recently submitted articles which are under suspicion of being OP is perfectly acceptable, as there must be some sort of starting point for the process of cleaning up. While NTSE Mods are responsible for preventing them from being approved in the first place by looking past flimsy excuses using their own sound judgement, only this will get rid of them once such things have been approved.
Now, if you want to bring up concerns about my impartiality as an NTSE Mod however, you're free to do so. However, I do point out that it's simply good business for the Black Syndicate to 'outsource', just as Origin Industries has.
More importantly though, I do agree that Wes should have a role to play in the NTSE, but the more recent issue is the frequency at which he was called in to overrule an NTSE Mod in favor of a submitter who wasn't having their way. It's one of the reasons why Doshii Noped on out of the NTSE and isn't touching things in there anymore. As @Rizzo has said, it should be appealing to Caesar, something done very sparingly, and only after the other NTSE Mods have been consulted first, and still found unsatisfactory.
Successfully appealed rejections say more about the reviewers than the person who "didn't get their way," in all honesty. Sort of proves that the obstruction was unwarranted. I know Wes wants his trusted yellow banners to be respected, but framing it in a way that suggests the submissions should have stayed rejected is pretty off-base.I do agree, but Wes should come in only as last resort. Previously, some people have abused this by calling him in frequently to ensure they got their way. I suggest Wes only be called in when all other NTSE Mods have been called in, and were unable to come to agreement.
So, where is this supposed line? What constitutes canon RP that is okay and what isn't? If we Open RP something and then try to get it approved, what are we supposed to do when we're told 'Nope, too OP'? I know its kind of off topic, but in my mind this is where most of these complaints are coming from, which I think is overblown, but whatever, I'm biased.
I'm pro well reasoned rules that can be clearly stated. I <3 solid, simple rules systems and I think the end goal is that approvals should be a straight forward, nearly automated process. Best case scenario you could just automate approval.
I am against going by gut instinct. Everyone has a different idea about what is acceptable and if we don't have rules to define what is and is not allowed then we are not going to have a healthy RP.
Zack every time we try to patch something you are strongly against it (see thread for trying to implement the DRV3) we either have to patch things, or we have to have people over see the rules using logic and reasoning to spot problems and say no. However as this is a storytelling based 'game' and we're trying to avoid a rule set that's too restrictive the size the rules would have to be would be huge after all the patches.Pun-Pun is the reason patches and updates exist. It is not an intended part of DnD, and it was fixed in later versions.
Which is to say here: If there is a problem with the rules, then fix the rules.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?