Algodoo

I misread that as "Icy Look!"

I have been watching way too much BFDI lately

I think those are supposed to be balloons and clouds

Now that you mention it though, it does look kind of like that, so if I could I would suggest maybe making the balloons a bit shorter and thinning out the string quite a bit, and disabling the borders on the clouds.

I'm super immature so now I can't stop laughing.

This is cool! Would it be possible to make a scene detailing a square root algorithm? Bonus points if it works for all radicals and not just square roots.

When I saw the thumbnail all I could think of was Toilet saying "THE CORN MAN?!"

groovyOn isn't unused!

If you want to enable groovy mode, simply type "groovyOn" in the console. You can turn it back off by typing "groovyOff".

On Windows, the console is opened by pressing `. I'm not sure how to open it on MacOS and unfortunately you cannot open it on iPad.

Hope this helps!

I don't watch numberblocks because I'm too old for it but I'm sure the scene is great!

I do watch object shows like II and BFDI though!

I'm 16 though :<
Plus, I don't really find interest in shows like that anymore -- I did when I was younger though and I used to watch a show similar to Numberblocks!

I don't think hitting the computer with a hammer and pouring coca cola on it will help anything

Jokes aside, lol!

In onLaserHit, you can see where the laser hits the object with e.pos.

Hope this helps!

One of many reasons cats hate water is because it makes them feel uncomfortable and they have trouble getting it out of their fur -- fish doesn't get water all over them, so they don't hate fish!
I'm a girl so I know that getting water out of your hair is already really hard and annoying whenever I shower or wash my hair -- now just imagine if that hair wasn't just on top of your head!

Some other reasons include the fact that being wet makes you cold which is uncomfortable as well!


Hope this helps!

pretty

It appears that physics is calculated before objects are deleted by killer objects.

I actually didn't expect this because killer objects kill objects before scripts are run (hence why you can't use onCollide when an object is killed by a killer object!), so that's fascinating!

That's fine!

I could have sworn I reported myself one time for something.

Thank you!

An old Algobox user known as Kilinich (hope I spelled that right) made a solution!

It's called xfor.
Simply place this script into any object and name it _xfor:

(n1, n2, code)=>{
n2 > n1 ? {
m := (n1 + n2) / 2;
_xfor(n1, m, code);
_xfor(m + 1, n2, code)
} : {code(n1)}
}

and you're done!

Xfor loops from n1 to n2 whilst running the given code.
It still has a recursion limit, but it's almost infinite! The difference is that regular for spawns new scripts linearly (i.e. every "for" can only spawn one other "for") whereas xfor spawns new scripts exponentially (i.e. every "xfor" can spawn 2 more "xfors").

If the recursion limit was just 4, then xfor would be able to run for 2^4 = 16 iterations, while for would only be able to run for 4!

Assuming a clear stack with a recursion limit of 64, xfor would be able to run for 18 quintillion iterations, while for could only run for a puny 64!

Very deep recursion aside, xfor's iteration limit is so high that running into it would take a very, very long time.

I hope this helps! Xfor has saved me so, so much pain.

There is a catch though unfortunatey.
Xfor is slightly slower than for, and for what reason I'm not sure. It shouldn't be too bad though!

I wish you luck!
If you need any more scripting help in the future, I might be able to help! -- I will subscribe to this scene so I get notified if you comment on it again.

(Is doing that allowed Xray?)

(Also keep in mind that I'm not very smart, soo......
My code usually works but it also usually runs about as efficiently as blowing on a truck to move it)

By the way, your drawing is really nice!

I hate having ADHD!

I have wanted to make a sequel scene to this for literal months but still haven't even started because every time i start, i immediately lose interest.

I have some very, very bad memories from Scratch...
I would personally go for the reimplementation of Thyme instead -- but that's ultimately up to you!

Also, as for your keeping track of entities problem -- onLaserHit is run for each object the laser hits in order of when the object was hit!

Simply making a postStep script to create a blank table and then adding objects to it on every onLaserHit can be used to keep track of hit objects.

I hope this helps!

EDIT: I have made a simple script (well, 2 of them) that will save the entities the laser has hit into a table.

Here's the code for onLaserHit:

(e)=>{_hitObjects = _hitObjects ++ [e.geom.geomID]

And the code for postStep!

(e)=>{
"place whatever you want in postStep here";
_hitObjects = []
}

A little fun fact is that postStep appears to run before onLaserHit -- so if you pause Algodoo, the laser will still contain the list of objects!

This all assumes a table variable named _hitObjects within the object!

No problem!

Discovering the little mirror thing was really fun! For once I could look in a mirror without seeing something horrible.

That's actually pretty interesting!

I was diagnosed at a very young age (I wanna say before I was 5?) so I don't think artificial food dyes were the reason, but that is interesting to think about. I've heard that Red-40 is especially bad, but it's used all the time in snacks and drinks here.

I'm pretty sure Red-40 is supposed to exacerbate ADHD too though, plus it's just really not worth the cancer risk.
I only drink water and I don't eat processed snacks because I'm super self conscious about my body (i've been overweight almost my entire life so) and eating/drinking anything like potato chips or soda makes me feel awful for myself

On the bright side though, that means I barely consume any red 40!

I have a question I've been wanting to ask Algobox for a while by the way!

Especially here lately the vast majority of what I make on Algodoo is low quality and I just can't think of a way to fit it into a scene, and even if I did it's too low quality for me to feel good about it.

Should I maybe try sharing some of the lower quality/lower effort stuff?
I know UnityDogGaming04, one of my friends, shares pretty much everything she makes on Algodoo. Out of my last 50 phunlets, only 14 were in the algobox, spread across only a few scenes. Out of my last 50 scenes, only 8 of them are published.


At the same time though, I feel like if I start uploading more of what I make then I would basically just be flooding Algobox with garbage. :<

I already feel like the scenes i post (especially the computer scenes and some of my more recent ones) are really low quality and I don't want to pollute Algobox with bad scenes.

Thank you!
I know in the past on Algobox I was a bit umm... very egotistical and I still feel bad about it
Thank you for saying that by the way!

Also, yes, Unity is a girl!

How does the laser cut the object? This is fascinating!

I was addressing s_noonan. Sorry for the mixup!

I chronically keep Algodoo in Godmode. It makes everything easier. I honestly don't know why it's not on by default!

It's not working for me!

Nothing appears on the screen

I found the issue!

The Refresh box is trying to load an EntityID from scene.my.charID.
However, once a scene is reloaded, all entity IDs get reassigned.

To fix this, you could simply add this to the onSpawn of the character:
scene.my.charID = entityID

Hope this helps!

Nope!
HDDs work using magnetic storage and a magnetic read-write-head rather than a laser and an optical disk -- this makes them much more similar to a floppy drive than an optical drive!

This allows for far, far higher data density -- at the expense of needing some pretty incredible precision!

I half wish removable media would make a comeback. The satisfaction of plopping a CD in your computer to install a game while listening to a bunch of funny noises will never be beaten by simply clicking "Download" in Steam!