Remove the exit command

[Prsn828]

It isn't a bug really, but I think it belongs with them. I really think the exit command needs to be removed, as the anti-Algodoo scenes have been increasing in numbers recently. It is annoying to have to remove the line of code exiting Algodoo every time you want to use it to run one of these scenes. I know it was amusing that such a clever tactic was devised, but it is really getting out of hand in my opinion.

[admin]

Not sure I understand what you mean by the "exit command".

[standardtoaster]

He's talking about executing system.exit with the command "exit"

[pixartist]

OR you just ban all users makin "anti-algodoo" scenes.. which in my eyes would be more appropriate

[admin]

No, we don't want to ban anyone. We really don't believe in negative actions (that should be obvious from the fact that Phun edition is still around, and after so much hard work we are quite sad to see such extreme views from some people who apparently seem to think they "own" Phun themselves). If we would ban people, or otherwise try to stop them from saying bad things, we would behave just like many of the big enterprises and media conglomerates do.

Actually, we much prefer to see the community helping us, when it comes to these attitudes. Thanks!

[admin]

Ok, I see the point now. Some people are using the exit command in scene files to terrorize algodoo users that load that file. Of course, that is not just showing an opinion, but sabotage. Like all kinds of behavior of this type, it is counter productive since everyone else in the community that gets affected will just hate them.

Will will take care of the exit command in some way.

[sashavol]

Here's a nice suggestion. Make a dialog box that says (This scene is attempting to close Algodoo. Proceed?) (Yes or No)

I think that would be enough to stop Anti-Algodoo scenes from closing Algodoo.

[Chronos]

Here's a nice suggestion. Make a dialog box that says (This scene is attempting to close Algodoo. Proceed?) (Yes or No)

I think that would be enough to stop Anti-Algodoo scenes from closing Algodoo.

but that box would pop up every time the action is triggered, which can be a lot maybe if you say no, it wont trigger again?

[RicH]

Or maybe have an option that disables the exit command. Or just remove it completely.

[RA2lover]

I was the "Anti-Algodoo Device" creator.

it wasn't intended to be used for scene sabotage, but just to show its possible to make a phun-only device(was a contest entry, if i intended scen sabotage, i could simply unbind LOTS of keys, bind them to do wacky commands(like spawning 1 million water particles at once), or mess up completely the commands(like setting simulation update frequency to get to a number so high it makes the simulation to crash upon playing it(something near 2^128(approximately the lowest number rounded to +inf(which deletes all non-fixated objects)) hz)).

also, i think it was a good thing for it to get deleted. that was just an example, and I also disliked the fact people used it to deny algodoo users from loading the scene. upon certain circumstances that's understandable, but only when you do not exit the program automatically, and just do a one-time warning(well... algodoo already does it for scenes made with phun, so i think its still not compreensible to make something like that). some people through, might have saved it as a phunlet for backup (or annoyance) purposes.

PS: standardtoaster, its app.exit, not system.exit
PPS:at algodoo beta testing, there was another command(Scene.SaveAs) which got disabled due to similar concerns.
PPPS: the anti-algodoo thing can be fixed by making an algodoo phun edition update, introducing laser compatibility(hovewer, when you open a scene with it, you're told that you CANNOT save it due to the fact of it having algodoo-only content), and thyme commands compatibility(in the case, i just used an exploit on an if-statement. algodoo has the Math.ToX functions, while phun edition has not. the exit command on the scenes works only on algodoo because phun edition cannot understand the device's if-statement, and, therefore, simply doesn't do anything with it
PPPPS:Gradyfitz also tried a *very close to 0 hz* refresh rate, and reported it as a bug. then emil told that a the simulation would simply make a single step every 10 billion seconds, or 317 years, and told him to wait a *long* bit.
PPPPPS :i can also make an anti-phun device easily, using only 3 objects, but i'm not going to do it, for the same reasons stated in this post.

[admin]

Thanks for clarifying. We will introduce some things to protect users from unfriendly scenes, but it is really a difficult balance between being able to do cool things and staying 100% bullet proof. The scenes with the exit() command have been removed from Algobox (Thanks Link!).

[Nxdt]

Could you have a "report anti algodoo scene" button in the algobox page so users can notify staff and other members of this scene. A red box surrouding the image of the scene would be a easy way of notifiy other uses of the hazard.

[RA2lover]

the "report" button is enough for that.

nice idea on the red borders, hovewer, it is hard to implement, and.... someone will edit his scene sooner or later - and it might still be considered an anti-algodoo scene while not being anti-algodoo anymore.

i think scene deletion should be ok.