Author Topic: GUI / Script transferring  (Read 2380 times)

"This server has a custom client on RTB. Would you like to download it?"
>Yes
>RTB automatically installs the add-on



What's so hard about this? A possible feature in RTB5?

"This server has a custom client on RTB. Would you like to download it?"
>Yes
>RTB automatically installs the add-on



What's so hard about this? A possible feature in RTB5?
It's hard to release GUI add-ons, especially crude and unpolished ones, on RTB for individual servers. So I'm not going to do this instead of my original plan.

Imagine that this is what the server transfers without you knowing and you actually agree -


//crash.GUI
crash();




Or even worse it could create a folder with a client.cs and description.txt which packages the function or runs a loop to detect when you press the activate button when you change your activation key, get input from the key1 - key4 boxes and send it to a webserver.

It's a security risk because even if you let them view the code, not all Blocklanders know about torque script.

you could even save client mods that crash save injections to things like your avatar prefs so everytime you run blockland it's still running, key log your auth key

maybe if the commands were super limited only to things like poping dialogs and clientcmds, but the problem is rtb already has this, except it's got a hugely limited amount of gui elements

It's hard to release GUI add-ons, especially crude and unpolished ones, on RTB for individual servers. So I'm not going to do this instead of my original plan.
But I did it a couple months ago.
If you don't want it to get denied, then put effort into it.

maybe if the commands were super limited only to things like poping dialogs and clientcmds
This reminds me of something else.

How about an advanced web system where client mods need to be reviewed, but the only factor is they need to work and not be hostile.

How about an advanced web system where client mods need to be reviewed, but the only factor is they need to work and not be hostile.
This would not work, for 4 reasons:
•The moderators may not know how to script properly.
•Nobody who is a good scripter might sign up to moderate.
•There are infinite ways to hide code inside an add-on.
•The moderators could be corrupt.
« Last Edit: October 12, 2013, 06:16:15 PM by hammereditor² »

"This server has a custom client on RTB. Would you like to download it?"
>Yes
>RTB automatically installs the add-on



What's so hard about this? A possible feature in RTB5?

Yep, this is the only sensible option. It's fairly trivial for me to do and I'd rather the community have something well thought out, safe and nicely implemented than some ramshackle attempt like whatever's being done here - so I'll shortlist it for a new RTB feature.

"This server has a custom client on RTB. Would you like to download it?"
>Yes
>RTB automatically installs the add-on
Yeah, this seems like a perfectly good option. And it'd make servers with custom gui's much nicer since you won't have to find the mod, install it, and restart Blockland and all

This would not work, for 4 reasons:
•The moderators may not know how to script properly.
•Nobody who is a good scripter might sign up to moderate.
•There are infinite ways to hide code inside an add-on.
•The moderators could be corrupt.
So in short, just one reason:
"I could accidently hire the wrong person as a moderator."
Easily preventable.
Yep, this is the only sensible option. It's fairly trivial for me to do and I'd rather the community have something well thought out, safe and nicely implemented than some ramshackle attempt like whatever's being done here - so I'll shortlist it for a new RTB feature.
Awesome!