Scratch

Do not use stamping because you will need each of the bombs to have their own script. Stamping will be deperately hard to work with. Heres some suggestions: make how many bombs or pies you want that would show up on the screen at the same time, use hide and show for disappearing and reappearing.
idk if this would help but good luck 

Actually, stamping is perfect for this! All you need is a simple little script and 3 lists.

First, you'll need 2 costumes in a sprite: Bomb and Pie, in that order.
Now, make 3 lists: Type, X, and Y.
Next, a variable: counter.
Let's start off our script. We'll do this:

when gf clicked
delete (all v) of [Type v]
delete (all v) of [X v]
delete (all v) of [Y v]
forever
 clear
 hide
 set [counter v] to [1]
end

Let's start with the stamping script. We'll need to add this to the bottom of the loop:

if <not <(counter) > (length of [Type v])>>
 show
 switch to costume (item (counter) of [Type v])
 go to x: (item (counter) of [X v]) y: (item (counter) of [Y v])
 stamp
 if <touching [player v]?>
  if <(item (counter) of [Type v]) = [1]>
   delete (all v) of [Type v]
   delete (all v) of [X v]
   delete (all v) of [Y v]
   broadcast [game-over v]
  else
   delete (counter) of [Type v]
   delete (counter) of [X v]
   delete (counter) of [Y v]
   broadcast [pie-collected v]
  end
 end
 hide
 change [counter v] by (1)
end

So, our script now looks like this:

when gf clicked
delete (all v) of [Type v]
delete (all v) of [X v]
delete (all v) of [Y v]
forever
 clear
 hide
 set [counter v] to [1]
 if <not <(counter) > (length of [Type v])>>
  show
  switch to costume (item (counter) of [Type v])
  go to x: (item (counter) of [X v]) y: (item (counter) of [Y v])
  stamp
  if <touching [player v]?>
   if <(item (counter) of [Type v]) = [1]>
    delete (all v) of [Type v]
    delete (all v) of [X v]
    delete (all v) of [Y v]
    broadcast [game-over v]
   else
    delete (counter) of [Type v]
    delete (counter) of [X v]
    delete (counter) of [Y v]
    broadcast [pie-collected v]
   end
  end
  hide
  change [counter v] by (1)
 end
end

Now, we right click on the if just below the set counter block and select duplicate. Put it just above the if that you right clicked on. Repeat this process 6 times.

To add more objects, use this script:

add [1] to [Type v] //1 is bomb, 2 is pie. You can use a pick random block here.
add [0] to [X v] //X position of new object. Use pick random block.
add [0] to [Y v] //Y position of new object. Use pick random block.

You store the locations of the stamps in variables, so the screen can be redrawn at any time.  That's basically how a 1s1s project works: in the "draw" section of the script, the single sprite goes to all the locations in the screen that it needs to and either stamps itself (after switching to the right costume) or uses the pen to draw lines, etc.

Hi tree hugger!!!

amcerbu wrote:

@tree-hugger - Yeah.  You can break up a 1s1s project into a bunch of "broadcast and wait" blocks and "when I receive" hats for ease of readability, or if the 1s1s is lagging too much.  It also helps organize your code. 

If you're using a bunch of bombs, you can have a single "bombs" sprite that holds a list of x positions and a list of y positions.  At any point, it can go to (item 1 of x, item 1 of y) and stamp to draw a bomb, or any item number, for that matter.  When you have to draw the screen, you use a loop to go through all the items in x and y lists and stamp.  This usually requires the project to run in turbo mode.

Ya... I was trying to do something like that    just needed an idea of how too thanx!