#41790: "Never skip any player, even if they have abandoned the game"
Hva handler denne rapporten om?
Hva har skjedd, eller hva gjelder det? Vennligst velg
Hva har skjedd, eller hva gjelder det? Vennligst velg
Vennligst sjekk om det allerede er en rapport om samme emne
Hvis ja, vennligst STEM på denne rapporten. Rapporter med flest stemmer er gitt PRIORITET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaljert beskrivelse
-
• Vennligst kopier/lim inn feilmeldingen du ser på skjermen, om mulig.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• Vennligst forklar hva du ønsket å gjøre, samt hva du faktisk gjorde og hva som skjedde
• Hvilken nettleser bruker du?
Firefox
-
• Vennligst kopier / lim inn teksten som vises på engelsk i stedet for språket ditt. Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet her.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• Er denne teksten tilgjengelig i translation system? Hvis ja, har den blitt oversatt i mer enn 24 timer?
• Hvilken nettleser bruker du?
Firefox
-
• Vennligst forklar ditt forslag nøyaktig og konsistent slik at det er så enkelt som mulig å forstå hva du mener.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
• Hvilken nettleser bruker du?
Firefox
-
• Hva ble vist på skjermen når du ble blokkert (Tom skjerm? Del av spillgrensesnittet? Feilmelding?)
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
• Hvilken nettleser bruker du?
Firefox
-
• Hvilken del av reglene ble ikke respektert av BGA-tilpasningen
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• Er regelbruddet tydelig i spilloggen? Hvis ja, Hvilket trekknummer?
• Hvilken nettleser bruker du?
Firefox
-
• Hva var spillhandlingen du ønsket å gjøre?
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• Hva prøvde du å gjøre for å trigge denne spillhandlingen?
-
• Hva skjer når du prøver å gjøre dette (feilmelding, meldingsstatus for meldingsfelt, ...)?
• Hvilken nettleser bruker du?
Firefox
-
• På hvilket tidspunkt i spillet oppsto problemet (hva var den daværende spillinstruksjonen)?
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• Hva skjer når du forsøker å gjøre en spillhandling (feilmelding, spillstatusfeltmelding, ...)?
• Hvilken nettleser bruker du?
Firefox
-
• Vennligst beskriv visningsproblemet. Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet her.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
• Hvilken nettleser bruker du?
Firefox
-
• Vennligst kopier / lim inn teksten som vises på engelsk i stedet for språket ditt. Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet her.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• Er denne teksten tilgjengelig i translation system? Hvis ja, har den blitt oversatt i mer enn 24 timer?
• Hvilken nettleser bruker du?
Firefox
-
• Vennligst forklar ditt forslag nøyaktig og konsistent slik at det er så enkelt som mulig å forstå hva du mener.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
• Hvilken nettleser bruker du?
Firefox
Rapporthistorikk
Maybe this issue would be better addressed to BGA management.
Legg til noe i denne rapporten
- En annen bord ID / flytt ID
- Løste F5 problemet?
- Oppstod problemet gjentatte ganger? Hver gang? Tilfeldig?
- Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet her.
