-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Matchmaking #5
Comments
|
May need a small REST-like service instead. |
Will scale the project down for now and start with "homemade" matchmaking, i.e. joining players will have to copy-paste an address string from the host. Can easily add stuff on top of that to list open rooms. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GET/PUT /rooms
GET/PUT /players
Old idea
IRC channels are game rooms.
For now we'll need a max of 8 users per channel, but in the future we can
+v
players, and-v
spectators, and allow up to 32 users per channel.The first player to join a channel creates it and gets
+o
.+o
is the host. Hosts can start a game.When a game starts, a CTCP message should be sent to the channel. Like how IRC clients implement /me:
CTCP #channel ACTION text
, we could useCTCP #room GAME_STARTING
. DirectPlay connection info needs to be sent to the players, which could either be a message to the room or to individual players:CTCP nick GAME_LAUNCH <host_ip> <dp_session_guid>
.May prefer to use a slightly modified IRC server that doesn't allow you to fake CTCP messages as easily (perhaps by sending them from the server, and not the room host)
The text was updated successfully, but these errors were encountered: