[OPEN SOURCE] anti env logger v2 (25ms/threaded confirmed)

what is an anti env logger?

an anti env logger aka env check, breaks env loggers (services that run your code in order to see what it does) by viewing inconsistencies in the environment that usually don't appear on normal executors

how do i use this?

simply copy the code, and when you go to obfuscate your code, paste it before your code, and then env loggers should no longer be able to see what your code does

why/when should i use this?

if you obfuscate your code, you'll want to use an anti env logger, as it's an added layer of security that most obfuscators don't provide

how does this anti env logger work?

i noticed during testing that env loggers seem to only run code inside of connections once just to see what it does, so i used that to my advantage, all this code simply does is see if a connection (one that's supposed to run every frame) runs twice, and waits for it to do so

why should i use this over any other anti env logger or env check?

this env logger is currently not patched as of the time of this message, it's also not comparing or checking a function or global so it will never result in less compatibility with executors, even in the future, it uses a repeat loop instead of an error to ensure the env logger breaks, and it's simple enough to learn off of

what env loggers does this work on?

currently, it's confirmed to work on .gg/25ms and .gg/threaded, and it may work on every env logger out there, but some env loggers, such as unix (.gg/ADggURGv6r), are ahead of others when it comes to patching detections