#9811: "Downsized Castle/Keep did not ripple"
A che riguardo è la segnalazione?
Cos'è successo? Prego, seleziona tra le seguenti
Cos'è successo? Prego, seleziona tra le seguenti
Si prega di verificare se esiste già una segnalazione sullo stesso argomento
Se sì, per favore VOTA solo questa segnalazione. Segnalazioni con più voti hanno priorità di presa in carico!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Descrizione dettagliata
-
• Per favore copia/incolla il messaggio di errore visualizzato sullo schermo, se possibile.
Whenever a building is downsized in Might (or Faith) so long as its shadow is the same type, same size and same owner the shadow should always be destroyed, and then the new downsized building should be rippled forward to replace it. In this case, the shadow building was left alone even though it met the requirement of same type, same size and same owner. Instead, it failed to ripple (it did not even destroy the shadow) because of a claimed conflict of hierarchy. The downsized building (castle to a keep) should have destroryed the shadow Castle, the rippled the new Keep into the domain regardless of potential "conflicts"... this is quite clear in the rules and in the FAQ on file with BGG. If a conflict of Hierarchy occurs, then the conflicting buildings (after being rippled) should be downsized by choice of the effecting player, with his own buildings being prioritized over those of other players.
-
• Per favore spiega cosa avresti voluto fare, cosa hai fatto e cosa è successo
approximately move # 197
• Qual è il tuo browser?
Google Chrome v66
-
• Per favore copia/incolla il testo visualizzato in inglese invece che nella tua lingua. Se hai uno screenshot di questo bug (è sempre buona norma farlo), usa un servizio di caricamento immagini a tua scelta (come snipboard.io) per caricarlo e copiare/incollare il link qui. Questo testo è disponibile nel sistema di traduzione? Se sì, è stato tradotto nell'arco di più di 24 ore?
Whenever a building is downsized in Might (or Faith) so long as its shadow is the same type, same size and same owner the shadow should always be destroyed, and then the new downsized building should be rippled forward to replace it. In this case, the shadow building was left alone even though it met the requirement of same type, same size and same owner. Instead, it failed to ripple (it did not even destroy the shadow) because of a claimed conflict of hierarchy. The downsized building (castle to a keep) should have destroryed the shadow Castle, the rippled the new Keep into the domain regardless of potential "conflicts"... this is quite clear in the rules and in the FAQ on file with BGG. If a conflict of Hierarchy occurs, then the conflicting buildings (after being rippled) should be downsized by choice of the effecting player, with his own buildings being prioritized over those of other players.
• Qual è il tuo browser?
Google Chrome v66
-
• Spiega il tuo suggerimento in modo preciso e conciso in modo che sia il più semplice possibile per capire cosa intendi.
Whenever a building is downsized in Might (or Faith) so long as its shadow is the same type, same size and same owner the shadow should always be destroyed, and then the new downsized building should be rippled forward to replace it. In this case, the shadow building was left alone even though it met the requirement of same type, same size and same owner. Instead, it failed to ripple (it did not even destroy the shadow) because of a claimed conflict of hierarchy. The downsized building (castle to a keep) should have destroryed the shadow Castle, the rippled the new Keep into the domain regardless of potential "conflicts"... this is quite clear in the rules and in the FAQ on file with BGG. If a conflict of Hierarchy occurs, then the conflicting buildings (after being rippled) should be downsized by choice of the effecting player, with his own buildings being prioritized over those of other players.
• Qual è il tuo browser?
Google Chrome v66
-
• Cosa era mostrato sullo schermo quando sei rimasto bloccato (schermo bianco? interfaccia di gioco parziale? messaggio di errore?)
Whenever a building is downsized in Might (or Faith) so long as its shadow is the same type, same size and same owner the shadow should always be destroyed, and then the new downsized building should be rippled forward to replace it. In this case, the shadow building was left alone even though it met the requirement of same type, same size and same owner. Instead, it failed to ripple (it did not even destroy the shadow) because of a claimed conflict of hierarchy. The downsized building (castle to a keep) should have destroryed the shadow Castle, the rippled the new Keep into the domain regardless of potential "conflicts"... this is quite clear in the rules and in the FAQ on file with BGG. If a conflict of Hierarchy occurs, then the conflicting buildings (after being rippled) should be downsized by choice of the effecting player, with his own buildings being prioritized over those of other players.
• Qual è il tuo browser?
Google Chrome v66
-
• Quale parte delle regole non è stata rispettata dall'adattamento BGA
Whenever a building is downsized in Might (or Faith) so long as its shadow is the same type, same size and same owner the shadow should always be destroyed, and then the new downsized building should be rippled forward to replace it. In this case, the shadow building was left alone even though it met the requirement of same type, same size and same owner. Instead, it failed to ripple (it did not even destroy the shadow) because of a claimed conflict of hierarchy. The downsized building (castle to a keep) should have destroryed the shadow Castle, the rippled the new Keep into the domain regardless of potential "conflicts"... this is quite clear in the rules and in the FAQ on file with BGG. If a conflict of Hierarchy occurs, then the conflicting buildings (after being rippled) should be downsized by choice of the effecting player, with his own buildings being prioritized over those of other players.
-
• La violazione delle regole è visibile nel replay della partita? Se sì, a che numero di mossa?
approximately move # 197
• Qual è il tuo browser?
Google Chrome v66
-
• Qual era l'azione di gioco che volevi fare?
Whenever a building is downsized in Might (or Faith) so long as its shadow is the same type, same size and same owner the shadow should always be destroyed, and then the new downsized building should be rippled forward to replace it. In this case, the shadow building was left alone even though it met the requirement of same type, same size and same owner. Instead, it failed to ripple (it did not even destroy the shadow) because of a claimed conflict of hierarchy. The downsized building (castle to a keep) should have destroryed the shadow Castle, the rippled the new Keep into the domain regardless of potential "conflicts"... this is quite clear in the rules and in the FAQ on file with BGG. If a conflict of Hierarchy occurs, then the conflicting buildings (after being rippled) should be downsized by choice of the effecting player, with his own buildings being prioritized over those of other players.
-
• Cosa stai provando a fare per attivare questa azione di gioco?
approximately move # 197
-
• Cosa è successo quando hai provato a fare questo (messaggio di errore, messaggio nella barra di stato del gioco...)?
• Qual è il tuo browser?
Google Chrome v66
-
• In quale fase del gioco si è verificato il problema (qual era l'istruzione della partita in corso)?
Whenever a building is downsized in Might (or Faith) so long as its shadow is the same type, same size and same owner the shadow should always be destroyed, and then the new downsized building should be rippled forward to replace it. In this case, the shadow building was left alone even though it met the requirement of same type, same size and same owner. Instead, it failed to ripple (it did not even destroy the shadow) because of a claimed conflict of hierarchy. The downsized building (castle to a keep) should have destroryed the shadow Castle, the rippled the new Keep into the domain regardless of potential "conflicts"... this is quite clear in the rules and in the FAQ on file with BGG. If a conflict of Hierarchy occurs, then the conflicting buildings (after being rippled) should be downsized by choice of the effecting player, with his own buildings being prioritized over those of other players.
-
• Cosa è successo quando hai provato a fare questa azione di gioco (messaggio di errore, messaggio nella barra di stato del gioco...)?
approximately move # 197
• Qual è il tuo browser?
Google Chrome v66
-
• Per favore descrivi il problema rilevato. Se hai uno screenshot di questo bug (è sempre buona norma farlo), usa un servizio di caricamento immagini a tua scelta (come snipboard.io) per caricarlo e copiare/incollare il link qui.
Whenever a building is downsized in Might (or Faith) so long as its shadow is the same type, same size and same owner the shadow should always be destroyed, and then the new downsized building should be rippled forward to replace it. In this case, the shadow building was left alone even though it met the requirement of same type, same size and same owner. Instead, it failed to ripple (it did not even destroy the shadow) because of a claimed conflict of hierarchy. The downsized building (castle to a keep) should have destroryed the shadow Castle, the rippled the new Keep into the domain regardless of potential "conflicts"... this is quite clear in the rules and in the FAQ on file with BGG. If a conflict of Hierarchy occurs, then the conflicting buildings (after being rippled) should be downsized by choice of the effecting player, with his own buildings being prioritized over those of other players.
• Qual è il tuo browser?
Google Chrome v66
-
• Per favore copia/incolla il testo visualizzato in inglese invece che nella tua lingua. Se hai uno screenshot di questo bug (è sempre buona norma farlo), usa un servizio di caricamento immagini a tua scelta (come snipboard.io) per caricarlo e copiare/incollare il link qui. Questo testo è disponibile nel sistema di traduzione? Se sì, è stato tradotto nell'arco di più di 24 ore?
Whenever a building is downsized in Might (or Faith) so long as its shadow is the same type, same size and same owner the shadow should always be destroyed, and then the new downsized building should be rippled forward to replace it. In this case, the shadow building was left alone even though it met the requirement of same type, same size and same owner. Instead, it failed to ripple (it did not even destroy the shadow) because of a claimed conflict of hierarchy. The downsized building (castle to a keep) should have destroryed the shadow Castle, the rippled the new Keep into the domain regardless of potential "conflicts"... this is quite clear in the rules and in the FAQ on file with BGG. If a conflict of Hierarchy occurs, then the conflicting buildings (after being rippled) should be downsized by choice of the effecting player, with his own buildings being prioritized over those of other players.
• Qual è il tuo browser?
Google Chrome v66
-
• Spiega il tuo suggerimento in modo preciso e conciso in modo che sia il più semplice possibile per capire cosa intendi.
Whenever a building is downsized in Might (or Faith) so long as its shadow is the same type, same size and same owner the shadow should always be destroyed, and then the new downsized building should be rippled forward to replace it. In this case, the shadow building was left alone even though it met the requirement of same type, same size and same owner. Instead, it failed to ripple (it did not even destroy the shadow) because of a claimed conflict of hierarchy. The downsized building (castle to a keep) should have destroryed the shadow Castle, the rippled the new Keep into the domain regardless of potential "conflicts"... this is quite clear in the rules and in the FAQ on file with BGG. If a conflict of Hierarchy occurs, then the conflicting buildings (after being rippled) should be downsized by choice of the effecting player, with his own buildings being prioritized over those of other players.
• Qual è il tuo browser?
Google Chrome v66
Storico dei resoconti
Table 39642880 move #197 (about); The is complete... the bug caused me to lose the game btw.. :p
imgur.com/gallery/7Ss4nex
What happened:
My placing the hamlet in Might (circled in red) merged two domains, each with a Castle... my Castle had superior strength, and so won the contest. Red player downsized his Castle to a keep and then the system claimed "Ripple Cancelled due to Conflict of Hierarchy". Nothing was changed in Faith or Reason.
What should have occurred:
The castle in Faith (marked with a red "X" in my diagram) should have downsized to a keep with the same footprint as the Keep in Might (circled in Red). This should have caused a conflict of hierarchy with the Black player's Keep already in that same domain, however it is clear in the rules that such a conflict is allowed to occur but must be immediately resolved by the effecting player. I should've been allowed to then choose which Keep would win the conflict (if i had a Keep of my own in the contest, then I would've had to downsize it first, but i did not). I was planning to choose the black keep to downsize... then, no matter where the black player located his downsized Watchtower, the City in the upper right corner would've been 'isolated' in a domain without any religious buildings. I then would've used one of my last 2 actions to place a chapel in that domain and claim 5 additional points for the final scoring, allowing me to win by 3 points, instead of losing by 1 point.
The system needs to learn to ignore conflicts when resolving separations of domains due to downsized buildings. It also needs to learn the timing of events... the shadows are always destroyed first, and the the ripple of the new building is placed -- so, even if something prevents the downsize in Faith or Reason, the original building is still destroyed in those realms (and ruin renovations are lost in Reason).
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
Aggiungi qualcosa a questo report
- Un altro ID tavolo / ID mossa
- F5 ha risolto il problema?
- Il problema si verifica spesso? Ogni volta? Casualmente?
- Se hai uno screenshot di questo bug (è sempre buona norma farlo), usa un servizio di caricamento immagini a tua scelta (come snipboard.io) per caricarlo e copiare/incollare il link qui.
