Minesweeper Safe on first Reveal

[Verbage]

Hey MMF2 community, I've come across a minor problem.

I want to add a power-up to my Minesweeper game that allows users to always have a first safe-reveal.

This is how I've gone about it (doesn't work):
41. (this event starts the generator Fast Loop)
+"First press event"
- Set position of "SafeRevealObject" at "Tile"
- Start loop "Numbering" "Bombs(global value)" times

43. (this event generates the bombs)
+On Loop "Numbering"
+Pick one of "Underneath_Tile"
+"Underneath_Tile" is not overlapping "SafeRevealObject"
+Number of "Bombs" < "Bombs(global value)"
-Set internal flag 0 on (Underneath_Tile flag 0 ON means bomb)

However, when I set the mine count super high, I still get a bomb on the first reveal.

[Pineapple]

I don't really understand your code, either because I'm not too smart, or perhaps because I can't see the context you're using it in.
ANyway, I did something similar in one of my games.

What I did was to put the "detector" in the center of the screen, then ran a loop checking whether or not the detector was overlapping an object or not. (looking for an open space)
If the detector was not overlapping, then I ended the loop.
If it was overlapping an object, I moved the detector 1 space then checked again.
I used a "nautilus" outward spiral pattern, which took a number of events to set up, but I think someone could set up something with trigonometry to do the same.

Alternately, you could try making a loop to set the detector to random X/Y coordinates, and stop the loop when it finally finds an open space.

[Verbage]

Well, what my goal was, was to place an object at the position of the first tile revealed. Then, in the fast loop, have it NOT place a bomb at a tile where the object was overlapping.

[Verbage]

Also, to make it clearer, the goal is it to NOT generate a bomb at the point of first touch (bombs do not generate until a tile is revealed).