Editing Hotspots or even Walk-Behinds in-game?

[Ryan Timothy B]

Is it possible to edit Hotspots or Walk-Behinds in-game?

I need to make destructible terrain similar to the Worms2 game.  Where the shotgun in that game can destroy circular sections of the side scrolling background and allow the character (worm) to walk on what was once the mountain.

I'm planning on making a Worms2 type game, and without this I don't really want to attempt it.



Now IF the Hotspots can't be manipulated with the drawing surface feature, I've been thinking about creating an array that stores the x and y coords and radius of where the weapon had hit the surface.  Then I would have the global script check to see if the character is within any of the slightly larger 'square' sections of the circles radius (with a square you wouldn't have to do the radius calculations each and every time even if the character is no where near a damaged section of the map).  Once they are, the character would interact with the new damaged section of the background.
Now this I believe I could do, I'm just hoping someone knows of an easier way that just allows you to edit the hotspots while in-game.

[Dualnames]

Is it possible to edit Hotspots or Walk-Behinds in-game?

I need to make destructible terrain similar to the Worms2 game.  Where the shotgun in that game can destroy circular sections of the side scrolling background and allow the character (worm) to walk on what was once the mountain.

I'm planning on making a Worms2 type game, and without this I don't really want to attempt it.

You mean as changing their areas? Drawing hotspots in-game? No, that is not possible, though it would be cool. Same for walk-behinds.

[Ryan Timothy B]

What a shame.

[Khris]

You don't need hotspots.
Keep a 2-color copy of the current background in a second DrawingSurface, then erase terrain on both the actual screen and the copy.
To check if there's terrain or not, use DrawingSurface.GetPixel.

[Ryan Timothy B]

You don't need hotspots.
Keep a 2-color copy of the current background in a second DrawingSurface, then erase terrain on both the actual screen and the copy.
To check if there's terrain or not, use DrawingSurface.GetPixel.

That sounds like a good idea.
Thanks Khris.  You just saved me from tons of unneeded math equations.