PhotriusPyrelus

Apparently this is defined as anything that makes Anego look bad. So maybe you should warn yourself, as *you* are the one making Anego look bad. If the topic needed pruning to remove mud-slinging, do that. Deleting the *entire* discussion of a topic of interest relevant to the community is an abject failure of moderation. And I sure hope you have a manager who's going to look at this with open eyes and not the apparent tribalism rife in your little fiefdom, the only possible reason I can cotton for you guys burning down so much good will to defend - let's call it what it was - a hacker. Someone who subversively puts code on your PC that you don't want on your PC is a hacker..

Seriously, do you not understand the internet or human psychology or remedial marketing? Stop silencing people with force, and silence us with an actual response addressing the problem.

Deleting a thread discussing a problem doesn't make the problem go away.

"...known about it months ago. The thing is, he told us about it." Was that before or after you hired him? Either way, you just sat on it? *Knowing* it was a powder keg just waiting to explode? Smart.

Cool. You do that. Doesn't mean you need to tell us we need to do that, too.

Yeah, just sweep it under the rug. Stop talking about it. The devs won't even have to make a response then!

This is very simple to me. Had they known all this before they hired him, would they still have hired him? If no, kick him to the curb. If yes, well then I guess for all their high talk about morals and community trust they're just as bad as EA, Micro$lop, and Nintendo. Seriously, imagine thinking trust among the dev team matters more than trust with the users. What a joke. Oh well, I guess I got my $25 of fun out of it.

Good grief, I miss the 90s and early 00s. This was the order of the day. Someone cheating on your server? Ban him. It wasn't <Developer's> job to do it for you.

Interesting. I strongly suspect (but welcome correction) that if the VS Staff had known about this before hiring him, they would not have done so. In which case, yeah, he probably should be fired or at the absolute least (I don't know about Latvian "LaBoUr PrOtEcTiOn" laws) removed from contributing code if they can't remove him from the company entirely. ...which makes it very curious to me why they're defending him. ::furrows brow::

So I'm confused, is this something he did just in his mods, or something that was added to the standard vanilla client after he was added to the dev team? Or is the issue that his "anti-cheat" code in his mods violated the rules of what mods are and aren't allowed to do?

Maybe it's not his place to do that? Maybe it's a matter for the individual server admins to address? Maybe this top-down enforcement approach needs to die in the hell that spawned it?

...what? Golly, I dunno, maybe I mean that you don't need shattering or tool durability to provoke players to go out into the world? Or - in your own words - the specific words that I was responding to and quoted: If a guy already has 3,000 iron, he doesn't care if a tool shatters; it doesn't force him to go interact with the world. If a guy can "literally get 10 stacks of iron ore in less than a day" (sound familiar? it should, it was you who said that and that post was specifically why I included 'or easily go get more'), it doesn't matter if a tool breaks. 128 bits per stack, is 1280 bits. 20 bits per ingot, that's 640 ingots. That's probably well more than enough iron for an entire play through if *all* you care about is "winning" and not building cool stuff. So please, tell me again how shattering tools and having to make the same tools over and over again "push[es] the player towards interacting more with the world and with other mechanics, aka going out into the world and gather more recources." It doesn't. That's why that excuse is old and tired. I

It was more advice for recent posts and going-forward. I don't expect you to remember which version you inspected each of these seeds going back almost a whole year.

You may want to include version numbers for the seeds, as every time something updates in world gen, seeds can change profoundly.

That's so cool! Thanks for the explanation.