Jump to content

Regarding the impact of the crashcode put into ConfigLib and the needed clarification and explanation of the code for layman understanding


Recommended Posts

Posted

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.

Posted (edited)
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 by Stoney Hawk
Posted
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.

Posted (edited)
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 by Stoney Hawk
  • Like 1
Posted
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. 

  • Like 2
  • Thanks 1
Posted
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.

  • Like 1
  • Wolf Bait 1
Posted (edited)

FYSA Multiple threads from this forum related to the ongoing incident are now being removed without feedback by the staff.

Zaldaryon restored the removed threads. 

image.thumb.png.63c07bcecf9817b184fd5d1a20d3b2ee.png

Edited by icesharkk
Posted

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..

  • Like 7
  • Wolf Bait 1
  • Mind=blown 1
Posted (edited)

I just want a place where we can record the public statements and information so far so that it can be perused by other member of the community. there is a lot of misinformation as well as blatant minimization and spin going on.

 

and not just the cherry picked stickied PR safe stuff in the discord.

Edited by icesharkk
  • Like 3
Posted

This whole situation is really not giving me much faith in Anego. So much for caring about the players and their trust I guess unless they give an ACTUAL official response not just a response in the walled garden that is Discord.

  • Like 4
  • Zaldaryon unlocked this topic
  • Tyron locked and locked this topic
Posted (edited)

can we get a sticky on the forum for this topic with an appropriate title. while zaldaryon unlocked the original thread it did have an aggressive name and tyron has come back in and locked it again. at least it remains visible for now.

a thread with a clear title indicating the discussion is about the maltiez situation, malicious code in the moddb, and broken trust within the playerbase?

Edited by icesharkk
  • Like 1
  • Tyron locked this topic
  • Tyron locked this topic
Posted

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.

  • Haha 1
  • Confused 3
  • Thanks 1
Posted

It's not our goal to silence people, we're desperately trying to moderate a massive flood of angry content. There is also plenty of discussion on reddit and discord that is public. The forum threads are public again now. 

  • Like 15
  • Haha 3
  • Thanks 2
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.