Alle Meldungen
P.I. Meldungen
#9907: "Investigator "orders" discs and cubes in a way that gives away extra information"
notabug: Das ist kein Fehler
2
Worum geht es bei dieser Meldung?
Was ist passiert? Bitte wähle unten aus
Regeln: Eine Regel des Spiels wurde nicht beachtet
Detaillierte Beschreibung
• Welcher Teil der Spielregel wurde durch die BGA-Adaption nicht beachtet?
When sending an investigator to a location, discs and cubes are placed in the order "Suspect, Location, Crime". In a case where at least one disc and at least one cube is connected to the same location, this gives away which aspect of the crime is associated with each disc/cube. Please see the attached screenshot for an example.• Ist der Regelverstoß in der Spielwiederholung zu sehen? Falls ja, bei welcher Zugnummer?
Move #39• Welchen Browser benutzt du?
Google Chrome v66
Meldungshistorie
12. Mai 2018 20:17 • Octrinity • Der Fehler wurde von den Entwicklern noch nicht nachvollzogen:
Screencapped here: imgur.com/a/jbBckr0
In this screenshot, I'm the red player and the solution of my case is Pinky, Central Station, Bank Job (which was solved on my next turn). This is even further spoiled due to the order of how investigators marked their info - Trocadero and Central Station both put discs and cubes in a specific yet different order consistent with the "Suspect, Location, Crime" order specified earlier.
In this screenshot, I'm the red player and the solution of my case is Pinky, Central Station, Bank Job (which was solved on my next turn). This is even further spoiled due to the order of how investigators marked their info - Trocadero and Central Station both put discs and cubes in a specific yet different order consistent with the "Suspect, Location, Crime" order specified earlier.
13. Mai 2018 14:45 • fa81 • Das ist kein Fehler:
Sorry to disappoint you, but this would have been really a bad bug, so I considered it, of course, during development.
1. The backend shuffles in which order it checks the various aspects. That not even required as only 1 single message goes to the frontend, but in case this ever changes even the order in which we check would remain hidden.
2. The client-side code (i.e. the game log message that is sent to all players) only ever gets to see the number of cubes/discs the frontend has to place.
3. the order in which the tokens appear on the investigator tile is based on a simple style sheet and depends only on the number and types (cubes vs. discs) on the tile. Each token does not "know" which aspect it belongs to until it is moved to the corresponding tile due to an evidence card action.
In short: There is no information leaking when placing and investigator. If it appears to do, like in your examples, it's coincidence.
If you want to I can show you the code for review. I actually want to open-source it, which I plan to do anyway, I just have to put a different license the the artwork files.
1. The backend shuffles in which order it checks the various aspects. That not even required as only 1 single message goes to the frontend, but in case this ever changes even the order in which we check would remain hidden.
2. The client-side code (i.e. the game log message that is sent to all players) only ever gets to see the number of cubes/discs the frontend has to place.
3. the order in which the tokens appear on the investigator tile is based on a simple style sheet and depends only on the number and types (cubes vs. discs) on the tile. Each token does not "know" which aspect it belongs to until it is moved to the corresponding tile due to an evidence card action.
In short: There is no information leaking when placing and investigator. If it appears to do, like in your examples, it's coincidence.
If you want to I can show you the code for review. I actually want to open-source it, which I plan to do anyway, I just have to put a different license the the artwork files.
14. Mai 2018 8:52 • Octrinity • Das ist kein Fehler:
OP here. Played another game where I expected this to show up but didn't (i.e. the order I specified in my original report wasn't followed) and on this basis agree that I jumped to an incorrect conclusion and there is no bug. Game number is 40301294 if you want to see for your own records/confidence. I think you can safely close this issue. Thanks for taking a look and giving further explanation.
Ergänze diese Meldung
Bitte erwähne hier alles, was bedeutsam sein könnte, um diesen Fehler nachzuvollziehen oder deinen Vorschlag zu verstehen:
- Eine weitere Tisch-ID/Zug-ID
- Konnte F5 das Problem lösen?
- Trat das Problem öfter auf? Jedes Mal? Zufällig?
- Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
