#32886: "Eliminate hidden trackable information (at least when playing async)"
Waarover gaat dit rapport?
Wat is er gebeurd? Selecteer uit het onderstaande
Wat is er gebeurd? Selecteer uit het onderstaande
Controleer of er al een rapport is over hetzelfde onderwerp
Zo ja, gelieve dan voor dit rapport te STEMMEN. Rapporten met de meeste stemmen krijgen VOORRANG!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Gedetailleerde beschrijving
-
• Kopieer en plak alsjeblieft de foutboodschap die je op je scherm ziet, indien van toepassing.
In person (and possibly live), tracking what pieces other players have played is mostly possible. But async, it's pretty impossible. Yes, I can reconstruct it from the log, or take personal notes every turn. Better, IMO, is if all players had access to all information -- how many of each component each player has remaining.
-
• Leg uit wat je wilde doen, wat je deed en wat er gebeurde
• Welke browser gebruik je?
Google Chrome v90
-
• Kopieer en plak alsjeblieft de tekst die in het Engels wordt getoond in plaats van in jouw taal. Als je een screenshot van de bug hebt (goede gewoonte), kun je een afbeeldingswebsite gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te delen. Is deze tekst beschikbaar in het vertaalsysteem? Zo ja, is deze meer dan 24 uur geleden vertaald?
In person (and possibly live), tracking what pieces other players have played is mostly possible. But async, it's pretty impossible. Yes, I can reconstruct it from the log, or take personal notes every turn. Better, IMO, is if all players had access to all information -- how many of each component each player has remaining.
• Welke browser gebruik je?
Google Chrome v90
-
• Gelieve jouw suggestie precies en beknopt uit te leggen zodat het zo makkelijk mogelijk is om te begrijpen wat je bedoelt.
In person (and possibly live), tracking what pieces other players have played is mostly possible. But async, it's pretty impossible. Yes, I can reconstruct it from the log, or take personal notes every turn. Better, IMO, is if all players had access to all information -- how many of each component each player has remaining.
• Welke browser gebruik je?
Google Chrome v90
-
• Wat stond op het scherm toen je geblokkeerd was (Leeg scherm? Een deel van de spelinterface? Foutboodschap?)
In person (and possibly live), tracking what pieces other players have played is mostly possible. But async, it's pretty impossible. Yes, I can reconstruct it from the log, or take personal notes every turn. Better, IMO, is if all players had access to all information -- how many of each component each player has remaining.
• Welke browser gebruik je?
Google Chrome v90
-
• Met welk onderdeel van de regels is geen rekening gehouden bij de BGA-versie?
In person (and possibly live), tracking what pieces other players have played is mostly possible. But async, it's pretty impossible. Yes, I can reconstruct it from the log, or take personal notes every turn. Better, IMO, is if all players had access to all information -- how many of each component each player has remaining.
-
• Is de inbreuk op de spelregels zichtbaar in de spelherhaling? Indien ja, bij welk zetnummer?
• Welke browser gebruik je?
Google Chrome v90
-
• Welke spelactie wilde je uitvoeren?
In person (and possibly live), tracking what pieces other players have played is mostly possible. But async, it's pretty impossible. Yes, I can reconstruct it from the log, or take personal notes every turn. Better, IMO, is if all players had access to all information -- how many of each component each player has remaining.
-
• Wat probeerde je te doen om deze spelactie te laten optreden?
-
• Wat gebeurde er toen je dit probeerde te doen (foutboodschap, melding op de statusbalk van het spel, ...)?
• Welke browser gebruik je?
Google Chrome v90
-
• In welke fase van het spel deed het probleem zich voor (wat was de huidige spelinstructie)?
In person (and possibly live), tracking what pieces other players have played is mostly possible. But async, it's pretty impossible. Yes, I can reconstruct it from the log, or take personal notes every turn. Better, IMO, is if all players had access to all information -- how many of each component each player has remaining.
-
• Wat gebeurde toen je deze spelactie probeerde (foutboodschap, melding op de statusbalk van het spel, ...)?
• Welke browser gebruik je?
Google Chrome v90
-
• Beschrijf alsjeblieft het probleem met de beeldweergave. Als je een screenshot van de bug hebt (goede gewoonte), kun je een afbeeldingswebsite gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te delen.
In person (and possibly live), tracking what pieces other players have played is mostly possible. But async, it's pretty impossible. Yes, I can reconstruct it from the log, or take personal notes every turn. Better, IMO, is if all players had access to all information -- how many of each component each player has remaining.
• Welke browser gebruik je?
Google Chrome v90
-
• Kopieer en plak alsjeblieft de tekst die in het Engels wordt getoond in plaats van in jouw taal. Als je een screenshot van de bug hebt (goede gewoonte), kun je een afbeeldingswebsite gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te delen. Is deze tekst beschikbaar in het vertaalsysteem? Zo ja, is deze meer dan 24 uur geleden vertaald?
In person (and possibly live), tracking what pieces other players have played is mostly possible. But async, it's pretty impossible. Yes, I can reconstruct it from the log, or take personal notes every turn. Better, IMO, is if all players had access to all information -- how many of each component each player has remaining.
• Welke browser gebruik je?
Google Chrome v90
-
• Gelieve jouw suggestie precies en beknopt uit te leggen zodat het zo makkelijk mogelijk is om te begrijpen wat je bedoelt.
In person (and possibly live), tracking what pieces other players have played is mostly possible. But async, it's pretty impossible. Yes, I can reconstruct it from the log, or take personal notes every turn. Better, IMO, is if all players had access to all information -- how many of each component each player has remaining.
• Welke browser gebruik je?
Google Chrome v90
Rapportgeschiedenis
Because in real life in it is difficult to remember how many pieces people have left unless you have a REALLY good memory (specially in 3-4 players games). Assisting players with such information, would, IMHO, ruin part of the spirit of the game. Of course, you can still browse through the logs and see that, but it is difficult, much more like in the live game. Perhaps as an option of people want it, but it will definitively not be by default.
Perhaps, showing the number of TOTAL pieces placed (or remaining) could be done as default, I have to think about this because as it does not require memory but just to count pieces on the booard, it is much more the spirit of the game.
There is a substantial cadre of gamers who play any game where all hidden information is strictly trackable (as it is here) with open hands, and that group also has significant overlap with the type of gamers who like these old school abstract placement euros. To have the option to play this way in the digital world would be great.
I'm not sure I get the "spirit of the game" argument. There's nothing else in the game to indicate that memory or bluffing etc is an intended mechanism or element of the competition in the game, nor do a player's holdings ever change except by removal (it's not like a hidden-money game where flows are going both in and out).
Thanks for considering the option.
With 2 players, it is a cut-throat battle where every move you make matters, and I don't even think that there is an argument for why that information shouldn't be displayed that's worth making. Why not just make it easier for both players when you are able to survey the complete state of the game by counting anyway?
With real competitive games against strangers where your ELO ranking is at stake though, this really just doesn’t make any sense.
Benj
Benj
Benj
Dit rapport aanvullen
- Andere tafel ID / zet ID
- Loste F5 het probleem op?
- Kwam het probleem meerdere keren voor? Altijd? Willekeurig?
- Als je een screenshot van de bug hebt (goede gewoonte), kun je een afbeeldingswebsite gebruiken (bijvoorbeeld snipboard.io) om deze te uploaden en de link hier te delen.
