Those who know… (Magnus Night)
You can, just the overall Exploit design on the market only allows for Luau due to how unsafe C++ generally is. Most of them wouldn’t want to deal with kids getting their computers broken because they forgot how to free memory.
Indeed, it’s mainly because of that, and either way they’d have to implement JIT compilation which is not worth it at all. It would be easier to just implement arbitrary memory r/w functions to do that saveinstance thing you mentionned.
The only thing I wonder is how in the world you came up with all that ideas? How you got idea to use getfenv() for that, how you understood that using :Destroy() and .Parent = nil in combo with getfenv will hide script, and how this actually affect cheaters? Can’t they just read that data somewhere, cuz if script will continue execution, then it’s still stored somewhere?
Hey! The method of using getfenv()
to hide a script in its own environment has been around for years, I didn’t come up with it myself. It’s something that’s been known for a long time, Roblox’s documentation provides some details on it.
As for detecting SaveInstance, it’s really just a matter of “reverse engineering” figuring out what it does to the game, and looking into the code to see what’s going on. It’s honestly a LOT of trial and error too.
my methods, once again
(whos leaking these bro)
cloneref instance on autoexec which you can store in a global for later reference
only works if the autoexec in question is fast enough
What? This isn’t your method lol. I created and discovered this myself, didn’t acquire it from any “leaks”.
First of all gang , i never said “this isnt your method” secondly, i never said you got this from leaks
lastly, i meant i used this method before it got leaked, and now once its leaked its gonna get patched, good job for leaking it and getting the script developers patching it.
leaking it on the dev forum isnt gonna get anyone farther, except the developers of the script, your basically making a post telling the developers to patch it ,
and no, im not hating on you for leaking these methods, they are useful but they will be useless.
All methods eventually get leaked. Whether someone discovers this method after me or if its true others had already figured it out before me, it was bound to be leaked sooner or later.
I simply figured out and created the method myself, and have known it for a long time. I just thought it was pretty cool that you can detect SaveInstance this way, a so-called exploit that has been considered ‘fully undetectable’ for several years.
The thing is, there is no point in sharing these things with the public because they either call it useless or just won’t use it due to it being client based. Essentially the best way to share it is on a need to know basis.
You’re hurting your own game security aswell as others by leaking these things.
Yes. You do have a very good point. I probably shouldn’t of free released it, but it’s done now. Nothing I can do about it
If you mean SCRIPT developers then a fix will be rare. If you mean EXECUTOR developers then a fix will be rare. Have you not paid attention for the past year? Exploit developers don’t care about being detected
awp.gg, has patched every detection on dev forum, do not act like you know what your talking about, seliware, Synapse z, have patched multiple detections, you have 0 idea about what your talking about heres a image provided that the saveinstance script is stlil being worked on
secondly, most executors care about detections for example, velocity a executor with over 15k users, they patch detections, the thing people always say is “script/executor developers dont care” this is a STUPID statement.
allat yap just for both of them to be detected…
despite the detections existing for months
both of them still work
use ur brain sir, because its private
if it was public then it wouldve been patched!
the method is in no way private and has existed since electron v2 release
also decompilers exist???
uhh wasnt the game with awp.gg detection private? you literally told me that
and if it isnt private then name the method