Unsure if this is a child who's simply too ignorant to understand anyone's two cents of the topic, or if this is some actual concern.
I will assume the latter.
"Hacking on ROBLOX involves exploiting a glitch in the ROBLOX client. There is no possible way to hack the report system or block requests. Where is your evidence of people doing so, anyway?"
Or server side via an exploit by finding a hole in ROBLOX's security and messing around with how the stuff works and calls other stuff. You interrupt that and inject your own code in, yada yada yada, that's why PlayStation is always down.
Client side might as well be ignored, because unless you have a .dll (which ROBLOX has stuff in place to discriminate very extremely, since the whole 2011 thing.), the very best you can do is make shiny cool material retextures which ROBLOX doesn't care about, or removing your own Exit button.
Maybe you can play around with stuff, but either way each ROBLOX update would get rid of it all, and you would have to patch that version, and then that will get replaced in mere minutes for some tiny update, and so on, and so on.
(source: experiences with messing around with the Mass Effect 3 content, then calling the better modders every time my texture mods broke. rip in piece 4K texture mods.)
Additionally, hacking can't really be stopped.
Using the most efficient method to do anything causes a ton of possible exploits,
Using the most inefficient way costs the proper experience of the user.
You have to min/max and hope the player is happy.
For example, you can do:
"
print() = print()
x = Hello World"
while script.Disabled = false do
print(x)
end
"
and that would solve the exploit of changing print() to some other function. (Well it wouldn't but there's a better way to do that, I don't remember how.)
This means if there's someone hacking server-side to change print() to destroy() in that tick the script runs, then your script will still work fine.)
so yeah
|