Swallowtail Festival and Henchman closes

[zeroth_hour]

So, today during a quest I encountered the villain and was going to close the Swallowtail Festival

 

1) Encounter Villain

2) Temp close Swallowtail Festival

3) Encounter Wrathful Sinspawn as part of the close and defeat it

4) Get a chance to permanently close the location (seems wrong somehow, but sure)

5) Fail the check to close the location (Failed combat against Goblin Warrior)

6) Jumps straight to villain encounter without any other chances to close

 

In any case, 6 is definitely a bug.  Whether or not 4 is a bug is something I'll have to use the rules to clarify.

 

EDIT: 4 is not a bug, as Hawkmoon points out.

Edited May 23, 2016 by zeroth_hour

[Rhygar]

Seems right. At 3) you already succeeded at temporarily closing the location. But because it's the henchman, you're given a proper attempt to close the location since the henchman is drawn from the location deck. Not summoned.

You failed the perm closure attempt, at 5) . But it's temporarily closed at 3) therefore the game swung back to the villain as per norm.

 

Edit : unless at 6, you mean there's other locations left unclosed and you didn't get to the screen where it shows you the spots you could choose to close. Then that could be a bug .

Edited May 23, 2016 by Rhygar

[zeroth_hour]

I meant that there were other location left unclosed, yeah.

[Sylvanta]

So, today during a quest I encountered the villain and was going to close the Swallowtail Festival

 

1) Encounter Villain

2) Temp close Swallowtail Festival

3) Encounter Wrathful Sinspawn as part of the close and defeat it

4) Get a chance to permanently close the location (seems wrong somehow, but sure)

5) Fail the check to close the location (Failed combat against Goblin Warrior)

6) Jumps straight to villain encounter without any other chances to close

 

In any case, 6 is definitely a bug.  Whether or not 4 is a bug is something I'll have to use the rules to clarify.

 

EDIT: 4 is not a bug, as Hawkmoon points out.

 

6 is definitely a bug.  Thanks for the report!