Hi @Bretticus82 - regarding this change in the latest update:
> Dungeonborn: rarer, sized to your guild instead of arriving at a fixed high ability, and it now asks rather than joining or vanishing on its own. A full hall can still take one, by releasing someone.
...I just had this scenario trigger and - the last bit didn't quite work properly.
I had a full roster of 14/14 in hall beds, plus two aspirants on the floor.
Then in clearing a dungeon, got the popup about a beast yielding, offering to join. I had the option of releasing someone, and I chose one of the full members (not one of the aspirants) to release, then asked the beast to join via appropriate button.
But then when going back to the dashboard screen I see:
> Ozara Glorywrought did not take Felosial's release well.
> 🐲 There was no bed for Gorbal the Thrice-Slain after all, and the beast was let loose back into the dark.
So - the *release* did happen, as I'm now at 13/14 in beds, 2 on the floor. But beasty didn't join.
Seems like there's a bug in the free beds check re the final joining stage? Maybe something to do with the 2 aspirants on the floor affecting the count?
Great game BTW, just reporting this bug to help improve :)
I've just made a save after the event triggered .... if it would help debug and there's an easy way for me to send it to you, please DM me.