#129385: "It is possible to see other players' destinations by inspecting the websocket connection"

• Kérjük másold be a hiba üzenetet, amit kaptál, ha volt ilyen.
Each player's destinations should only be made known to them.
• Kérjük mondd el, hogy mit szerettél volna csinálni, mit csináltál és mi történt
It is visible on game replay, and also visible when playing a new game.

How to reproduce:
1. Start/Join a new game.
2. Open the Chrome devtools to the Network tab.
3. Refresh the game webpage.
4. Find the websocket connection that contains moves (websocket connections are easily identified by status code 101 (protocol upgrade); there should be two websockets and the one that contains moves is the second one).
5. Click on it to look at the incoming websocket packets.
6. Keep some destinations using the game UI.
7. Observe that a websocket packet will be received containing some JSON, which contains `\"type\":\"destinationsPicked\"`. This same packet also contains the pairs of cities that form each destination you picked. They look like `\"from\":6,\"to\":31`, where "6" and "31" will be replaced by the actual destinations you picked. These numbers are the cities on the map. While it isn't possible to match numbers to cities right now, it is possible once you have played enough games.
8. Go back to step 1, and repeat until you have figured out which destination each number refers to.
9. Go back to step 1, but now observe that for step 7, you actually receive a packet anytime any player chooses their cards, and the packet contains the player's username as well as the destinations that they have to connect.

Now I have not built a game on BGA before, but a quick read of boardgamearena.com/doc/Tutorial_hearts suggests that it is possible to notify just one player (to tell them their private information). If that is implementable, it should be implemented to prevent cheating.
• Milyen böngészőt használsz?
Google Chrome v126

• Kérjük, másold az angolul megjelenített szöveget, ahelyett, hogy lefordítanád a Te nyelvedre! Ha van screenshot-od erről a bugról (ajánlott), használd a Imgur.com, hogy feltöltsd, majd másold be a linket.
Each player's destinations should only be made known to them.
• Létezik ez a szöveg a fordítási rendszerben? Ha igen, több mint 24 órája lett lefordítva?
It is visible on game replay, and also visible when playing a new game.

How to reproduce:
1. Start/Join a new game.
2. Open the Chrome devtools to the Network tab.
3. Refresh the game webpage.
4. Find the websocket connection that contains moves (websocket connections are easily identified by status code 101 (protocol upgrade); there should be two websockets and the one that contains moves is the second one).
5. Click on it to look at the incoming websocket packets.
6. Keep some destinations using the game UI.
7. Observe that a websocket packet will be received containing some JSON, which contains `\"type\":\"destinationsPicked\"`. This same packet also contains the pairs of cities that form each destination you picked. They look like `\"from\":6,\"to\":31`, where "6" and "31" will be replaced by the actual destinations you picked. These numbers are the cities on the map. While it isn't possible to match numbers to cities right now, it is possible once you have played enough games.
8. Go back to step 1, and repeat until you have figured out which destination each number refers to.
9. Go back to step 1, but now observe that for step 7, you actually receive a packet anytime any player chooses their cards, and the packet contains the player's username as well as the destinations that they have to connect.

Now I have not built a game on BGA before, but a quick read of boardgamearena.com/doc/Tutorial_hearts suggests that it is possible to notify just one player (to tell them their private information). If that is implementable, it should be implemented to prevent cheating.
• Milyen böngészőt használsz?
Google Chrome v126

• Kérjük magyarázd el a javaslatodat pontosan és tömören, hogy amennyire lehet, könnyen érthető legyen, mire is gondolsz!
Each player's destinations should only be made known to them.
• Milyen böngészőt használsz?
Google Chrome v126

• Mit láttál a képernyőn, amikor blokkolva lettél? (Üres képernyő? A játék felületének egy részét? Hiba üzenet?)
Each player's destinations should only be made known to them.
• Milyen böngészőt használsz?
Google Chrome v126

• A szabályok melyik részét nem vette figyelembe a BGA adaptáció
Each player's destinations should only be made known to them.
• Ez a szabály áthágása látható a visszajátszásban? Ha igen, melyik lépésszámnál?
It is visible on game replay, and also visible when playing a new game.

How to reproduce:
1. Start/Join a new game.
2. Open the Chrome devtools to the Network tab.
3. Refresh the game webpage.
4. Find the websocket connection that contains moves (websocket connections are easily identified by status code 101 (protocol upgrade); there should be two websockets and the one that contains moves is the second one).
5. Click on it to look at the incoming websocket packets.
6. Keep some destinations using the game UI.
7. Observe that a websocket packet will be received containing some JSON, which contains `\"type\":\"destinationsPicked\"`. This same packet also contains the pairs of cities that form each destination you picked. They look like `\"from\":6,\"to\":31`, where "6" and "31" will be replaced by the actual destinations you picked. These numbers are the cities on the map. While it isn't possible to match numbers to cities right now, it is possible once you have played enough games.
8. Go back to step 1, and repeat until you have figured out which destination each number refers to.
9. Go back to step 1, but now observe that for step 7, you actually receive a packet anytime any player chooses their cards, and the packet contains the player's username as well as the destinations that they have to connect.

Now I have not built a game on BGA before, but a quick read of boardgamearena.com/doc/Tutorial_hearts suggests that it is possible to notify just one player (to tell them their private information). If that is implementable, it should be implemented to prevent cheating.
• Milyen böngészőt használsz?
Google Chrome v126

• Melyik játékbeli akciót akartad csinálni, amikor a hiba előjött?
Each player's destinations should only be made known to them.
• Mit akartál csinálni, hogy ezt a játékbeli akciót elindíthasd?
It is visible on game replay, and also visible when playing a new game.

