of     2   
chevron_rightchevron_rightchevron_right

slmnemo
#140565808Wednesday, July 16, 2014 11:24 PM GMT

https://www.youtube.com/watch?v=RL_sOFlIj7s A video dedicated to explaining with evidence, watch in 720p fullscreen. --------------------------------------------------------------------------------- Okay, so the way the CE speedhack works is by removing the limit imposed by the client of 60 FPS on physics. For some smart reason, the admins didn't make the server have the final say in whether someone moves, I guess to support low end PC/IP. A fix to this is to either A: Crash clients that are above 60 FPS in physics. B: Making the server do the calculations for movement and physics. (May make ROBLOX require better PC/IP) C: Preventing hooking into the ROBLOX process. So A obviously works like if someone hits above 60FPS in physics, we crash them, but we also need a barrier just in case physics speeds up for a bit, you can have it above 60 FPS, but only for X seconds, past that and you are obviously trying to do something. X is admin decided. B is so obvious I don't know why ROBLOX didn't do this. C is also possible, but might require an anticheat, which usually costs money, and isn't viable. If I am wrong about anything feel free to correct me. I am slightly open to constructive critism, but just being like NAW THIS GUY IS BUNK and then no supporting without a reason is against the rules of this forum. Scriptable this may be, but not everyone knows about the realphysicsFPS >65 command.
SpicyBuilderclub
#140565944Wednesday, July 16, 2014 11:26 PM GMT

Support.
Kotios
#140566953Wednesday, July 16, 2014 11:38 PM GMT

This is stupid. Obviously you don't realize how many times that ROBLOX has patched speedhacking, you act like this is going to be the magic solution, but the truth is exploiters are just going to find another way, so making a thread on this forum about hacking/exploiting is just a waste of your time. Hyperbole is the single most amazing and useful word I've ever used, ever.
slmnemo
#140567452Wednesday, July 16, 2014 11:43 PM GMT

Well it puts the script kiddies who rely on leaks into a hole until the actual leakers find out about a new method. Also, that's just negative, just because I'm trying to help by preventing the current method I'm wasting time?
Kotios
#140567786Wednesday, July 16, 2014 11:47 PM GMT

Even if this gets patched, at any given time there's at least 5 different ways to do the same exploit, and even if there aren't, it doesn't take much longer than a few days for someone to find another way, and leak it. Hyperbole is the single most amazing and useful word I've ever used, ever.
Kotios
#140567981Wednesday, July 16, 2014 11:49 PM GMT

A better suggestion might be "Give more frequent punishments to people who exploit or hack." since I hardly ever see anyone get banned for exploiting or hacking. Hyperbole is the single most amazing and useful word I've ever used, ever.
slmnemo
#140568921Thursday, July 17, 2014 12:01 AM GMT

Yeah, but the reason they aren't banned is because you need evidence, and evidence requires either video footage or traces of cheating. Testing for hooking processes works, but not always. (Go search VAC) If we aren't gonna make a patch, it makes it harder for the exploiters to find a loophole which to speedhack with, and the most widespread version will be removed.
TheCriminalTurkey
#140569056Thursday, July 17, 2014 12:02 AM GMT

"A: Crash clients that are above 60 FPS in physics." crashing them could hypothetically overheat computers and break them you know what that means? ROBLOX could get sued you know what that means? ROBLOX could maybe go out of business it should just kick them instead of crashing them ~What's this madness ye spew?~
slmnemo
#140569129Thursday, July 17, 2014 12:03 AM GMT

By crash I mean end the client process. Thanks for getting me to clarify!
triode
#140569626Thursday, July 17, 2014 12:09 AM GMT

You can always Combine a process instead of hooking Hooking = Making 2 Transistors Work together in one Process Combine = Using 1 Transistor to run 2 processes, Like Threading
RuUp
#140569753Thursday, July 17, 2014 12:10 AM GMT

ok
RobuxLife
#140569847Thursday, July 17, 2014 12:11 AM GMT

"A obviously works like if someone hits above 60FPS in physics, we crash them, but we also need a barrier just in case physics speeds up for a bit, you can have it above 60 FPS, but only for X seconds, past that and you are obviously trying to do something. X is admin decided." that's a cool idea, also, I think that if your above 60 fps in physics for 15 seconds, you get kicked from the game
triode
#140570003Thursday, July 17, 2014 12:13 AM GMT

Either way ROBLOX has patched alot of speed hacking methods.
slmnemo
#140570456Thursday, July 17, 2014 12:18 AM GMT

Yeah, but not all of them, one gets patched, another is found within a month because of people with tons of time on their hands and script kiddies. Compared to dll exploits which take months to develop but are much more dangerous, I think the outbreak earlier is already gone. Speedhacks will always be around, like point exploiting, but the current speedhack was introduced in 2013 IIRC, that's way too long for a simple patch to fix.
triode
#140570603Thursday, July 17, 2014 12:20 AM GMT

thats the point hacking is nearly impossible to stop if CE was to be completely removed from ROBLOX, People would make other types of things to cheat around games. Client exploits aren't the only things out there.
triode
#140570649Thursday, July 17, 2014 12:20 AM GMT

but eh support i guess
CjGame
#140571261Thursday, July 17, 2014 12:27 AM GMT

I'm not a scripter but there is a new property added to ROBLOX Studio called FilteringEnabled. It stops the client side of users from editing server side properties, for the most part. It's complicated and you'd have to rescript your game because you can't just simply turn it on.
nobbers12345
#140571612Thursday, July 17, 2014 12:31 AM GMT

@Cj That is only for inserting scripts and such. The exploit was patched a few days ago. "script kiddies who rely on leaks" Call them skids. Braghenaflarbenabeg.
slmnemo
#140572800Thursday, July 17, 2014 12:44 AM GMT

K Also, when cheatengine is banned, only the dedicated will still exploit, because then special clients will come out, which can be countered easier.
CjGame
#140572838Thursday, July 17, 2014 12:44 AM GMT

Thanks for clarification! Support for B.
slmnemo
#140578139Thursday, July 17, 2014 1:41 AM GMT

Don quero bump bell
slmnemo
#140598451Thursday, July 17, 2014 4:53 AM GMT

By the way, did I forget the twitter pic link? If so, https://twitter.com/slmnemo/status/489546831743840256/photo/1
spacegang
#140600378Thursday, July 17, 2014 5:10 AM GMT

@Kotios You obviously don't understand. If anything, ANYTHING at all goes above 60FPS, then it's an obvious speedhacker. Another thing, you can't find another way. Changing your walkspeed won't do anything good, since games have a new feature called FilteringEnabled. Check out my channel! [https://www.youtube.com/user/dedudeism/featured]
slmnemo
#140626142Thursday, July 17, 2014 2:03 PM GMT

I keep forgetting about filteringEnabled as a function, but thanks for helping (This is technically a bump)
slmnemo
#140664513Thursday, July 17, 2014 9:15 PM GMT

Non bump

    of     2   
chevron_rightchevron_rightchevron_right