So was working on temple run through when I noticed, there's no Big Bad this week, dunno if this has happened before, but gave me a giggle

Heh. Very strange. If I had to guess, it's probably because I've tacked on a ton of functionality to the dungeon spawner algorithms from their initial creation. Probably just some super weird oddity condition in there now that can cause this.

I tried taking a look at the code, but I can't see exactly where something like this would happen.

Since this is the first time I've heard of such an issue, I'm just going to hope it's an extremely rare bug and probably just ignore it at this point. However, if it seems to happen with somewhat frequent occurrence, I'll have to dig in and try and figure out where the issue is.

Sorry that isn't of much help, but let me know if you (or anyone else) has this happen again.

Hello, seems Aykios and the Horseman have both decided to ditch work. Got a map from my first encounter event in the south second floor dungeon and saw only 3 boss rooms (all 3 sub-bosses) but waited to see if beating them all might show/open the boss room. When this didn't work, I made sure to clear every room just to be sure and still no Horseman. I've left the dungeon both before and after beating all 3 sub-bosses as well as before and after clearing each room.


After obtaining map


After beating all 3 sub-bosses


After clearing each room

That was a fun one.~

I believe this issue should be fixed. Took a lot of digging to figure out the chain of events that led to this error lol.

Basically, when an instance is building itself, it builds a bunch of tendrils. As each tendril branches out, there's a bunch of various checks to make sure it's valid and fits the criteria. Sometimes, a tendril begins and then the script realizes it isn't going to fit, so it cancels it and undoes it. Well, there was one tiny part missing to this "undo" part lol.

As tendrils are being built, a catalogue is being built of valid rooms to place "nodes" into. Nodes are treasure chests, events, etc. A Named or Boss room is invalid to be a node as there is only one spawn point in each room - can't have more than one.

Well, during this "undo" part, it wasn't removing rooms from the potential node list. So, as it would happen, every couple hundred iterations the stars aligned (a tendril was cancelled, a Boss room ended up being the same coordinates as a cancelled tendril room, and that room was picked to spawn a node) and it replaced a Boss room with a node room. Thus, the dungeon would complete and there'd be no Boss.

It should all be fixed now and this shouldn't happen again. =)

Awesome, thank you! As for the current temple run I have, will I have to refresh next week and just not be able to complete the 4th Dungeon and get into the Crypt this week?

Link: https://www.sylestia.com/forums/?thread=105209&page=1#5 Author: Unstaeble Time Posted: 2/17/2023 at 8:58 PM Awesome, thank you! As for the current temple run I have, will I have to refresh next week and just not be able to complete the 4th Dungeon and get into the Crypt this week?

I don't have a way to really adjust an active Instance like that. However, I went ahead and just counted that zone task as complete for you. You should be able to start an Instance for the Crypt now.

Thank you!

thank you~!

off topic but how do you unlock the dungeon map like that? (I dont care about spoilers, I'm absolutely suffering with the temple)

it unlocks room by room as you encounter them- unless you find a room with an ! that prompts a "you found a map" event.
can be opened by clicking the map button here: