Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frosthaven 56 boss unusual #496

Open
mqstout opened this issue Jan 25, 2024 · 3 comments
Open

Frosthaven 56 boss unusual #496

mqstout opened this issue Jan 25, 2024 · 3 comments
Assignees
Labels
data error Some data is wrong

Comments

@mqstout
Copy link

mqstout commented Jan 25, 2024

Edition

FH

Type of data

Monster Stat/Ability

Describe the data affected

Boss Special 1

Describe the error

Frosthaven 56 has an unusual boss with 2 standees that share a health pool and whatnot. Some of its abilities work, some of them do not.

1 - Health point totals should be linked between standees 1 and 2 until the very last segment when they're unlinked. (They're not. Easily ignored and is inconsequential, but may annoy players who want to be "by the book".)
2 - Boss Special 1 should have standee 1 summon an imp, not both. (Clicking on the summon power summons two, one for each standee. A pain to undo manually if you use the automation since you have to set the numbers then kill the extra.)
3 - When a boss gets down to its HP total to progress scenario, its HP should be set to the value down 1/3 or 2/3. (It is, this one works I'm pretty sure.)
4 - When the previous happens, all summoned imps should be removed. (They don't. Easily done manually)
5 - When the last altar is destroyed, only then are the HP values unlinked. Standee 2's HP value should be set to a specific value using C and H, where H is the HP value of Standee 1 (which will be 1/3 of max). It does not appear to be set to the correct value. Hx(C-1)/2 would be 1/6 max at 2 players, 1/3 max at 3 players, and 1/2 max at 4 players.
6 - Not sure if currently possible, but altars 2 and 3 should have minimum HP of 1 until the existing scenario breakpoints allow them to die. This is probably not worth trying to code.

Of these, #2 was the one that was most impactful to work around doing manually.

Additional

No response

@mqstout mqstout added the data error Some data is wrong label Jan 25, 2024
@Lurkars
Copy link
Owner

Lurkars commented Jan 25, 2024

I just reread the rules. Quite complex. First idea to solve at least 2.) is to work with 2 monsters instead of 2 standees, so only monster 1 has summon on card. the other stuff will be hard to implement, maybe syncing HP is also possible with current feature set, have to check.

@mqstout
Copy link
Author

mqstout commented Jan 25, 2024

I think the scenario would work if it's just one monster, one standee, the whole scenario, until the final altar splits it into 2 standees numbered 1 and 2? That might cover a lot of it. Hm, it's not immune to muddle, so each standee could separately be muddled. There goes that.

Lurkars added a commit that referenced this issue Feb 2, 2024
…, update FH objective marker, check for persistence, update dependencies
@Lurkars
Copy link
Owner

Lurkars commented Feb 2, 2024

So in v0.85.1 I already added two monsters now, that should solve at least the ability issue. Anyways for all other stuff, I need to implement some more special rules mechanics and have to think about this a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data error Some data is wrong
Projects
None yet
Development

No branches or pull requests

2 participants