-
Notifications
You must be signed in to change notification settings - Fork 1
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
support morphing twin die #41
Comments
Don't recall the issue - probably it just wasn't clear what the behavior should be. However, most likely an m(1,5) capturing a 6 would become m(6,6). But what happens if an m(1,5) captures a (2,4)? Depending on that special case, it seems like this shouldn't be hard to support. In BMC_Die::OnApplyAttackPlayer() there is this code:
In which case it would look like:
Also, at least one BM_ASSERT and BM_ERROR to remove. SECONDARY ISSUE |
IIRC, a morphing twin die doesn't behave any differently from a non-twin morphing die: the morphing die twins and un-twins as needed. |
@jl8e so m(1,5) capturing a 6 would become m(6). m(1,5) captures a (2,4) and becomes m(2,4) Is that right ? |
yes |
A button Gluttony has a morphing twin die
however the codebase doesn't allow for it
The text was updated successfully, but these errors were encountered: