Page 1 of 1

Something's wrong with resolving effects in turn order

Posted: 10 September 2021, 16:31
by Labravo
Ok, so here's the deal: I think I just won a match unfairly. It was a 4 player game and it went down to two. My oponent had 6 energy, 12 fame and 3 life. I had no energy, next to no fame and also 3 life. You can guess that they had gone for points and I had gone for whacking. Since the beginning they were the first player in turn order, I was last. So it was their turn, they couldn't do much and the market offered High Altitude Bombing: cost 4, all monsters (including you) take 3 damage. And they took it. Now, I'd have guessed that, since we both had 3 life, we would both die — and I was right. However, I would also have guessed that the damage would resolve simultaneously and one or two things would ensue: 1) having both died, we would both lose, a game with no winners, or 2) since they had 12 fame and I had nothing, they would win. This is what happened: damage resolved BY TURN ORDER, so we both eventually died, but since they died first, I was declared the winner. Could we count this as a bug?

Re: Something's wrong with resolving effects in turn order

Posted: 10 September 2021, 16:43
by Ez0ah
It would be helpful to have the table ID.
That being said, it’s probably a bug. Back in alpha, all the damage was done in turn order, so every time multiple players were killed during the same instance, they would be still ranked differently.
That was fixed, but maybe high altitude bombing still has that issue. There is another card that does dmg to everyone but the buyer, it would be interesting to check if the same bug applies

Re: Something's wrong with resolving effects in turn order

Posted: 15 September 2021, 22:18
by Empresario
Now that brings one more question:

both players have 3 hearts, but one has 17 fame and Eater of Dead. This player buys High Altitude Bombing. How does BGA resolve it?

Re: Something's wrong with resolving effects in turn order

Posted: 15 September 2021, 22:52
by thoun
You have to survive your turn to win, so going to 20 and die at the same time does not give you the win

Re: Something's wrong with resolving effects in turn order

Posted: 15 November 2021, 11:16
by Friggs
I had something similar in game #216721713. I would guess it would have been a tie (because nobody had any fame). But in stead because of the turn order thing the player buying the card lost.

Re: Something's wrong with resolving effects in turn order

Posted: 15 November 2021, 20:15
by Yasten
Ez0ah wrote: 10 September 2021, 16:43 It would be helpful to have the table ID.
That being said, it’s probably a bug. Back in alpha, all the damage was done in turn order, so every time multiple players were killed during the same instance, they would be still ranked differently.
That was fixed, but maybe high altitude bombing still has that issue. There is another card that does dmg to everyone but the buyer, it would be interesting to check if the same bug applies
If that happens, wouldn't the buyer win anyway if everybody had 1 life since he isn't affected? That's pretty much a given tbh... Although IF the buyer was dead that's an interesting point.

Re: Something's wrong with resolving effects in turn order

Posted: 15 November 2021, 21:53
by Ez0ah
Yasten wrote: 15 November 2021, 20:15
Ez0ah wrote: 10 September 2021, 16:43 It would be helpful to have the table ID.
That being said, it’s probably a bug. Back in alpha, all the damage was done in turn order, so every time multiple players were killed during the same instance, they would be still ranked differently.
That was fixed, but maybe high altitude bombing still has that issue. There is another card that does dmg to everyone but the buyer, it would be interesting to check if the same bug applies
If that happens, wouldn't the buyer win anyway if everybody had 1 life since he isn't affected? That's pretty much a given tbh... Although IF the buyer was dead that's an interesting point.
I meant as if the dmg is also dealt in turn order and if several players are eliminated, they should have the same final ranking