onSpawn?

[Sonic]

I was wondering if anyone could tell me how the onSpawn command works. I'm trying to make a box that when it spawns another box that one spawns another box and then that one spawns another box, repeat ad ininitum until the whole thing is filled and the scene crashes. Is that possible, and if so how? I haven't used Thyme in over two years so I'm a bit rusty.

[electronicboy]

onSpawn should do that, I've not looked into it myself, but the onspawn code obviously has to be set by a code spawning the object for it to run "onspawn".

If that makes sense in my sleep deprived state

[Sonic]

So it would be possible to make a grey goo style end of the world box?

[Someone Else]

Try something like this:

Code: Select all

onSpawn = (e)>={
  scene.addBox({
    pos := pos
    size := [1, 1]
    onSpawn := onSpawn
  })
}

However, (I'm guessing, not tested- this might crash immediately) this will spawn one box per frame (100 per second, at default sim.frequency), which will take a while to crash Algodoo.
So instead, this code:

Code: Select all

onCollide = (e)>={
  scene.addBox({
    pos := e.pos
    size := [1, 1]
    onCollide := onCollide
  })
}

Might work just a little bit better. It also solves the problem of having to spawn the box to run the code to spawn the next one- each frame, each box will collide with quite a few of the others, so the number of boxes increases very, very fast. I'm not sure on the exact nature of the shape of a plot of the number of boxes versus time (Not sure if it's exponential or something steeper), but the result will be a crashed Algodoo very soon after the original box touches something.

As for "great goo"- I'm not acquainted with that, but (making a random guess as to what you're going after) I'd recommend something to do with either counters in postStep scripts or finite timeToLive and onDeath scripts - you might be able to adapt the code I used in this scene for your purposes:

Proliferati­on

Someone Else

Rating:
Filesize: 11 kB
Comments: 1
Ratings: 1

[jon_joy_1999]

gray goo (not great goo, as the OP said) is a hypothetical end-of-the-world scenario involving nanotechnology in which out of control self-replicating nanobots consume all matter on earth while replicating themselves. the term "grey goo" doesn't indicate color or texture, but instead that the nanobots capable of this might be less inspiring than crabgrass

[Someone Else]

gray goo (not great goo, as the OP said) is a hypothetical end-of-the-world scenario involving nanotechnology in which out of control self-replicating nanobots consume all matter on earth while replicating themselves. the term "grey goo" doesn't indicate color or texture, but instead that the nanobots capable of this might be less inspiring than crabgrass

Sounds a bit like the recursive explosives I made a while back (inspired by gmowebster's recursive bomb)...

Explosive Testing Facility

Someone Else

Rating:
Filesize: 143.74 kB
Comments: 9
Ratings: 7

[Sonic]

Try something like this:

Code: Select all

onSpawn = (e)>={
  scene.addBox({
    pos := pos
    size := [1, 1]
    onSpawn := onSpawn
  })
}

However, (I'm guessing, not tested- this might crash immediately) this will spawn one box per frame (100 per second, at default sim.frequency), which will take a while to crash Algodoo.
So instead, this code:

Code: Select all

onCollide = (e)>={
  scene.addBox({
    pos := e.pos
    size := [1, 1]
    onCollide := onCollide
  })
}

Might work just a little bit better. It also solves the problem of having to spawn the box to run the code to spawn the next one- each frame, each box will collide with quite a few of the others, so the number of boxes increases very, very fast. I'm not sure on the exact nature of the shape of a plot of the number of boxes versus time (Not sure if it's exponential or something steeper), but the result will be a crashed Algodoo very soon after the original box touches something.

As for "great goo"- I'm not acquainted with that, but (making a random guess as to what you're going after) I'd recommend something to do with either counters in postStep scripts or finite timeToLive and onDeath scripts - you might be able to adapt the code I used in this scene for your purposes:

Proliferati­on

Someone Else

Rating:
Filesize: 11 kB
Comments: 1
Ratings: 1

I can't seem to get your code to work. It keeps telling me it can't compile it.

[Someone Else]

Try something like this:

Code: Select all

onSpawn = (e)>={
  scene.addBox({
    pos := pos
    size := [1, 1]
    onSpawn := onSpawn
  })
}

However, (I'm guessing, not tested- this might crash immediately) this will spawn one box per frame (100 per second, at default sim.frequency), which will take a while to crash Algodoo.
So instead, this code:

Code: Select all

onCollide = (e)>={
  scene.addBox({
    pos := e.pos
    size := [1, 1]
    onCollide := onCollide
  })
}

Might work just a little bit better. It also solves the problem of having to spawn the box to run the code to spawn the next one- each frame, each box will collide with quite a few of the others, so the number of boxes increases very, very fast. I'm not sure on the exact nature of the shape of a plot of the number of boxes versus time (Not sure if it's exponential or something steeper), but the result will be a crashed Algodoo very soon after the original box touches something.

As for "great goo"- I'm not acquainted with that, but (making a random guess as to what you're going after) I'd recommend something to do with either counters in postStep scripts or finite timeToLive and onDeath scripts - you might be able to adapt the code I used in this scene for your purposes:

Proliferati­on

Someone Else

Rating:
Filesize: 11 kB
Comments: 1
Ratings: 1

I can't seem to get your code to work. It keeps telling me it can't compile it.

That may be, I haven't tested it- although, which code are you referring to, exactly, and where did you put it?
Both of the above scripts are intended to go into a geom (not the console)- when I say

Code: Select all

onCollide = (e)=>{ <insert code here> }

I mean that the onCollide variable should be set equal to "(e)=>{ <insert code here> }" by replacing the "(e)=>{}" that was already in onCollide with "(e)=>{ <insert code here> }"; or drop "<insert code here>" between the curly braces in "(e)=>{}".

Oh, wait, I see what I did. I forgot the semicolons, and made a few other syntax errors. Time to test these scripts!

Code: Select all

onSpawn = (e)=>{
  scene.addBox({
    pos := pos;
    size := [1, 1];
    onSpawn := onSpawn
  })
}

This code seems to spawn the next box in the same frame as the previous one- proving that onSpawn scripts act instantaneously, and causing my Algodoo to hang. It didn't crash (I force-quit before it did- but I waited a while before I did that), but I ran it in Linux through Wine, so I don't know what would happen on another computer.
I didn't actually see any of the spawned circles- I triggered the script, and Algodoo was never heard from again. The screen did not update, aside from when Ubuntu darkened the screen to indicate that the program wasn't responding.

Code: Select all

onCollide = (e)=>{
  scene.addBox({
    pos := e.pos;
    size := [1, 1];
    onCollide := onCollide
  })
}

A dozen boxes appeared (that I could see- probably more hidden behind them), then Algodoo hung for about fifteen seconds, then crash. An actual, program-closes-itself crash, not the infinite loop of the previous script. (Exponential Growth for the Win!)

I've also put together a scene based off the scene in my previous post, in an attempt at creating world-eating goo.

Proliferati­on 2

Someone Else

Rating:
Filesize: 15.59 kB
Comments: 0
Ratings: 1