Tweet
No higher up staff would ever agree to a 1-year TW ban for violating a Distension rule- especially one difficult/sketchy to prove is even being violated. It could, however, be a permanent Distension ban on both aliases.
I explained it in the previous reply. If someone doesn't play Distension, they're going to have no idea who plays using what aliases, and there is no readily available way to check that via bot/database.
This is for the same reason as above. Because there is no bot/database method of checking up on Distension aliases (at the moment). Judging whether someone has abused the assist system is obviously not an objective thing, but it's usually quite obvious as there are a few serial offenders. For the record, I have never banned a single person, although a few people have been warned via PM.
Your idea would work if bot work was done to accommodate Distension alias checking for operators, and that, admittedly, would be trivial for someone like qan. If that were the case, though, it could probably go a step farther and just automatically disallow multiple accounts to login during that Distension session going by macid/ip along with the op alias checking to catch anyone that bypasses that. To be honest, I'll suggest this to him. The rule would have to be "no aliases whatsoever" though. Now that I think of it, the sibling thing probably wouldn't matter at all if it only logged aliasing per session; what are the chances of two siblings playing Distension one after the other in the same 2-hour session? Not very likely.
I also asked him to fix the command that raises the player limit, because it could probably handle being higher. It's just a shame that he's so busy and doesn't have a lot of time to do anything Distension-related.
Look, I'll agree that the whole thing is annoying and should be against the rules. The thing is, people are bitching and whining at me to do something about it NOW, which I am powerless to do without alias checking power. I apologize for getting a bit pissy about it, but some people have just been straight up dicks about it. This alias thing wouldn't be much of an issue if the queue worked correctly (and it doesn't) and if the player limit wasn't so severely cut back. Believe me, I've been trying to get qan to work on it, but he's been showing up once a week or less and it's a pain in the ass.
Originally posted by TagMor
View Post
Originally posted by Tagmor
Your idea would work if bot work was done to accommodate Distension alias checking for operators, and that, admittedly, would be trivial for someone like qan. If that were the case, though, it could probably go a step farther and just automatically disallow multiple accounts to login during that Distension session going by macid/ip along with the op alias checking to catch anyone that bypasses that. To be honest, I'll suggest this to him. The rule would have to be "no aliases whatsoever" though. Now that I think of it, the sibling thing probably wouldn't matter at all if it only logged aliasing per session; what are the chances of two siblings playing Distension one after the other in the same 2-hour session? Not very likely.
I also asked him to fix the command that raises the player limit, because it could probably handle being higher. It's just a shame that he's so busy and doesn't have a lot of time to do anything Distension-related.
Look, I'll agree that the whole thing is annoying and should be against the rules. The thing is, people are bitching and whining at me to do something about it NOW, which I am powerless to do without alias checking power. I apologize for getting a bit pissy about it, but some people have just been straight up dicks about it. This alias thing wouldn't be much of an issue if the queue worked correctly (and it doesn't) and if the player limit wasn't so severely cut back. Believe me, I've been trying to get qan to work on it, but he's been showing up once a week or less and it's a pain in the ass.
Comment