Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> If it's creating a 3-player game, Player 3 conceding shouldn't also make Player 2 concede.

It stays a 2 player game, his code has to figure out which "seat" index his account is, and then has the bot join the other seat index.

The problem is that they're not validating that the joining user is the correct user that should be in that seat.

There's also the thought that you shouldn't allow a player to connect to an already connected seat. But since this game is also available on mobile, you probably want disconnection timeouts to be fairly long, and you don't want to interrupt a player who briefly disconnected and then reconnected before the timeout has recognized their early connection is broken. I've seen this in other games, where you try to reconnect and get a "cannot join game in progress" for about 10 seconds until you're actually able to reconnect.

Basically imagine showing up to an MTG tournament at your local game store, pushing someone out of their seat, sitting in it and shouting "I concede!". And then the judges agree that player B forfeited the game because the person in their chair declared it.



Thanks for this simple explanation! I got distracted by the [FULL VERSION] Magnus Carlsen Blind & Timed Chess Simul at the Sohn Conference in NYC (https://www.youtube.com/watch?v=xmXwdoRG43U) video and now I'm late for dinner!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: