Jack_Black

I figured it out, guys! How to reply anyways. This here is the real logical problem I see and why I don't step into these kinds of debates beyond saying what I have to say in a concise matter, why I believe what I do, and an appeal to see eye to eye- its going to be met by some smart-ass in bad faith trying to make a nonargument, sophistry and entirely pedantic takes that attack use of vernacular over meaning and what actually happened. I'm a scientist. I don't deal with these people nor do I encounter them short of volunteering myself to the experience. We deal with facts of matter and foundationals. We do not handle those eager to abstract well and thus I choose not to participate in most of these types of drama. In this one however, coding ethics are near and dear to my heart and what Malth chose to do particularly on "feeling its right and justified- the only effective way to handle it" sees him nonperson'd in our field on a routine basis. Anego, you have hired a proven outstanding example of how to get fired doing the one rookie move beginners with an ego lack the self restraint to stop themselves from doing in the first place. Trying to have your Maltware and eat it too isn't going to end well longterm. You're losing sales.

Not sure how to reply here but I see the reply to obfuscated code was "Its not obfuscating anything- it just pointed the gun at a random mod in your crashlogs to make you think something other than itself was responsible. You wasted all those hours figuring out why a grab bag of mods was crashing because Maltiez felt he was righteous and prioritized his own ideologically driven ideal over keeping the mod out of controversial grounds. Nothing was hidden, nothing was actively attempting to hide itself in the crash logs, it's totally transparent to the enduser!" When it's not and I'm not tolerating lazy bad faith like this because I'm past my mid 30s and done with children. Ridiculously pedantic. You know exactly what's being said and what the problem is. It's not going away. The nature of the issue is trust and code that shouldn't have ran running on likely a five digit number of PCs. Dev response? "He's hired!" Worst can of worms I've ever seen get cracked open and stood beside in a while but not ever. Games good, people care about it for that reason, so this is an especially shitty situation. I won't be asking for a refund. Every time I think of this game I'll think of what I ran on my Pterodactyl panel and infrastructure, and how close to losing peace of mind I was lest it wasn't on a containerized VM and then I'll correspondingly recommend against buying this game off its own independent site and tell them the tale of Who Maltiez and his corroborating moderators were, What they were deflecting from and what the devteam decided was a character trait worth hiring, When the earliest deflections and ban waves began and Why people are so upset about it alongside why Malthiez himself claimed he did it. That should really get them to put their card details into some thirdparty site that hired the guy. My firm recommendation will always be to torrent this game now.

Hey, I'm on a phone, but could you remind me of whether or not it took over half a year of searching to find that it was obfuscating its own crash log? Of course we know it's there now. It took a long time for us to get to that point and what we got in response was a few days of getting called out on it and acting very hostile and unapologetic until it came time to give an apology less than 24 hours later to put out the fire. He hid his code to such an extent it functionally put on a blindfold and a shotgun and had a bad habit of saying "Wildcraft did it lol" in crash logs.

I never participate in this kind of thread and this kind of thread looks astroturfed or filled to the brim with people who do not recognize had he done this as a coder in 99% of positions he would be blacklisted from the industry for proving predisposed to hiding functionality because they think it's 'right'. You can put a burglar in the bank as a teller and insist because you're watching them we should by extent have inherent trust in a pattern of behavior that shows no remorse, utmost confidence in themselves and a very unfriendly face before they got gag ordered. I don't trust your burglar, and when your official PR answer dodges all the thousands of hours lost by hundreds of people to crash logs that deliberately point a finger at a non-problem in the midst of announcing he's on the team, I don't trust you either and no, I don't need to be told don't play it then. I hosted Pterodactyl VMs running the game and I'm not anymore. For such a good game, this conversation, this thread, the kind of nonargument detractions being made in the face of someone whose name would never work in coding again were this any other situation is the most massive and profound disappointment I've ever seen in a community. They defiled cybersecurity to the point they'd not be hired for being a legal liability. These kinds of things usually effect the finance sector pretty aggressively or some sort of bookkeeping- not my videogame, and its very unappreciated the importance of trust did not apply evenly here despite the liability factor being the very same for the very same reasoning- Malt is able to be ideologically motivated by his own internal debates on whats right or wrong and then apply it with deliberate intent to hide it. Stop making excuses for someone who took their prestigious career as a lying jerk and managed to get promoted to game dev because they made their dependency a pillar. If you genuinely side with him, in cybersecurity you are what's called a big fish with a picket fence- you think yourself unable to bleed or be bothered by a hole in your PC security and thats exactly why you are the big catch because when you finally learn the hard way you're likely to shift your beliefs after learning the hard way. You stand against hiring and firing of liabilities to principles every formally educated coder knows and abides by. But Maltware is an exception that deserves to he an exception to the standard response to an employee deploying unsanctioned code on thousands of PCs? Get real.