Now that fluster is patched and printsploit only supports fluster, I will need to add support for the (new) UWP client or the Web client.
(preferably the web client)
Oh, and about the "Hyperion will just patch your unhooking method", I'll just have to get over it and find another way.
I think VEH (or something) works, but I don't know the implementation of that.
Unlike most developers for exploits, I will be sharing my source code, this willwould give me an advantage (if people actually weren't lazy and actually learned reverse engineering, programming, and Anti-Tamper bypass methods, it'd be easier)
Some people say "just go external",
but I'd like to keep it internal for as long as possible.
I am NOT going to turn this into another CE (Cheat Engine) exploit, as it has a lot of detection vectors.
Progress:

• Injector (needs to bypass Hyperion)
  • Unhooking (source)
  • Actual injection (CreateRemoteThread injector OR more preferably, Manual mapping (manual mapping is less detectable))
• New offsets OR use patterns (preferably patterns, they won't break every time Roblox updates)
• Web client
• (new) UWP client
• Update the tutorial to tell you how to update the patterns or offsets on the new client (p.s. it's going to be a pain in the ass if I don't make a dumper, not sure about if I will make a dumper)