Author Topic: What was "call server command- output event"?  (Read 1783 times)

/title
it got failed, but what was it?

"this addon was failed so please tell me it's name so that i can try and find it on the internet because its not like it was failed for a reason or anything"

"this addon was failed so please tell me it's name so that i can try and find it on the internet because its not like it was failed for a reason or anything"

thignk erry dey
« Last Edit: January 19, 2014, 11:55:30 PM by Lego lad »

"this addon was failed so please tell me it's name so that i can try and find it on the internet because its not like it was failed for a reason or anything"
He asked what it was, dummy.

It's a useless script that does exactly what TB2 requested here: http://forum.blockland.us/index.php?topic=250078.0

I don't know what he's working on that requires such an add-on but here's why you shouldn't enable it without admin only events:

link removed

protip: change the image extension to zip to download the file

User was banned for this post
« Last Edit: January 20, 2014, 03:00:51 AM by Ephialtes »

That actually looks very useful.



Poor zeblote.
But that add-on looked pretty cool.


Why was he banned?

Look, I'm sorry that I had to remove the add-on you worked on but it's just not a sound design.  Anyone could build a brick that would shutdown the server or ban someone or whatever.  If you release this, kids will turn it on all the time and their experience will be made worse and they won't know what's going on. 

It's easy to blame them for turning it on but really the problem is that the design is so prone to failure that it is almost unavoidable.  Please don't fight me on this.  This would be another eval nightmare if released.

Why was he banned?
Badspot failed the add-on since people who were not admin could use the /ban command. Zeblote complained that its there fault for turning it on. Badspot said that people would download it to see what it does and it is the add-ons problem. Zebelote posted the file and said "you should have admin only events on" when people could forget or for servers where people could event. Zebelote got banned for being an starfish and trying to still insist his add-on was good.
« Last Edit: January 20, 2014, 02:06:38 PM by Bester Bageler »

Badspot failed the add-on since people who were not admin could use the /ban command. Zeblote complained that its there fault for turning it on. Badspot said that people would download it to see what it does and it is the add-ons problem. Zebelote posted the file and said "you should have admin only events on" when people could forget or for servers where people could event. Zebelote got banned for being an starfish and trying to still insist his add-on was good.
You gotta explain how posting an add-on that
  • Was requested
  • Can be extremely useful for people creating gamemodes without scripting knowledge (unable to create the wanted event, and need a solution to call a command asap without waiting for others to fulfill the request hours later)
  • Might be very dangerous if used wrongly but therefor with a clear warning to not run it unless absolutely required and admin only events turned in, together with a sample image showing a very dangerous use of the add-on


is 'being an starfish'.

is 'being an starfish'.
because if you look at his post he had a picture of the failed add-on he made that had been addressed directly by badspot to him

and then he gave a little note cleverly dropping in how to acquire the mod by changing the file extension on the image URL

So why not add restrictions in the event's coding to permanently set it to admin-only?