|
| 04 Sep 2014 10:50 PM |
As many of you very well know, the biggest thing this update has broken is Script Builders.
Ive seen a few posts about it, and i see quite a few people that do not seem to understand alot about the Script Builders, and their community.
Most Script Builders, like most think, are filled with people who use scripts they find on Free Models or 3rd party sites like Pastebin, or people who do script themselves but arent very good yet act as if they are professional.
But most, isn't all, there are a few Script Builders that have a good amount of experienced scripters, that simply like scripting in a public space for a few reasons, one of the main ones to meet other good scripters, and get interesting info from those other scripters.
I have also seen another mistake, people seem to think that Script Builders should just use ServerSide scripts for their scripts. This is something most script builders have an option for, Script Builders use ServerSide scripts and ClientSide scripts, as they both have completely different uses. In other words, you cannot access ClientSide objects from ServerSide, such as the Camera, RunService for RenderStepped, Players Mouses, and more.
Meaning, the people who used to script there, now cannot run any LocalScripts that have to do with smooth animations, things having to do with ClientSide parts, or anything that has to do with the players Mouse, or renderstepped for doing things with the Players framerate.
The loadstring update makes it challenging for script builders to support localscripts, and i only know of 1 script builder that has come up with a fix, and that Script Builder is half filled with FMers(People who use scripts they did not make)
I understand that this loadstring update is a update needed, paired with another update to help with exploiters(Or so i hear), but i think there are a couple things roblox could add to make it easier for Script Builders to continue working, and exploits to still be broken.
Such as, allowing functions to be passed through RemoteFunctions, or RemoteEvents, this would allow us to send the loadstring function from the server to the client, wich exploiters could not use unless the creator had that inside their game, as exploiters cannot properly create scripts from clientside. |
|
|
| Report Abuse |
|
Seranok
|
  |
| Joined: 12 Dec 2009 |
| Total Posts: 11083 |
|
|
| 05 Sep 2014 12:31 AM |
So if I understand you correctly, you are proposing a method which the server would call to run arbitrary code on the client? This sounds like a great way to promote bad programming.
It's fine if SBs want to hack their way to running arbitrary LocalScripts. That's great. It shouldn't be built-in because then ROBLOX would be encouraging developers to use it. |
|
|
| Report Abuse |
|
|
| 05 Sep 2014 12:47 AM |
| No, what this is proposing is the ability to send functions to clients via RemoteFuctions/RemoteEvents, after this function had been sent, it would be executed by the client. |
|
|
| Report Abuse |
|
| |
Friaza
|
  |
| Joined: 26 Dec 2008 |
| Total Posts: 6229 |
|
|
| 05 Sep 2014 03:51 AM |
I'm getting script builder withdrawal symptoms, I make my Devil Fruit at a private SB and test it on friends qq
support^17 *math.huge
|
|
|
| Report Abuse |
|
|
| 05 Sep 2014 08:51 AM |
| Broke SB but didn't stop speed hacking...way to go Roblox developers... |
|
|
| Report Abuse |
|
gskw
|
  |
| Joined: 05 Jan 2013 |
| Total Posts: 1364 |
|
|
| 05 Sep 2014 10:01 AM |
Uh, I thought they patched FPS throttle. Atleast I haven't seen anybody use it...
This is a signature. Recommended username: BoringGskw |
|
|
| Report Abuse |
|