Algodoo

Epic

Maybe not ultimate, but pretty dangerous. I think 8/10 will do fine.

btw: I don't know if it is because my Algodoo version is too old, but the springs were too strong (or the motors to weak) and I had to adjust the stuff.
In addition I had to redefine the white key, because I don't have backslash by default.

Not good. Just a simple killer with attraction and all collide sets.

3/10 because at least you fixed it with density +inf

How can it be Phuntastic when it is made in Algodoo?

Too huge and too weak.

NaN density also kills objects without crashing Phun.

I tried the hole in Algodoo btw and it didn't earn weight or power. Maybe it is because I am using 1.7.0 (I think), but perhaps the scene isn't uploaded or done perfectly.

+ for the skin
big fat - for the (not present) power.

e.other.liquify in a bouncy ball.

Now it works correctly

To the right? Without download I'd say counter clockwise

Because it is cutting quite a lot. Actually I wanted to use twice as many lasers, but you already see the effect by this...

Well stolen 1/10
http://www.algodoo.com/algobox/details.php?id=40000

Seriously, same tube, same pills. Only the background is different and the cap looks messed.

Interesting concept...
The thing with the combination of attracting and repelling is a little old actually and I must say it has been solved differently before via quadratic and linear gravity instead of 2 sticked balls, but you did very good scripting work inside the onCollide and especially by the spawner. The balls also appear in nice pattern btw.
I hope you agree with 9/10?

Oh, damn, I just had another look at the scene... My first comment is quite senseless, sorry dude! But yes, you are right, the system seems to be pretty stable. Maybe you can make a laserless Phun version too?

Well, not directly *YOU* made it. It is a default function that was in Phun and got passed to Algodoo. Open your console (usually F11) and type
groovyOn
and press enter. To turn off again do the same with groovyOff

How then?

It would not cut, but it still would turn the object mortal and then delete it, but as whole. In theory this should not happen, when I remember right I turned the range to +inf to prevent such.

I guess inside the engine it simply uses the absolute function to prevent glitches.

Or the traces is drawn mirrored what you can't see cuz the tracer is just a simple circle.

Does he have no cape? The flying mario in Super Mario World had one.

<removed by author, made a mistake>

Umm, where's the glitch about it?