Escape Overlay Released [NARG]

[Nexus]

I haven't seen anything in the FAQ, so I'll just ask now since reading through 12 pages is too bothersome.  Do you have any plans for server-side regulation of the mod?  Yeah it's a great add-on, etc, etc, but you know the potential abusiveness of it, and you know that it's not "just as abusive as macros", but even more enabling for clients to spam servers with. 

That said, some server version of this add-on that would cap the number of bricks that clients can load at once, whether or not they can (in v2) copy bricks that aren't their own, and so on, seems like it would be in order.

lol, like 10 of the 12 pages are about that.

There is no real way to detect if someone is using BuildBot.
Try to write a server side code so people can only toggle their lights by typing '/light' into the chat.
How will you prevent people from just pressing the light key on their keyboard?  How will the server tell the difference since both methods tell the server exactly the same information?
The same problem exists with people trying to stop BuildBot.

[Ad Bot]

[otto-san]

Why not just make a load limit. Create a global variable with its limit like 10. The variable increases 1 number each time an individual client has completely loaded a build bot save. Once the number reaches 10, they can't load anymore. Sorry if that isn't a way im not really an advanced scripter.

it's a way but not a very efficient way of doing it.

[Katamari007]

Video's blocked in my country :(

[otto-san]

lol, like 10 of the 12 pages are about that.

There is no real way to detect if someone is using BuildBot.
Try to write a server side code so people can only toggle their lights by typing '/light' into the chat.
How will you prevent people from just pressing the light key on their keyboard?  How will the server tell the difference since both methods tell the server exactly the same information?
The same problem exists with people trying to stop BuildBot.

The only way I can think of is to make the client commandtoserver a function that asks if it has the no-buildbot mod, and if it's enabled, if it returns one, it doesn't do anything, if it doesn't return anything or if it returns zero, it'll continue.

Even then, it can be edited out of the client script. If that's the case, you can just ban them.

[Niliscro]

lol, like 10 of the 12 pages are about that.

There is no real way to detect if someone is using BuildBot.
Try to write a server side code so people can only toggle their lights by typing '/light' into the chat.
How will you prevent people from just pressing the light key on their keyboard?  How will the server tell the difference since both methods tell the server exactly the same information?
The same problem exists with people trying to stop BuildBot.

So really the only practical way of preventing abuse from it would to have a server build trust mod running?  Most certainly a "why the forget would you release this" situation.
inb4latetotheparty

[Nexus]

So really the only practical way of preventing abuse from it would to have a server build trust mod running?  Most certainly a "why the forget would you release this" situation.
inb4latetotheparty

Seriously, building in general in blockland is ultra-abusive.  That is why admins are important in servers.  Just because people have a new way to build does not mean the admins are unable to clear their bricks and ban them.  Events are much more abusive than BuildBot.

[PurpleMetro]

Seriously, building in general in blockland is ultra-abusive.  That is why admins are important in servers.  Just because people have a new way to build does not mean the admins are unable to clear their bricks and ban them.  Events are much more abusive than BuildBot.

Yeah I really don't see anything to complain about guys. I'm pretty sure Nexus won't be making it so that BuildBot will load events too so atleast thats alot of abusive power going to waste. And besides, even if noobs can use build bot to spam alot, don't tell me you admins are lazy enough to clear their bricks, kick them or even ban them. This is just ridiculous.

[Niliscro]

Seriously, building in general in blockland is ultra-abusive.  That is why admins are important in servers.  Just because people have a new way to build does not mean the admins are unable to clear their bricks and ban them.  Events are much more abusive than BuildBot.

Events are easily regulated.  And yeah, building can be abusive when users are enabled to use it in such a way that clicking a button takes full advantage of its abusive potential.  From the standpoint of dedicated servers, admins aren't always online.  It's not so much a matter of admins being lazy, but just another problem they'll now have to look out for.

If someone made a script that allowed clients to, say, rapidly fire a weapon, would you decry its abuse factor as a consequence of projectiles?  And rapidfire scripts can be prevented with robust weapon scripting; buildbot is a different matter entirely.  And while it's true that rapidfire scripts can be useful while building or copying events, it's even more true that rapidfire scripts are more often (and easily so) abused in DMs and such.  Thus, its abusive potential outweighs the benefit and you have something that is wholly abusive.

You could even go as far as to say that the duplicator is abusive, but that can not only be regulated but is limited by trust.  Once again, buildbot goes further than this.

My point here is that releasing something this abusive to the general community has nasty drawbacks.  If, like the redo add-on, this were server-sided, there would be no issues with abuse.

[Nexus]

Events are easily regulated.  And yeah, building can be abusive when users are enabled to use it in such a way that clicking a button takes full advantage of its abusive potential.  From the standpoint of dedicated servers, admins aren't always online.  It's not so much a matter of admins being lazy, but just another problem they'll now have to look out for.

If someone made a script that allowed clients to, say, rapidly fire a weapon, would you decry its abuse factor as a consequence of projectiles?  And rapidfire scripts can be prevented with robust weapon scripting; buildbot is a different matter entirely.  And while it's true that rapidfire scripts can be useful while building or copying events, it's even more true that rapidfire scripts are more often (and easily so) abused in DMs and such.  Thus, its abusive potential outweighs the benefit and you have something that is wholly abusive.

You could even go as far as to say that the duplicator is abusive, but that can not only be regulated but is limited by trust.  Once again, buildbot goes further than this.

My point here is that releasing something this abusive to the general community has nasty drawbacks.  If, like the redo add-on, this were server-sided, there would be no issues with abuse.

All your points have been previously made.  It all comes down to the fact that users have always been able to build this fast, and load saves without admins via Macros and other automated things.  BuildBot just makes something that was previously so hard and time consuming to do that no one really bothered, easy.

[flametail]

Well, although I see an obvious way to restrict this, I must say I want this script to stay.
For one, what new threat does it pose? As far as I see it, it may as well be a macro menu. All it does is rebuild things you have built.

But I like this, becuase it will remeber my events, and more compliacted work.

But seriously, I can build an event timer more destructive than this. Without any add-ons.

I vote that this stays. I'm sure you can add a way to ask the server for permission, but I want it to stay.

[Nexus]

I see an obvious way to restrict this

I declare BS

But I like this, becuase it will remeber my events, and more compliacted work.

Not events until much later in development

[PVC Potato Gun]

I declare BS

Your BS is void. You posted a break for it.

[Nexus]

Your BS is void. You posted a break for it.

It is a break for all building.

[flametail]

I declare BS

Not events until much later in development

Seriously, there is a way. With some edits.

You make the server also have to have the(or a server version) add-on.

Then, the client asks the server if it is permitted to build.

Or, just modify the script to use trusts.

[Nexus]

Seriously, there is a way. With some edits.

You make the server also have to have the(or a server version) add-on.

Then, the client asks the server if it is permitted to build.

Or, just modify the script to use trusts.

Server denies permission.

Client uses BuildBot anyway.

Where is the solution here?  Why is this even truly a problem?  The only way to stop abuse for anything is to clearbricks and ban.