#166755: "Monster started with bleeding token already on it"
Hvad handler denne rapport om?
Hvad skete der? Vær venlig og vælg nedenunder
Hvad skete der? Vær venlig og vælg nedenunder
Vær sød at undersøge, om der allerede er sendt en besked om emnet
Hvis ja, venligst STEM for denne rapport. Rapporter med flest stemmer er dem der får PRIORITET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaljeret beskrivelse
-
• Venligst kopier/indsæt fejlmeddelelsen du ser på din skærm, hvis der er en.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Venligst forklar hvad du ønsker at gøre, hvad du gjorde og hvad der skete
215
• Hvilken browser bruger du?
Google Chrome v135
-
• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. 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. er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Hvilken browser bruger du?
Google Chrome v135
-
• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Hvilken browser bruger du?
Google Chrome v135
-
• Hvad blev der vist på skærmen, da du blev blokeret (Blank skærm? Noget af spilbrugerfladen? Fejlmeddelelse?)
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Hvilken browser bruger du?
Google Chrome v135
-
• Hvilken del af reglerne blev ikke respekteret ved BGA-tilpasningen
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Er regel-brudddet synligt i e
215
• Hvilken browser bruger du?
Google Chrome v135
-
• Hvad var den spilhandling du ønskede at udføre?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Hvad forsøgte du at gøre for at udløse denne spilhandling?
215
-
• Hvad skete der, da du forsøgre at gøre dette (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
• Hvilken browser bruger du?
Google Chrome v135
-
• I hvilket stadie af spillet opstod problemet (hvad var den daværende spilinstruktion)?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Hvad skete der, da du forsøgte at udføre denne spilhandling (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
215
• Hvilken browser bruger du?
Google Chrome v135
-
• Venligst beskriv display problemet. 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.
• Hvilken browser bruger du?
Google Chrome v135
-
• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. 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. er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Hvilken browser bruger du?
Google Chrome v135
-
• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Hvilken browser bruger du?
Google Chrome v135
Rapporthistorik
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 :-)
Tilføj noget til denne rapport
- Et andet bord-ID / træk ID
- Løste F5 problemet?
- Skete problemet flere gange? Hver gang? Tilfældigt?
- 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.
