#166755: "Monster started with bleeding token already on it"
What is this report about?
What happened ? Please select from below
What happened ? Please select from below
Please check if there is already a report on the same subject
If yes, please VOTE for this report. Reports with the most votes are taken care of in PRIORITY!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailed description
-
• Please copy/paste the error message you see on your screen, if any.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Please explains what you wanted to do, what you do and what happened
215
• What is your browser?
Google Chrome v135
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• What is your browser?
Google Chrome v135
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• What is your browser?
Google Chrome v135
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• What is your browser?
Google Chrome v135
-
• Which part of the rules was not respected by the BGA adaptation
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Is the rules violation visible on game replay? If yes, at which move number?
215
• What is your browser?
Google Chrome v135
-
• Which was the game action you wanted to do?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• What do you try to do to trigger this game action?
215
-
• What happened when you try to do this (error message, game status bar message, ...)?
• What is your browser?
Google Chrome v135
-
• At which step of the game did the problem occurs (what was the current game instruction)?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• What happened when you try to do a game action (error message, game status bar message, ...)?
215
• What is your browser?
Google Chrome v135
-
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• What is your browser?
Google Chrome v135
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• What is your browser?
Google Chrome v135
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• What is your browser?
Google Chrome v135
Report history
Move 200 :9:21:00 AM
ntwest moves the group onto a new encounter tile
andyjwest is the new first player
A Shieldbearer spawns
A Inquisitor spawns
Move 201 :9:21:23 AM
ntwest plays a combat card
Move 202 :9:33:10 AM
andyjwest plays a combat card
Move 203 :9:33:12 AM
andyjwest plays a combat card
All players have chosen their combat actions
Move 204 :9:33:22 AM
andyjwest gains 1 shield
Move 205 :9:33:26 AM
ntwest gains 1 shield
Move 206 :9:33:27 AM
andyjwest gains 1 golden shield
Move 207 :9:38:10 AM
ntwest damages Inquisitor
Combat round 1 begins
Move 208 :9:38:16 AM
andyjwest sets Shieldbearer on fire
Move 209 :9:38:32 AM
andyjwest gains 1 golden shield
Move 210 :9:38:39 AM
ntwest damages Shieldbearer
Shieldbearer gains 1 shield
Shieldbearer gives 1 shield to Inquisitor
Combat round 2 begins
Move 211 :9:43:00 AM
Shieldbearer blocks andyjwest's attack
Inquisitor attacks
Move 212 :9:43:06 AM
andyjwest blocks an attack
Combat round 3 begins
Move 213 :9:43:13 AM
andyjwest freezes Inquisitor
Move 214 :9:43:21 AM
ntwest sets Shieldbearer on fire
The group kills Shieldbearer
The group receives a gold tooth
Move 215 :9:43:52 AM
The group loots a cell
Inquisitor bleeds to death
The group kills Inquisitor
The group receives a gold tooth
The group receives a cell
The combat is over
Note back at move 130:
Move 130 :6:43:49 AM
ntwest bleeds Inquisitor
That combat ended with Inquisitor being killed by damage not bleeding.
I tracked down and fixed the reason this happened:
Your group uncovered all combat tiles in the Ramparts and there are not enough cards in the enemy deck, so the discard gets reshuffled to draw the remaining one.
When killing the Inquisitor (B3-10) for the first time, its state flags did not get erased. So when it spawned again, they were still there.
By the way, this is an oversight in game design as confirmed by the publisher. There should be enough monsters in the deck :-)
Add something to this report
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
