I'm not sure how best to explain this, but it's happened to me a few times already so I figure it's worth reporting.

Whenever I enter a boss battle (usually seems to be the Captains? Can't confirm 100% since I haven't kept track) I'll hear the boss music start, then it will start again directly after and play it in two loops about 5 seconds apart.

I can turn off the battle music with the settings, and it will silence ONE of them. The second stream of battle music, however, keeps on playing. The battle will end, and it's still playing even when I'm back on the move around and explore screen; if I have the exploration music on as well, it just plays them both at the same time. (Sounds horrible; I don't recommend it, lol)

It's easy enough to just open up a new explore window to fix it, but I still felt it worth noting.



Honestly I wish I could get this glitch to happen with the night music; I'd rather hear that one persistently if only I had the option. :P

When this happens, is it by chance immediately after another battle against a random enemy?

Not entirely sure if I got the question right, but I did try to set up a situation like what I assume you mean.

I danced around in front of the Captain until I had a random enemy encounter right in front of him, then engaged the Captain. No double-up on the music with that situation.

I'll try to keep better track of what happens beforehand from now on. I do tend to blow through things quickly (fast fingers are great) so it may well be something with how I run through.

Yea, there's a 100% verified bug where if you basically end a battle and enter another battle w/ both explore and battle music unmuted, it will start double playing and get all messed up.

Under most normal situations, you can't physically end a battle and start a new battle fast enough just randomly roaming the map with current pets. It can be done, but it's like a 1:1000 thing all players considered.

However, it's much easier to accomplish when you go from a random battle straight into a placeholder battle since you can trigger it immediately after the first battle ends.


What basically is happening code wise, is that the explore music and the battle music are essentially two separate instances and never stop. When you enter a battle, a script runs that decrements the explore music to volume 0 while incrementing the battle music to the set amount. This happens over the course of a second or so. When the battle ends, the opposite happens.

The bug is that if you trigger another music shift while the current shift is still ongoing, it gets bugged. I am not entirely sure why because I have made numerous attempts to block this - but they obviously don't work lol. It's also why I haven't gone and fixed it yet because I am honestly unsure of how to fix it. I'd have to probably rebuild it all from scratch piece by piece trying to figure it out which would be rather time consuming.

Definitely sounds like it'd be a lot of work for a minor inconvenience; I'll just re-open new windows, lol.


But if you dooooo ever happen to go back through the coding, I still like the idea of letting players pick their music! I run through things ridiculously fast so I only really hear like 2 seconds of explore, ~4 seconds of battle, 2 seconds of explore, ~4 seconds of battle... Music goes back and forth a lot so I can't really get into it unless I intentionally stop and work on other things while leaving TLG open in another tab.


Secondary possible bug? When I do blast through everything I occasionally start into a battle, and once I set my first round of attacks and hit "e" it just... kinda sits there. Music still going, but combat is frozen so I have to open up a new tab for TLG again.

>.> Is Sylestia trying to tell me to slow down?


Edit: Literally just as I went back to my explore window, I got a random battle and triggered the double-music bug on the ent guy for going too fast again. Got a laugh outta that.

When I am flying through battles like that I usually just mute the battle music and just keep the explore music going.

You also don't have to open a new tab, you can just reload the page (hit F5). Just reloading the page will fix it.


As for the other issue, I am not sure. It would definitely be a separate issue if you want to make a new thread we can discuss it there. =)