It looks like the new update makes this all even better!

For me, I typically just have each of my tracks "complete" instead of piecing layers together--so I switch between fully mixed versions. The only difference is at times adding maybe one element like a melody over top. A couple of those earlier events refer to the adaptive music parts that I use, so ignore those, but that's the gist of how I do it all. The business with arrays is all for my own convenience and re-use of events, so you don't have to worry about that.

Despite the tracks being set to loop, I still re-seek them to the beginning to reset the playback time (otherwise it keeps going up). And, with how I have it set up, I just call a simple function in-game and this code will take care of it all. The adaptive stuff is much more complex, but I can still control it all with one simple function call. So once the initial setup is done, be sure to make it easy for yourself to control it all!

Okay, I do this type of transition work in my game currently and it works great. Admittedly, I saw this post really late at night and I really need to go to sleep. Tomorrow I'll screenshot some of my events and show you a little of how it's done, but a few hints until then:

Do not use Wait or any other system thing for timing. This will more times than not be at least a tiny bit off from the actual audio files in use and, as I'm sure you've noticed, tiny differences make for a big problem with audio. Instead, you should use Audio.PlaybackTime(Tag) for everything. Then, you can use Audio>Seek to for lining up your tracks. Remember, though, if you're looping a track, the PlaybackTime will keep going past the looppoint (ie, it'll count past the end of the audio file) so you'll also need to seek your guide track back to 0. Lastly, you need to recognize that the events aren't going to be absolutely accurate, but you should use correct values. So if your loops is 6.345 seconds, you should run your events when PlaybackTime is > or = to 6.345.

And, lastly, if someone sees this and is curious about how to find the most accurate timing for stuff, here's a good formula for it. If your measures are at a strict tempo, it's BeatsPerMinute/60*BeatsPerMeasure. So 144/60*4 would be 144 bpm in 4/4 time. Then, you can multiply that number by however many measures are in your track to get the loop length.

So when I get a chance tomorrow, I'll walk you through a bit more of this in greater detail with screenshots (and probably an example).

Hey, that's a big jump from the last one (and thanks for crediting me)! It looks quite robust already. Was the layout transition really like that in LttP? Either way, I'm not a huge fan of that, but overall this is looking fantastic!

I went ahead and added the sun into my game

The problem is canvas2D. Apparently, even the tiled aspect of TB's was hackish to get working in canvas2D. It's all perfectly doable in WebGL, just no one has done quite that.

Potato23 Just add inverted "key is down" conditions to your current commands. Right-click on a condition to invert it

Up is pressed

left is NOT down

right is NOT down

and do that for each event.

Yes, Potato23 that link wored.

Here's a fix for you.

I added comments to the event sheet to show you what I was doing. Firstly, I had to fix your right-facing image points. Did you know you can right-click on an image point in the image editor and apply it to the whole animation? That way, the cannonballs spawn correctly. I also set your animations to loop (it comes up on the left side of the screen in the image editor), so just change it back over there if that's not what you wanted.

Anyways, I added a private variable to your ship so the game keeps track of which way it's facing. I made sub-events to yours that change the bullet angle of motion for your cannonballs based on the direction of the ship. Remember, 0 degrees is → and it rotates clockwise from there.

Lastly, I moved your firing actions to functions so you can use the same actions for all of your events. This makes it easier to maintain stuff and not copy+paste a bunch of stuff.

This thread should have everything you need. Admittedly, it's made for the official plugin, but it should be helpful. Once you create your font, it also gives you the spacing string to use (and the example capx shows you how to do it).

Just change "Set angle" to No in the object's properties for the bullet behavior (same place you can set initial speed, etc.).

I haven't been having any issues with it (while using r225 as well). Are you importing wav files or mp3's or what?

Before you do too much, remember that if you select an object from the Objects or directly in the layout, you'll change the values of just that instance or instances. If you select it in the Project bar, it will select all of them in the game (globally) and change all of them. So there shouldn't be a much reason to duplicate a whole ton of objects when you can change the values in each of them as instances.

If you really are talking about clones/duplicates, then ignore this. I just don't want you to screw your project over by not being clear on instances. Also, make a backup.