Fire Maltiez

[williams_482]

3 minutes ago, Stoney Hawk said:

Would you look at that. One of Mal’s janitors showed up.

This is rude and uncalled for. 

[Diff]

Yes, we know about the stability issues, that's literally what the code was designed to do. You claimed people were making claims of performance improvements. Your screenshots do not back you up. "No need to heap on made-up bullshit to dilute the actual bullshit" has always been my point.

[Stoney Martyr]

Just now, williams_482 said:

This is rude and uncalled for. 

Defending Malware dev is rude and uncalled for. Maybe he should stop sweeping. Nobody is paying him

[Stoney Martyr]

4 minutes ago, Diff said:

Yes, we know about the stability issues, that's literally what the code was designed to do. You claimed people were making claims of performance improvements. Your screenshots do not back you up. "No need to heap on made-up bullshit to dilute the actual bullshit" has always been my point.

Crashing, stability, and performance all go hand in hand. You should know that. We actually dont know what the issue was in some cases because ding ding ding obfuscated code

 

there is one person claiming better performance minus the code and two claiming worse while the code was active. Again. Try again.

 

there could be more! We’ll never know because DING DING DING obfuscated code

 

keep sweeping bud. 

Edited Wednesday at 04:46 PM by Stoney Hawk

[Diff]

Just now, Stoney Hawk said:

Crashing, stability, and performance all go hand in hand. You should know that.

 

They don't? They can be comorbid when you are writing bad code, but that general comorbidity goes out the window when you're writing code to intentionally produce certain effects. We know what his code did. We can disassemble and analyze it. Its effects were obscured but the code is not obfuscated. I'd love to have even more evidence of AI-riddled code being bad, but there is no evidence of that here in what you've presented and I couldn't find any myself when I went looking where you indicated I'd find it.

[Stoney Martyr]

8 minutes ago, Diff said:

They don't? They can be comorbid when you are writing bad code, but that general comorbidity goes out the window when you're writing code to intentionally produce certain effects. We know what his code did. We can disassemble and analyze it. Its effects were obscured but the code is not obfuscated. I'd love to have even more evidence of AI-riddled code being bad, but there is no evidence of that here in what you've presented and I couldn't find any myself when I went looking where you indicated I'd find it.

What evidence do you have? Millions of crashlogs with configlib hidden as the crash reason ? You cant see how it’s interacting if it’s intentionally hiding those interactions. We may know what it did but we cant see how it was interacting with random mod #50 from 5 months ago now can we?

 

and I dunno about you, but the fact we found out because it hit the wrong target is evidence it was bad code by default. How much you wanna bet bro asked claude “Write me code that detects and crash cheater’s games” and it spit that out. Someone smarter would have looked at actual anticheat devs and looked for certain checks and player behaviors

Edited Wednesday at 04:59 PM by Stoney Hawk

[icesharkk]

1 minute ago, Diff said:

... Its effects were obscured but the code is not obfuscated...

a distinction without meaningful difference. the code was written in a manner to obfuscated its presence during troubleshooting and investigation. 

i keep seeing people saying the code was plain so it wasnt obfuscated. no it was just missing from the public repository and sideloaded by the dev for release on moddb. thats concealment if i've ever seen it. 

[Diff]

1 minute ago, icesharkk said:

a distinction without meaningful difference. the code was written in a manner to obfuscated its presence during troubleshooting and investigation. 

i keep seeing people saying the code was plain so it wasnt obfuscated. no it was just missing from the public repository and sideloaded by the dev for release on moddb. thats concealment if i've ever seen it. 

You seem more level headed, hello.

It was missing from the public repository, it was only added during the build process and only present in the compiled releases. The code did take action to prevent itself from being spotted as the cause of the crashes, yes. It did conceal itself, absolutely.

The meaningful difference is not in the past, it's now. Now that it's been revealed, we can reliably analyze it and talk about it confidently. We can speak authoritatively on what it did, what it didn't do, what effects it had, what unintended effects were possible, and what is just breathless, uninformed speculation that people are running away with. I think you misunderstand me as trying to defend/excuse Maltiez or say that this is "better" somehow. It's not. It's just useful.

[Tyron]

Not going to allow discussions that start with the title "Fire Maltiez". Plus we don't have the capacity to moderate this flood of content. Use the other threads, discord or reddit where there is plenty of this already.