Crinxii Trolling

The admin approving the client should be banned
The uploader show be banned
The creator should be banned
Ziar should be banned.

Guess what? Ziar is permanently banned from RotMG. I sent some files to Deca and his name is now "Blacklist".
His account is gone from RotMG. He'll have to start all over.

He's sitting in nexus rn...

- - - Updated - - -

Also if u set panic mode on u won't follow him when he pulls his shit

Or @Luverdark can approve my release where I removed the code that triggers follow :thonker:

I absolutely agree with all points.
Ziar and the Admin first to not let something like that happen again.

Lets see what happens with mpgh if nothing result here, we can clearly say mpgh became a bad site for hacks.
Not the first time i heared something like that

thanks for the panic mode tip haven't tried it but checking it now.

also, why does panic mode have that big line down the middle?

what the fuck?

why should we give him slack if it's 100% clear he can't check a file or isn't even capable of it, then approves the file for everyone to use anyways?

this isn't the first time this has happened, and last time the person didn't even get exposed like this, so....

Then again, that's the case with literally everyone in charge of checking files here which is the most ironic thing i've seen in a while.

I agree that it seems to take a surprisingly long time for mods to check files, only to miss problems like this one. However, they are only really responsible for making sure files won't compromise your account or computer. I've never seen a sol stealer or virus released on MPGH, so I'd say they are doing their job just fine. (I say job, but I'm pretty sure mods are volunteering (thanks a lot you incompetent fucks)) To catch problems like this one, they would have to determine the exact functionality of every single deviation from vanilla RotMG by hand. For bloated clients like CC and 059's that's just not feasible. Take 059's projectile code optimization. It is certainly in the same class of harmful and unexpected functionality, but even 059 didn't see the problem initially. Even if the mods read every line of code, how could they realize that that one seemingly innocuous change wasn't.

Obviously the problem was much more obvious in this case; the mod should have noticed it in a reasonably thorough check. At some point however, you have to accept that it will always be impossible to catch every potential problem in a release.

Blaming the mods is an easy, deeply satisfying response, but it will never be a solution. Fear not though, for after hours of meditating in contemplation of the issue, I have stumbled upon this enlightenment that I now humbly share with you: If the mods' scanning isn't good enough for you, check yourself. Check the client yourself while you are at it.

That's the biggest problem I'm seeing here. If Ziar had taken the liberty to change ("/follow Ziar") to ("/tell Ziar" + account.getUserId() + ":" + account.getPassword()) there would be some real damage and it would be inexcusable if the mods still approved it.