#166755: "Monster started with bleeding token already on it"
Na kaj se nanaša prijava?
Kaj se je zgodilo? Prosimo, izberi spodaj
Kaj se je zgodilo? Prosimo, izberi spodaj
Prosimo preverite ali že obstaja poročilo o isti zadevi
Če je tako, GLASUJTE za to poročilo. Poročila z največ glasovi se obravnavajo PREDNOSTNO!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Natančen opis
-
• Kopirajte / prilepite sporočilo o napaki, ki ga vidite na zaslonu, če ga imate.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Prosim, pojasnite, kaj ste hoteli storiti, kaj ste naredili in kaj se je zgodilo
215
• Kateri brskalnik uporabljaš?
Google Chrome v135
-
• Kopirajte / prilepite besedilo, prikazano v angleščini, namesto v vašem jeziku. 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. Je ta tekst dosegljiv v prevajalnem sistemu? Če ja, ali je bil preveden več kot 24 ur nazaj?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Kateri brskalnik uporabljaš?
Google Chrome v135
-
• Natančno in jedrnato pojasnite svoj predlog, da bo čim lažje razumeti, kaj mislite.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Kateri brskalnik uporabljaš?
Google Chrome v135
-
• Kaj je bilo prikazano na zaslonu, ko ste bili blokirani (prazen zaslon? Del vmesnika za igro? Sporočilo o napaki?)
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Kateri brskalnik uporabljaš?
Google Chrome v135
-
• Kateri del pravil ni bil upoštevan pri priredbi za BGA
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Je kršitev pravil vidna na seznamu potez? Če je, pri kateri številki poteze?
215
• Kateri brskalnik uporabljaš?
Google Chrome v135
-
• Katero potezo ste želeli narediti v igri?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Kaj ste poskušali narediti, da bi izvedli to potezo v igri?
215
-
• Kaj se je zgodilo, ko ste poskusili to storiti (sporočilo o napaki, sporočilo v vrstici stanja, ...)?
• Kateri brskalnik uporabljaš?
Google Chrome v135
-
• Na kateri točki v igri se je težava pojavila (katera navodila so bila prikazana)
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
-
• Kaj se je zgodilo, ko ste poskušali narediti to potezo v igri (sporočilo o napaki, sporočilo v vrstici stanja, ...)?
215
• Kateri brskalnik uporabljaš?
Google Chrome v135
-
• Prosim opiši problem s prikazom. 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.
• Kateri brskalnik uporabljaš?
Google Chrome v135
-
• Kopirajte / prilepite besedilo, prikazano v angleščini, namesto v vašem jeziku. 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. Je ta tekst dosegljiv v prevajalnem sistemu? Če ja, ali je bil preveden več kot 24 ur nazaj?
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Kateri brskalnik uporabljaš?
Google Chrome v135
-
• Natančno in jedrnato pojasnite svoj predlog, da bo čim lažje razumeti, kaj mislite.
I don't think the inquisitor in the final battle of Ramparts we had was supposed to have a bleeding token already on it.
• Kateri brskalnik uporabljaš?
Google Chrome v135
Zgodovina poročil
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 :-)
Dodaj nekaj k temu poročilu
- Drug ID mize/ premikanje ID-ja
- Ali je F5 rešil težavo?
- Se je problem pojavil večkrat? Vsakič? Naključno?
- 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.
