Algodoo

this is a simple Kinetic Energy Disc, Press "1" to use it

technically, it only moves due to inertia, and will eventually stop due to air friction

engine works for 0.2 second then shuts down

don't copy scenes

actually, you plagiarized. the ragdoll isn't yours

i think it's phun only.

try something like Scanimation instead of texture changes(lag)

+1 to pedroinho(pedrolff).

-note from Brazilian portuguese algodoo translator

Blue bar is just a rail, in case you want to make a sliding trebuchet. you can also change its position if you don't like it. but trebuchet's base should touch the ground

@Cedwe: the bomb is NOT recursive(it was originally, spawning fragments which spawned fragments which spawned fragments)... still, it spawns 116 circles, which is not enough to make a crash...

@logan101: I doubt you'll ever be able to simulate nuclear fission in Algodoo. ever by then, you would need the earth's computing power(including brains) to run that in an average framerate.

make it to save a string variable inside the card. prefferably the text variable. then, if you want a texture, you'll need to save the texture's texturematrix(coordinates for the texture) too

@lethalsquirl:Because i programmed the arm to do that . with enough waypoints, you could write basically anything(but that's time-consuming, and very repetitive).

@ianno: Scene was made on a PC - not sure if it works on a mac/linux/blahblahblah...
Same happened with the "Anti-algodoo device" scene, which some people(like Synthro and standardtoaster) know about the problem
if the arm is not moving, blame the PoC - they made that arm.
if the tatoo gun is the non-responding part, tell me what went wrong so that i can try to fix

use a laser with a much shorter length, attached to the poston itself. you'll need a mechanism to avoid premature piston firing, giving opposite effect. or, if you can't fix that, try to convert that engine into an astinkson engine or similar

EDIT:when spawning stuff, use := in the code instead of =

because, in thyme, := works for declaring variables(new geometries/things), = changes the variables(existing stuff), and == checks if the variable is equal to another value(If-statements). you can view more by opening the file thyme.cfg, with notepad

if you use the wrong command in different situations, it might affect other objects(namely the own object with the onX(collide/laserhit/hitbylaser) script)...
example: let's say you want to spawn an object with a different variable. in this case, self-collision(HeteroCollide, in script menu). if you use a = in the spawn script, you can end up changing the spawner's self-collision variable, causing a recursive(AKA, Fork Bomb) crash. if you use a := it will spawn the objects themselves with the different self-collision setting.
:= declares a variable
== scans a variable(Equal to if-statement infix)
= forces the variable.
when you're spawning something, you are declaring a new geometry, so, its attrubutes should also be declared.

"hello world!" is a string variable.
for a texture you could use something like "Testpicture.png".

hmmmm.... 6/10.
bad aiming system(you can get the aimer to be behind you while moving forward), and textures usage with low graphics on the other part. makes you to be distracted...

it's not 411 rpm. only the motors are, but the gun doesn't fire at that rate.

uss enterprise is an aircraft carrier.
fail

Davidz's Reactionless thruster.

yep. so simple Frank made it long ago.
http://www.algodoo.com/algobox/details.php?id=25573

bad thing it still needs invisible buttons.

done LOOOOOOOOOOOOOOOOOONG ago by RaRaMalum...
original scene link here

Low usage of scripts, but still very effective. i like this style.

well, the cloak is supposed to protect you from ANY impact, including the nuke...

well, that pretty much ends the contest there.

Well, you forgot to draw the interior of it.

and remings me of pixartist.

no, you don't need to delete the purple laser - it's a writer, intended to write the target coordinates(and any extra info i want to add) into the storage box(green one).

it's currently set to set textcolor to [x position, y position, dummy, dummy].

i tried thrust vectoring before - result = failure. might try that again later though...