Jump to content

Sadi89

Very supportive Vintarian
  • Posts

    5
  • Joined

  • Last visited

Sadi89's Achievements

Wolf Bait

Wolf Bait (1/9)

2

Reputation

  1. Yeah I was trying to get away from the emotionally charged posts with that in the first place. Gives me the mixed signal I was being viewed the same way with my topic.
  2. Im was very confused today that my thread was "deleted" and now this complete different string of posts was in its place which seemed like a big amalgamation that were all melded together it seems. It also has my thread title [Regarding the impact of the crashcode put into ConfigLib and the needed clarification and explanation of the code for layman understanding] for some reason, so someone must have liked that. It is a bit jarring having saved a hyperlink to my thread and landing in something completely different, with the same title but a different owner and having to search 34 pages for my responses. Defeats the whole purpose of my intention having a clear dissection of the code and its true impact on the players. That felt really, not cool. my whole discussion is now buried so to speak.
  3. Thank you for clearing this up. The way I understand it now is that it looks for specific wording of "type names" which I think is part of the code instead the names of the mods. so for example if I would make a magic mod and name one of my spell funtions "KillAura" it would probably trigger a response because it thinks its a cheat? ------- Nearly 14 minutes to stop someone from destroying a MP world is quite long and feels like the person doesnt care if the cheats are actually used in favor to hide the tool. ------- Ok, will look into the claims of altering the logs more. It seems though this was a communication error and one can argument that the tool hiding its own presence by crashing the main game as "blaming other mods/the game" in a broad sense. As removing one mod would magically make it work again. First off, thank you for the detailed answer I prob post some follow up questions once I read through again. 1. You mentioned a second timer that reacts to "nonprintable characters in their name" does this refer to other alphabets like russian or chinese or what does a nonprintable character entail? 2. How does the character attack itself? Didnt know that function existed in the game. also seems more like an annoyance than a crash. 3.ok another post confirming no alteratiosn to the logs, it was probably a broad generalisation that led to this misunderstanding then.
  4. okay so take this with a grain of salt since I'm not proficient with programming. Please confirm my following understanding. Enumerates all assemblies loaded into the application's AppDomain. --> scans all game files loaded? but does not look through the pc's files Fingerprints loaded assemblies using hard-coded CRC32 values. knows hash values of certain mods and has them saved on a list to detect them when looking through the loaded mods ---> targeted specifc mods the author deems "bad". possibility of false positives? what is it looking for exactly? can we have the list? Performs an additional heuristic check for obfuscated assemblies by measuring the percentage of type and member names shorter than three characters. When its detection conditions are satisfied, schedules execution after a pseudo-random delay. --> reads like it look for shortened values in the code, like instead of the variable named caveindexmultiplier its just named "ab". a simple way to hide what the specifc part of code is about to the untrained eye. Does not sound bad and sounds more like a privacy filter. It feels like looking through a code block and flagging it if a lot of short variabels are found - it flags it. --> second part is about how the dll then proceeds to crash the game after a random length of time when one of the two search methods gave a positive reading, which is maybe good for keeping it hidden but doesnt really help people getting abused by said cheats if the crash can take several minutes to execute. What is the time frame coded into the dll? Deliberately modifies unrelated internal Vintage Story client state in ways capable of causing crashes, disconnects, broken networking, corrupted UI state, and other intermittent failures. Silently catches and discards exceptions throughout the detection path, making the resulting failures substantially more difficult to diagnose. --> Those alterations can cause crashes, disconnects, networking problems, UI problems, and other unpredictable behavior. Not just simple crashes --> hides/alters error logs to make you unaware what caused said DCs networking issues or crashes, blaming other mods, server owners, you ISPs or your own hardware. So this is how it is presented to me at this point which does not line up with the official statement.
  5. Hello, I never posted on the forums since I never had the need to since the few questions I would need an answer for was always answered in the discord. But since neither onReddit nor on the discord I have had any progress on my query I will post my reddit response to the official statement reddit thread here. Fore ease of conversation I will post it in text here as well: So I want to use this thread and get to the core of the problem. I want every capable person to look into the code sincerely and honestly so we can all come to a conclusion on the real impact, since in the current state it is unsatisfactory. I dont want people to dismiss it outrigth as "it didnt affect anybody" but I also dont want people to blame everything on it either.
×
×
  • 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.