Graul Ogrekin rolled effect persists in deck

[Foxoftheasterisk]

After failing to defeat a Graul Ogrekin, if returned to the deck with its effect still rolled; thus, instead of rolling a new effect when encountered again, it kept the same one.

I presume this is not intended behavior.

 

The first encounter was during another bug (Lem's turn, with the encountered card displayed on top of the deck instead of the encounter area),which may or may not be related.

 

--

Android 6.0.1 on Nvidia Shield tablet K1

PFID #EC19BBE1B715AFA6

Story mode, Heroic difficulty, trait Full Packs

No pass and play or permadeath

Party of Lem and Valeros, both on the Wooden Bridge

Lem encounter the Ogrekin the first time, Valeros the second

[mccrispy]

Yup, I've seen this happen too. It somewhat surprised me as I don't think that it's the intended effect (there's no way to track it in the physical game, so I wouldn't expect the digital implementation to do so)

[Ethics Gradient]

After failing to defeat a Graul Ogrekin, if returned to the deck with its effect still rolled; thus, instead of rolling a new effect when encountered again, it kept the same one.

From a tech perspective, here's what's going on inside the game:

 

AD3's Hechman Graul Ogrekin and Monster Ogrekin are each represented by five cards in the game.  One card is the "index" and there are four "alternates" representing each outcome for the index roll.

 

Only the index card in visible in the vault, and that is what is dealt out for play.  When one such card is encountered, a roll determines which alternate will be summoned in its place.  The index card is then banished, and the alternate is serialized and put into play.  The alternate then behaves like a normal henchman from then on, and does not revert back to an index if it goes undefeated.  It just shuffles like any other card.

 

It is more of a gameplay bug than a technical bug.  Cards are being handled appropriately by the app's known ruleset.  The alternate cards just need some additional scripting to swap them back in the event they go undefeated.

[mccrispy]

It's a technical bug because it's a logic flaw. But it doesn't really matter about the semantics of what flavour bug it is: it's a bug (a flaw in the implementation that does not do what the design is supposed to do), so it needs fixing.

[Ethics Gradient]

Of course its still a bug.  But any time those bugs extend into the actual codebase, they seem to take way longer to fix.

 

For instance, Merisiel's Inspired Dexterity issue took months to fix.  Some of it was in isolating the issue, but it looks like it required a few modifications in the game engine.  (As a downstream effect, now you roll to recharge everything after defeating the Villain..., even if you really don't care... just to be safe)

 

Patching up undesired behavior in a specific game object's scripting has like a 2-patch turnaround if you can get the dev's attention.  A recent example would be Justice Ironbriar.  As long as the underlying app code is ok, those fixes get banged out pretty fast.