#9811: "Downsized Castle/Keep did not ripple"
Пра што гэтая справаздача?
Што адбылося? Калі ласка, абярыце з ніжэй прапісаныя
Што адбылося? Калі ласка, абярыце з ніжэй прапісаныя
Калі ласка, праверце, ці існуе ўжо справаздача на тую ж тэму
Калі гэта так, ПРАГАЛАСУЙЦЕ за гэтую справаздачу. Справаздачы з найбольшай колькасцю галасоў будуць разглядацца У ПЕРШУЮ ЧАРГУ!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Дэталёвае апісанне
-
• Калі ласка, скапіруйце тэкст памылкі, якую вы бачыце на экране (калі яна ёсць).
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.
-
• Калі ласка, растлумачце, што вы хацелі зрабіць, што вы зрабілі і што здарылася
approximately move # 197
• Якім браўзэрам вы карыстаецеся?
Google Chrome v66
-
• Калі ласка, скапіруйце тэкст на англійскай замест перакладу на ваш мову. 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. Дзе можна знайсьці гэты тэкст у сістэме перакладу? Калі так, ці быў ён перакладзены больш за 24 гадзін таму?
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.
• Якім браўзэрам вы карыстаецеся?
Google Chrome v66
-
• Калі ласка, дакладна і коратка апішыце сваю прапанову, каб зрабіць яе найбольш даступнай для разумення.
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.
• Якім браўзэрам вы карыстаецеся?
Google Chrome v66
-
• Што было намалявана на экране, калі вас заблакавала? (Пусты экран? Частка гульнявога стала? Паведамленне пра памылку?)
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.
• Якім браўзэрам вы карыстаецеся?
Google Chrome v66
-
• Якая частка правілаў не выкананая ў версіі 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.
-
• Ці відаць парушэнне правілаў у паўторы гульні? Калі так, то на якім хаду?
approximately move # 197
• Якім браўзэрам вы карыстаецеся?
Google Chrome v66
-
• Якое гульнявое дзеянне вы хацелі зрабіць?
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.
-
• Што вы спрабавалі зрабіць, каб выканаць гэтае гульнявое дзеянне?
approximately move # 197
-
• Што адбылося, калі вы паспрабавалі зрабіць гэта (паведамленне пра памылку, паведамленне ў радку стану гульні ...)?
• Якім браўзэрам вы карыстаецеся?
Google Chrome v66
-
• На якім кроку гульні адбылася праблема (якая была інструкцыя ў той момант у гульні)?
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.
-
• Што адбылося, калі вы паспрабавалі здзейсніць гульнявое дзеянне (паведамленне пра памылку, паведамленне ў радку стану гульні ...)?
approximately move # 197
• Якім браўзэрам вы карыстаецеся?
Google Chrome v66
-
• Калі ласка, апішыце памылку адлюстравання. 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.
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.
• Якім браўзэрам вы карыстаецеся?
Google Chrome v66
-
• Калі ласка, скапіруйце тэкст на англійскай замест перакладу на ваш мову. 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. Дзе можна знайсьці гэты тэкст у сістэме перакладу? Калі так, ці быў ён перакладзены больш за 24 гадзін таму?
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.
• Якім браўзэрам вы карыстаецеся?
Google Chrome v66
-
• Калі ласка, дакладна і коратка апішыце сваю прапанову, каб зрабіць яе найбольш даступнай для разумення.
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.
• Якім браўзэрам вы карыстаецеся?
Google Chrome v66
Гісторыя справаздачы
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.
Дадайце да гэтага дакладу
- Іншая Табліца ID / ID ходу
- Ці F5 вырашыла Вашу праблему?
- Ці з'яўлялася праблема некалькі разоў? Кожны раз? Выпадкова?
- 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.
