/tg/Station 13

Byond account and character name: Jdpowercool / Roswell Pain
Banning admin: Host?
Ban type (What are you banned from?): All TG servers, apparently.
Ban reason and length: CID Randomizer (?) / Permanent
Time ban was placed (including time zone): 08/11/2015 (I don't think this is true... I've been playing for a bit and it just disconnected me and gave me the aforementioned ban message.)
Your side of the story: I read up about it and I think this is a known issue with the servers, possibly? I've only been banned once before (can confirm via searching forums) and I haven't even played in months. I don't even think I've gotten into any trouble in the past week or so that I've been playing, so I doubt it was a recent ban? I'm not sure, really.
Why you think you should be unbanned: I'd like to be at least given a reason, or if it is really an issue with the servers autobanning people occasionally like that thread mentioned, it'd be really cool to have it resolved! Thanks for reading :D

No, this one is intentional.
You started using a CID randomizer dll on 2013-12-08.
Remove it.

I'm.. uh, honestly, I don't think I did. I've been playing SS13 almost since 2013 iirc, and I've played TG for well over a year prior to this without any CID issues and stuff. I've played goon and a bunch of other servers as well without issues like this, and I definitely haven't had related issues before. Are you sure? If you tell me how, I can probably check to see, but I genuinely haven't fiddled with my CID. I got a new video card recently, but I've even used the same computer consistently. I've moved house a few times, I guess? And changed provider recently, but nothing three years ago.

dude you have 225 CIDs

Uh, what? Aren't I only supposed to have one?

EDIT: I did a computer-wide search for anything with CID in the name and this is all it found.
https://i.gyazo.com/c1b75cd2e650a9c6eff ... b11dd7.png

If his byond key isn't changing why would that be a problem?

It doesn't make much sense to me that someone would install a cid randomizer and then keep the same byond name.

Aren't bans normally keyed on Byond name first?

oranges wrote:If his byond key isn't changing why would that be a problem?

Because when he has over 200 random CIDs that start linking to other rampant ban evaders, it kinda looks bad to put it lightly.

Why would he install it in the first place? I don't know. Maybe he wanted to dick around on some other servers. Maybe he wanted to dick around on our server and try to get away with it.
We can't know, so its basically a no tolerance approach on the matter.

Either way this was Niknak's.

No it wasn't, it was ahammers

oranges wrote:If his byond key isn't changing why would that be a problem?

It doesn't make much sense to me that someone would install a cid randomizer and then keep the same byond name.

Aren't bans normally keyed on Byond name first?

The use of a cid randomizer basically makes it much harder to bans somebody, and usually means they used or are using an alt account to griff without the original account getting banned.

Either that or they ban evaded on other servers.

Anywho, it will show up as a file called wsock32.dll or something along those lines in c:\program files (x86)\byond\bin. it basically overrides window's internet subsystem, and watches for when the cid hash is sent to the servers, and scrambles it.

Remove it.

This case is 99% likely to be from the use of the randomizer, it fits the pattern, randomizes on new connections, but not round restarts, a legitimate issue with generating a cid would randomize only every time you start/restart byond's core or restart your computer.

A server side issue would randomize every round, even restarts.

Oh, and one of his ips was used on another account while this one was day banned.

2 and 2, meet together.

Edit: yep, Jdpowercool uses the ip XX.XX.XX.197 on the 2014-11-24, gets banned for killing borgs for no reason as non-antag, then, same day, woahfake logs on from the same ip, and gets warned for attacking the hos as CE for vaguely legit reasons.

OP hasn't responded in a few days since MSO's information that was brought to light. I'll leave this open for a day or two more and then resolving