#166755: "Monster started with bleeding token already on it"
Kāds ir šis ziņojums?
Kas notika? Lūdzu izvēlies no zemākredzamajiem
Kas notika? Lūdzu izvēlies no zemākredzamajiem
Lūdzu, pārbaudiet, vai par šo pašu tēmu jau ir ziņojums
Ja jā, lūdzu, balsojiet par šo ziņojumu. Ziņojumiem ar vislielākajām balsīm tiek dota PRIORITĀTE!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detalizēts apraksts
-
• Lūdzu nokopē/ielīmē kļūdas ziņu, ko redzi ekrānā, ja tāda ir.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Lūdzu paskaidro, ko Tu vēlējies darīt, ko Tu izdarīji un kas notika
215
• Kāda ir Tava pārlūkprogramma?
Google Chrome v135
-
• Lūdzu iekopē tekstu, kas redzams angļu, nevis tavā valodā. 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. Vai šis teksts ir pieejams tulkošanas sistēmā? Ja jā, vai tas ir ticis tulkots pēdējo 24 stundu laikā?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Kāda ir Tava pārlūkprogramma?
Google Chrome v135
-
• Lūdzu, paskaidrojiet savu ieteikumu precīzi un kodolīgi, lai tas būtu pēc iespējas vieglāk saprotams.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Kāda ir Tava pārlūkprogramma?
Google Chrome v135
-
• Kas tika attēlots ekrānā, kad Tu tiki bloķēts (tukšs ekrāns? Daļa no spēles interfeisa? Ziņa par kļūdu?)?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Kāda ir Tava pārlūkprogramma?
Google Chrome v135
-
• Kura noteikumu daļa netika ņemta vērā BGA versijā?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Vai noteikumu pārkāpums ir redzams spēles atkārtojumā? Ja jā, tad kurā gājienā?
215
• Kāda ir Tava pārlūkprogramma?
Google Chrome v135
-
• Kādu spēles darbību Tu vēlējies veikt?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Ko tu dari, lai panāktu šo spēles darbību?
215
-
• Kas notika, kad veicāt šo darbību (kļūdas paziņojums, spēles informācijas paziņojums,...)?
• Kāda ir Tava pārlūkprogramma?
Google Chrome v135
-
• Kurā spēles solī problēma parādījās (kas bija tā brīža spēles instrukcija)?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Kas notika, kad mēģinājāt veikt spēles darbību (kļūdas paziņojums, spēles informācijas paziņojums,...)?
215
• Kāda ir Tava pārlūkprogramma?
Google Chrome v135
-
• Lūdzu aprakstiet radušos problēmu. 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.
• Kāda ir Tava pārlūkprogramma?
Google Chrome v135
-
• Lūdzu iekopē tekstu, kas redzams angļu, nevis tavā valodā. 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. Vai šis teksts ir pieejams tulkošanas sistēmā? Ja jā, vai tas ir ticis tulkots pēdējo 24 stundu laikā?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Kāda ir Tava pārlūkprogramma?
Google Chrome v135
-
• Lūdzu, paskaidrojiet savu ieteikumu precīzi un kodolīgi, lai tas būtu pēc iespējas vieglāk saprotams.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Kāda ir Tava pārlūkprogramma?
Google Chrome v135
Ziņojuma vēsture
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 :-)
Pievieno kaut ko šim ziņojumam
- Cita galda ID / gājiena ID
- Vai F5 atrisināja šo problēmu?
- Vai šī problēma parādās vairākas reizes? Katru reizi? Nekonkrētās reizēs?
- 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.
