Skip to content

Berserk/Morphing Konstant dice do not trigger their Mighty/Weak size changes after a berserk/morphing attack #3096

Description

@PoshFrosh

History

This is related to #1627, where it is noted that a Berserk konstant shrinks properly, but that this shrink isn't mentioned in the log.
In that issue, blackshadowshade mentions "This also needs to deal with any other skill that replaces the die, like Mighty and Weak." In #1953 there is a distinction made between "rolling into a game" and "rerolling".

Description

I've noticed a related issue that extends beyond log text into actual behavior that I'm not sure is intended:

  1. BkH() or Bkh() does not trigger the expected Mighty/Weak size change after performing a Berserk attack
  2. mkH() or mkh() does not trigger the expected Mighty/Weak size change after performing an attack against a single target die

I will give examples of 1 & 2 below using Mighty, but all of this also applies to Weak.

Example 1a: Berserk Mighty

The skills text for Berserk states Interaction with Mighty: Dice with both Berserk and Mighty skills will first halve in size, and then grow, which is exactly what is observed:

PoshFrosh performed Berserk attack using [BH(2):2] against [(1):1,(1):1]; Defender (1) was captured; Defender (1) was captured; Attacker BH(2) changed to H(1) and changed size from 2 to 1 sides because of the Berserk attack, and then changed size from 1 to 2 sides, recipe changed from H(1) to H(2), rerolled 2 => 2.

However, once konstant is added, the behavior changes:

Example 1b: Berserk Mighty + konstant

PoshFrosh performed Berserk attack using [BkH(2):1] against [(1):1]; Defender (1) was captured; Attacker BkH(2) changed size from 2 to 1 sides, recipe changed from BkH(2) to kH(1), does not reroll.

So it seems odd that konstant allows the Berserk size change but disallows the subsequent mighty size change.

Example 2a: Mighty Morphing

PoshFrosh performed Power attack using [mH(2):2] against [(3):2]; Defender (3) was captured; Attacker mH(2) changed size from 2 to 4 sides, recipe changed from mH(2) to mH(4), rerolled 2 => 1.

The log text is unclear (see #3095), but I assume what happened is that the (2) morphed into a (3) and then grew into a (4).

Again, once konstant is added, the behavior changes:

Example 2b: Mighty Morphing + konstant

PoshFrosh performed Skill attack using [kmH(2):2,(0):0] against [(3):2]; Defender (3) was captured; Attacker kmH(2) changed size from 2 to 3 sides, recipe changed from kmH(2) to kmH(3), does not reroll; Attacker (0) rerolled 0 => 0.

Again, it seems odd that konstant allows the morphing size change but disallows the subsequent mighty size change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions