A solid soundtrack really gets me going. I'm a music guy at heart, so if I boot up a game and it has catchy/memorable tracks from the get-go, I'll be more likely to play through it for a while.

(of course, if the game outright sucks in every other aspect, then welp.)

Yes, but it looks like your spawning method works as well (since you're spawning it at an image point at a gun).

filedropper.com/bullets Is this what you were looking for? I modified a couple of things and set the bullet's angle of motion instead of what you had before (note: the way you had it simply changed the angle of the graphic - it did nothing to the direction of the bullet itself).

The way I have it set up for my own purposes is:

On Z pressed:

-> Create object <bullet> at player.LayerNumber (player.X, player.Y)

-> Set <bullet> angle of motion to player.Angle degrees

The bolded part is what allows the bullet to have the correct angle and not always shoot to the right. You should be able to apply this to yours.

If that doesn't work (or if you've already done it like that), would you mind posting your .capx file?

This is exactly what I need. It relies on the walls themselves, which is perfect. I'll have to play with this a bit.

Thank you!

Thanks for the sample, but yeah, those "GravityZone"-like sprites wouldn't really be possible in my case since the playing field is dynamic.

In regards to your questions: the speed of the objects is set to about 60, but they could go as fast as ~250ish. They should be reasonably close to the surface (within 5-10 pixels). The objects are about 24x24 pixels, whereas the rest of the tiles are 32x32. They don't necessarily need to rotate as they go around corners. The new landforms appear out of thin air (you create them by clicking). Finally, the objects are held down by gravity (when they're on the floor; when they're following the ceiling, the gravity is set to 0).

If you (or anyone else) can think of anything that might work with that information, I'm all ears. Thanks again.

Hey,

I'm looking to make a sprite that follows the walls, floor, and ceiling (with the solid behavior) - that is, one that circles around landforms. I'm trying to do this without using external triggers that alter the direction of the sprite, as the landforms have the potential to change via adding blocks to them. See the image below for an example of what I'm looking for:

Right now I have it semi-working by using a bunch of "is overlapping at offset" commands, but this is very iffy and the sprites periodically fall off of the wall and float out into oblivion.

Can anyone think of a failproof way to make this work? I would be extremely grateful. Thanks.

just use the save and load option option .

before you leave the game layout to go to the pause layout add a save and when you exit the pause layout and go the game layout again " on start of layout load that previous save". -this goes to the game layout-

I thought of this, but what if you alter some global variables while the game is paused (e.g. change some game settings)? Won't they be lost if you attempt to reload the save file?

For instance, if I wanted to pause the game and create a menu on its own layout, how would I save the state of the first one (enemy positions, player position, variables, etc)? Thanks in advance.

That's exactly what I'm looking for. Thanks a lot!

I'm looking for a way to make text appear one letter at a time in dialogue boxes (similar to most RPGs). Right now I'm using the "Set text" function which causes the text to appear all at once, but I'd rather have it come in letter-by-letter. Any advice on how I could do this?

Thanks in advance.

i can confirm that with an official xbox controller everything works with node so maybe it has to do with drivers and unofficial game pads.

I use a Logitech controller, so that may be why. I don't have a 360 controller I can actually use to test it unfortunately, so I can only hope a fix comes along eventually.

I was on r153 for a while and only recently updated to r170. I had set up a configurable control method that worked just fine in r153 (the gamepad was detected in Firefox, Chrome, Node-Webkit, etc). However, since updating, I've noticed that Node-Webkit fails to detect my gamepad, whereas any browser will just fine. I'm just wondering if anything major has changed between r153 and r170 that would result in a sudden loss of detection while using Node-Webkit.

Thanks a lot in advance.