It is currently 07 Jul 2021, 11:58
   
Text Size

Shandalar - Program Bugs

Unexpected (Siren's Call related?) death of a regenerating creature (fix completed)

 

I had Drudge Skeletons out. AI cast Siren's Call, forcing me to attack with everything that could. Drudge Skeletons attacked and suffered lethal damage in the battle. I had one black mana available and regenerated it. Then I saw at the start of the next turn:

http://i103.photobucket.com/albums/m156/jiansonz/Drudge%20in%20graveyard%20why_zpsg9tdhc0x.jpg

that it was now in the graveyard. It was as if Siren's Call's 'you will die if you don't attack' ability had taken effect even though the creature had in fact attacked.
I am pretty sure there was no other death effect around.

Comments

Posted by Korath » 09 Jun 2015, 19:39

Aha! I'd wondered why regenerate_target() had been patched in Manalink - you can see an annotation of the difference in src/exe_shandalar.c, line 48412. What's happening is that regeneration not only removes a regenerating card from combat, it keeps it from being flagged as ever having been in combat. The Siren's Call effect ends up thinking your Drudge Skeletons never attacked.

Posted by Korath » 10 Jun 2015, 01:05

commit 00f8c162ee6b2c00c61a046de845629f53dcb93e
Author: Korath <dgk@Dirge.none>
Date: Tue Jun 9 21:03:52 2015 -0400

[Shandalar] FIX #616: regenerate_target() sets STATE_ATTACKED/STATE_BLOCKED

Also fiddle order of ops, so tap_card() (which dispatches an event) isn't
called until after the regenerator stops attacking, blocking, and dying.

Ticket details

  • Ticket ID: 616
  • Project: Shandalar
  • Status: Fix completed
  • Component: Duel Engine
  • Project version: Ruined Tower 2
  • Priority: Normal
  • Severity: Normal
  • Assigned to: Korath
  • Reported by: jiansonz
  • Reporter's tickets: List all tickets
  • Reported on: 09 Jun 2015, 06:29
  • Last visited by Korath » 10 Jun 2015, 08:17.

Options

 

Login Form