#31420: "After getting hit with a war token, my coin count went negative"
Quel est le sujet de ce rapport ?
Que s'est-il passé ? Merci de choisir ci-dessous
Que s'est-il passé ? Merci de choisir ci-dessous
Veuillez vérifier s'il existe déjà un rapport sur le même sujet
Si oui, veuillez VOTER pour ce rapport. Les rapports ayant le plus de votes auront la PRIORITÉ !
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Description détaillée
-
• Merci de copier-coller le message d'erreur qui s'affiche à l'écran, s'il y a lieu.
The rules say (p14) "If your opponent doesn't have enough coins, they lose all of their coins." There's no way to go negative in the in-person game because money is managed with physical coin tokens, so if you would otherwise go negative you should just go to zero.
Screenshot:
blahedo.org/bga/seven-duel-negative.png
This is Table № 137320811 at Move #64. I suspect the cause had to do with my opponent having the Strategy token, building Pretorium (a three-shield card), and being placed just right to pick up *both* military tokens on the same turn, possibly bypassing some check in the code or checking against the original instead of current number of coins or somesuch.
-
• Veuillez expliquer ce que vous vouliez faire, ce que vous avez fait et ce qu'il s'est passé
Kind of. Here's the spanner in the works: when I replay, prior to the Pretorium play, it shows me with 8 coins, which are then decreased (correctly) to 1 at Move #64. So that's weird (and doesn't match the screenshot). Then, on the next move when I build something for free, my coin count goes up to 3 for no obvious reason. So that's also weird. (I don't think Urbanism should have fired in that case because there was no linking and no "free" condition, just a discount that applied, but if it *did* then it should have gone up by *4* not *2*. Or maybe it went up by 4 from -1 to get to 3? In which case the 1 was an incorrect display?) Basically, there's some hinky stuff going on but it's hard to diagnose without seeing the code. If I were sure the parenthetical above were a distinct bug I'd file a separate report for it, but it's too tightly tangled for me to do that.
• Quel est votre navigateur ?
Firefox v80.0.1
-
• SVP copiez / collez ici le texte affiché en anglais au lieu de votre langue. Si vous disposez d'une capture d'écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour la télécharger et en copier/coller le lien ici. Ce texte est-il disponible dans le système de traduction ? Si oui, a-t-il été traduit depuis plus de 24 heures ?
The rules say (p14) "If your opponent doesn't have enough coins, they lose all of their coins." There's no way to go negative in the in-person game because money is managed with physical coin tokens, so if you would otherwise go negative you should just go to zero.
Screenshot:
blahedo.org/bga/seven-duel-negative.png
This is Table № 137320811 at Move #64. I suspect the cause had to do with my opponent having the Strategy token, building Pretorium (a three-shield card), and being placed just right to pick up *both* military tokens on the same turn, possibly bypassing some check in the code or checking against the original instead of current number of coins or somesuch.
• Quel est votre navigateur ?
Firefox v80.0.1
-
• Merci d'expliquer votre suggestion de manière précise et concise, de façon à ce qu'il soit aussi simple que possible de comprendre ce que vous voulez dire.
The rules say (p14) "If your opponent doesn't have enough coins, they lose all of their coins." There's no way to go negative in the in-person game because money is managed with physical coin tokens, so if you would otherwise go negative you should just go to zero.
Screenshot:
blahedo.org/bga/seven-duel-negative.png
This is Table № 137320811 at Move #64. I suspect the cause had to do with my opponent having the Strategy token, building Pretorium (a three-shield card), and being placed just right to pick up *both* military tokens on the same turn, possibly bypassing some check in the code or checking against the original instead of current number of coins or somesuch.
• Quel est votre navigateur ?
Firefox v80.0.1
-
• Qu'affichait l'écran lorsque vous avez été bloqué(e) (Un écran vierge ? Une partie de l'interface du jeu ? Un message d'erreur ?)
The rules say (p14) "If your opponent doesn't have enough coins, they lose all of their coins." There's no way to go negative in the in-person game because money is managed with physical coin tokens, so if you would otherwise go negative you should just go to zero.
Screenshot:
blahedo.org/bga/seven-duel-negative.png
This is Table № 137320811 at Move #64. I suspect the cause had to do with my opponent having the Strategy token, building Pretorium (a three-shield card), and being placed just right to pick up *both* military tokens on the same turn, possibly bypassing some check in the code or checking against the original instead of current number of coins or somesuch.
• Quel est votre navigateur ?
Firefox v80.0.1
-
• Quelle partie des règles n'a pas été respectée par l'adaptation BGA ?
The rules say (p14) "If your opponent doesn't have enough coins, they lose all of their coins." There's no way to go negative in the in-person game because money is managed with physical coin tokens, so if you would otherwise go negative you should just go to zero.
Screenshot:
blahedo.org/bga/seven-duel-negative.png
This is Table № 137320811 at Move #64. I suspect the cause had to do with my opponent having the Strategy token, building Pretorium (a three-shield card), and being placed just right to pick up *both* military tokens on the same turn, possibly bypassing some check in the code or checking against the original instead of current number of coins or somesuch.
-
• La violation de règle est-elle visible dans le replay de la partie ? Si oui, à quel numéro de coup ?
Kind of. Here's the spanner in the works: when I replay, prior to the Pretorium play, it shows me with 8 coins, which are then decreased (correctly) to 1 at Move #64. So that's weird (and doesn't match the screenshot). Then, on the next move when I build something for free, my coin count goes up to 3 for no obvious reason. So that's also weird. (I don't think Urbanism should have fired in that case because there was no linking and no "free" condition, just a discount that applied, but if it *did* then it should have gone up by *4* not *2*. Or maybe it went up by 4 from -1 to get to 3? In which case the 1 was an incorrect display?) Basically, there's some hinky stuff going on but it's hard to diagnose without seeing the code. If I were sure the parenthetical above were a distinct bug I'd file a separate report for it, but it's too tightly tangled for me to do that.
• Quel est votre navigateur ?
Firefox v80.0.1
-
• Quelle action de jeu vouliez-vous faire ?
The rules say (p14) "If your opponent doesn't have enough coins, they lose all of their coins." There's no way to go negative in the in-person game because money is managed with physical coin tokens, so if you would otherwise go negative you should just go to zero.
Screenshot:
blahedo.org/bga/seven-duel-negative.png
This is Table № 137320811 at Move #64. I suspect the cause had to do with my opponent having the Strategy token, building Pretorium (a three-shield card), and being placed just right to pick up *both* military tokens on the same turn, possibly bypassing some check in the code or checking against the original instead of current number of coins or somesuch.
-
• Qu'avez-vous essayé de faire pour déclencher cette action de jeu ?
Kind of. Here's the spanner in the works: when I replay, prior to the Pretorium play, it shows me with 8 coins, which are then decreased (correctly) to 1 at Move #64. So that's weird (and doesn't match the screenshot). Then, on the next move when I build something for free, my coin count goes up to 3 for no obvious reason. So that's also weird. (I don't think Urbanism should have fired in that case because there was no linking and no "free" condition, just a discount that applied, but if it *did* then it should have gone up by *4* not *2*. Or maybe it went up by 4 from -1 to get to 3? In which case the 1 was an incorrect display?) Basically, there's some hinky stuff going on but it's hard to diagnose without seeing the code. If I were sure the parenthetical above were a distinct bug I'd file a separate report for it, but it's too tightly tangled for me to do that.
-
• Que s'est-il passé lorsque vous avez essayé de faire cela (message d'erreur, message dans la barre d'état du jeu...) ?
• Quel est votre navigateur ?
Firefox v80.0.1
-
• À quelle étape de la partie le problème est-il apparu ? Quelles instructions le jeu affichait-il ?
The rules say (p14) "If your opponent doesn't have enough coins, they lose all of their coins." There's no way to go negative in the in-person game because money is managed with physical coin tokens, so if you would otherwise go negative you should just go to zero.
Screenshot:
blahedo.org/bga/seven-duel-negative.png
This is Table № 137320811 at Move #64. I suspect the cause had to do with my opponent having the Strategy token, building Pretorium (a three-shield card), and being placed just right to pick up *both* military tokens on the same turn, possibly bypassing some check in the code or checking against the original instead of current number of coins or somesuch.
-
• Que s'est-il passé lorsque vous avez essayé de faire cette action de jeu (message d'erreur, message dans la barre d'état du jeu...) ?
Kind of. Here's the spanner in the works: when I replay, prior to the Pretorium play, it shows me with 8 coins, which are then decreased (correctly) to 1 at Move #64. So that's weird (and doesn't match the screenshot). Then, on the next move when I build something for free, my coin count goes up to 3 for no obvious reason. So that's also weird. (I don't think Urbanism should have fired in that case because there was no linking and no "free" condition, just a discount that applied, but if it *did* then it should have gone up by *4* not *2*. Or maybe it went up by 4 from -1 to get to 3? In which case the 1 was an incorrect display?) Basically, there's some hinky stuff going on but it's hard to diagnose without seeing the code. If I were sure the parenthetical above were a distinct bug I'd file a separate report for it, but it's too tightly tangled for me to do that.
• Quel est votre navigateur ?
Firefox v80.0.1
-
• Veuillez décrire le problème d'affichage. Si vous disposez d'une capture d'écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour la télécharger et en copier/coller le lien ici.
The rules say (p14) "If your opponent doesn't have enough coins, they lose all of their coins." There's no way to go negative in the in-person game because money is managed with physical coin tokens, so if you would otherwise go negative you should just go to zero.
Screenshot:
blahedo.org/bga/seven-duel-negative.png
This is Table № 137320811 at Move #64. I suspect the cause had to do with my opponent having the Strategy token, building Pretorium (a three-shield card), and being placed just right to pick up *both* military tokens on the same turn, possibly bypassing some check in the code or checking against the original instead of current number of coins or somesuch.
• Quel est votre navigateur ?
Firefox v80.0.1
-
• SVP copiez / collez ici le texte affiché en anglais au lieu de votre langue. Si vous disposez d'une capture d'écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour la télécharger et en copier/coller le lien ici. Ce texte est-il disponible dans le système de traduction ? Si oui, a-t-il été traduit depuis plus de 24 heures ?
The rules say (p14) "If your opponent doesn't have enough coins, they lose all of their coins." There's no way to go negative in the in-person game because money is managed with physical coin tokens, so if you would otherwise go negative you should just go to zero.
Screenshot:
blahedo.org/bga/seven-duel-negative.png
This is Table № 137320811 at Move #64. I suspect the cause had to do with my opponent having the Strategy token, building Pretorium (a three-shield card), and being placed just right to pick up *both* military tokens on the same turn, possibly bypassing some check in the code or checking against the original instead of current number of coins or somesuch.
• Quel est votre navigateur ?
Firefox v80.0.1
-
• Merci d'expliquer votre suggestion de manière précise et concise, de façon à ce qu'il soit aussi simple que possible de comprendre ce que vous voulez dire.
The rules say (p14) "If your opponent doesn't have enough coins, they lose all of their coins." There's no way to go negative in the in-person game because money is managed with physical coin tokens, so if you would otherwise go negative you should just go to zero.
Screenshot:
blahedo.org/bga/seven-duel-negative.png
This is Table № 137320811 at Move #64. I suspect the cause had to do with my opponent having the Strategy token, building Pretorium (a three-shield card), and being placed just right to pick up *both* military tokens on the same turn, possibly bypassing some check in the code or checking against the original instead of current number of coins or somesuch.
• Quel est votre navigateur ?
Firefox v80.0.1
Historique du rapport de bug
Before the Pretorium you actually had 10 (!) coins. The Pretorium play made you lose 2 + 5 coins, leaving you with 3.
So for some reason the coin count was wrong before hand. The jump to 3 ("for no obvious reason") was correct and is the server side sending the current coin count again to the client side.
I will have a look at keeping the coin count more robust, currently it is probably too reliant of animations being properly finished, which is probably why things get wonky in replay as well.
Btw, in the screenshots I see that the font on the coins and Victory points icon is wrong, what OS are you on? The bug report only says Firefox v80, I just checked Firefox v81 on Windows 10 and the correct font shows up.
It was set off by a military token as well. Running on safari on a mac.
Ajouter à ce rapport
- Un autre n° de table / n° de coup
- Appuyer sur F5 a-t-il résolu le problème ?
- Le problème est-il apparu plusieurs fois ? À chaque fois ? Aléatoirement ?
- Si vous disposez d'une capture d'écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour la télécharger et en copier/coller le lien ici.