How to reproduce:
1. Start/Join a new game.
2. Open the Chrome devtools to the Network tab.
3. Refresh the game webpage.
4. Find the websocket connection that contains moves (websocket connections are easily identified by status code 101 (protocol upgrade); there should be two websockets and the one that contains moves is the second one).
5. Click on it to look at the incoming websocket packets.
6. Keep some destinations using the game UI.
7. Observe that a websocket packet will be received containing some JSON, which contains `\"type\":\"destinationsPicked\"`. This same packet also contains the pairs of cities that form each destination you picked. They look like `\"from\":6,\"to\":31`, where "6" and "31" will be replaced by the actual destinations you picked. These numbers are the cities on the map. While it isn't possible to match numbers to cities right now, it is possible once you have played enough games.
8. Go back to step 1, and repeat until you have figured out which destination each number refers to.
9. Go back to step 1, but now observe that for step 7, you actually receive a packet anytime any player chooses their cards, and the packet contains the player's username as well as the destinations that they have to connect.

Now I have not built a game on BGA before, but a quick read of boardgamearena.com/doc/Tutorial_hearts suggests that it is possible to notify just one player (to tell them their private information). If that is implementable, it should be implemented to prevent cheating.
• Mi történt amikor megpróbáltad ezt (hiba üzenet, játék státusz üzenet, ...)?
• Milyen böngészőt használsz?
Google Chrome v126

• A játék melyik lépésénél lépett fel a probléma? (mi volt a kiírt utasítás?)
Each player's destinations should only be made known to them.
• Mi történt amikor megpróbáltad ezt az akciót (hiba üzenet, játék státusz üzenet, ...)?
It is visible on game replay, and also visible when playing a new game.

How to reproduce:
1. Start/Join a new game.
2. Open the Chrome devtools to the Network tab.
3. Refresh the game webpage.
4. Find the websocket connection that contains moves (websocket connections are easily identified by status code 101 (protocol upgrade); there should be two websockets and the one that contains moves is the second one).
5. Click on it to look at the incoming websocket packets.
6. Keep some destinations using the game UI.
7. Observe that a websocket packet will be received containing some JSON, which contains `\"type\":\"destinationsPicked\"`. This same packet also contains the pairs of cities that form each destination you picked. They look like `\"from\":6,\"to\":31`, where "6" and "31" will be replaced by the actual destinations you picked. These numbers are the cities on the map. While it isn't possible to match numbers to cities right now, it is possible once you have played enough games.
8. Go back to step 1, and repeat until you have figured out which destination each number refers to.
9. Go back to step 1, but now observe that for step 7, you actually receive a packet anytime any player chooses their cards, and the packet contains the player's username as well as the destinations that they have to connect.

Now I have not built a game on BGA before, but a quick read of boardgamearena.com/doc/Tutorial_hearts suggests that it is possible to notify just one player (to tell them their private information). If that is implementable, it should be implemented to prevent cheating.
• Milyen böngészőt használsz?
Google Chrome v126

• Kérjük, írd le a megjelenítési hibát! Ha van screenshot-od erről a bugról (ajánlott), használd a Imgur.com, hogy feltöltsd, majd másold be a linket.
Each player's destinations should only be made known to them.
• Milyen böngészőt használsz?
Google Chrome v126

• Kérjük, másold az angolul megjelenített szöveget, ahelyett, hogy lefordítanád a Te nyelvedre! Ha van screenshot-od erről a bugról (ajánlott), használd a Imgur.com, hogy feltöltsd, majd másold be a linket.
Each player's destinations should only be made known to them.
• Létezik ez a szöveg a fordítási rendszerben? Ha igen, több mint 24 órája lett lefordítva?
It is visible on game replay, and also visible when playing a new game.

How to reproduce:
1. Start/Join a new game.
2. Open the Chrome devtools to the Network tab.
3. Refresh the game webpage.
4. Find the websocket connection that contains moves (websocket connections are easily identified by status code 101 (protocol upgrade); there should be two websockets and the one that contains moves is the second one).
5. Click on it to look at the incoming websocket packets.
6. Keep some destinations using the game UI.
7. Observe that a websocket packet will be received containing some JSON, which contains `\"type\":\"destinationsPicked\"`. This same packet also contains the pairs of cities that form each destination you picked. They look like `\"from\":6,\"to\":31`, where "6" and "31" will be replaced by the actual destinations you picked. These numbers are the cities on the map. While it isn't possible to match numbers to cities right now, it is possible once you have played enough games.
8. Go back to step 1, and repeat until you have figured out which destination each number refers to.
9. Go back to step 1, but now observe that for step 7, you actually receive a packet anytime any player chooses their cards, and the packet contains the player's username as well as the destinations that they have to connect.

Now I have not built a game on BGA before, but a quick read of boardgamearena.com/doc/Tutorial_hearts suggests that it is possible to notify just one player (to tell them their private information). If that is implementable, it should be implemented to prevent cheating.
• Milyen böngészőt használsz?
Google Chrome v126

• Kérjük magyarázd el a javaslatodat pontosan és tömören, hogy amennyire lehet, könnyen érthető legyen, mire is gondolsz!
Each player's destinations should only be made known to them.
• Milyen böngészőt használsz?
Google Chrome v126

Miről szól ez a jelentés?

Mi történt? Kérünk, válassz az alábbiakból

Mi történt? Kérünk, válassz az alábbiakból

Kérjük ellenőrizd, hogy nincs-e azonos tárggyal már jelentés!

Részletes leírás

Bejelentés előzmények

Hozzáadni valamit a jelentéshez

Változtasd meg a bejelentés státuszát erre:

Segítség

Hozzájárulás

Kövess bennünket