Difference between revisions of "Resume Game"
From Worms Knowledge Base
(Initial resume page) |
|||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | Based on [http://feedback.worms2d.info/pages/general/suggestions/72462 | + | Based on [http://feedback.worms2d.info/pages/general/suggestions/72462 original idea] from feedback page. |
=== Ideas for resuming online games === | === Ideas for resuming online games === | ||
| − | [http://en.wikipedia.org/wiki/Public-key_cryptography | + | To securely resume a game, [http://en.wikipedia.org/wiki/Public-key_cryptography public-key cryptography] is applied. First, each player has a private key and public, which is randomly generated one-time by W:A. |
| − | + | ||
| − | The game is suspended at the end of a turn, when all players agree to do so. The host would type in the command '/ | + | The game is suspended at the end of a turn, when all players agree to do so. The host would type in the command '/suspend' during a turn, and when the turn's completed, the game would pause. All players would need to agree to suspend the game. |
| − | The player's public keys are then shared. Each player sends an encrypted message to the other players, each one receiving a unique message. When a game | + | The player's public keys are then shared. Each player sends an encrypted message to the other players, each one receiving a unique message. When a game is about to resume, the players return the messages they received to the other players. |
E.g. Players 1-3 exchange public keys, then encrypted messages are sent. | E.g. Players 1-3 exchange public keys, then encrypted messages are sent. | ||
| − | P1 to P2: Code is 527 | + | * P1 to P2: Code is 527 |
| − | P1 to P3: Code is 167 | + | * P1 to P3: Code is 167 |
| − | P2 to P1: Code is 502 | + | * P2 to P1: Code is 502 |
| − | P2 to P3: Code is 119 | + | * P2 to P3: Code is 119 |
| − | P3 to P1: Code is 293 | + | * P3 to P1: Code is 293 |
| − | P3 to P2: Code is 954 | + | * P3 to P2: Code is 954 |
When resuming, the messages are returned to sender. | When resuming, the messages are returned to sender. | ||
| − | + | * P2 to P1: Your code was 527 | |
| − | + | * P3 to P1: Your code was 167 | |
| − | + | * P1 to P2: Your code was 502 | |
| − | + | * P3 to P2: Your code was 119 | |
| − | + | * P1 to P3: Your code was 293 | |
| − | + | * P2 to P3: Your code was 954 | |
| + | |||
| + | When the messages are confirmed, the game resumes. | ||
Revision as of 13:20, 8 December 2008
Based on original idea from feedback page.
Ideas for resuming online games
To securely resume a game, public-key cryptography is applied. First, each player has a private key and public, which is randomly generated one-time by W:A.
The game is suspended at the end of a turn, when all players agree to do so. The host would type in the command '/suspend' during a turn, and when the turn's completed, the game would pause. All players would need to agree to suspend the game.
The player's public keys are then shared. Each player sends an encrypted message to the other players, each one receiving a unique message. When a game is about to resume, the players return the messages they received to the other players.
E.g. Players 1-3 exchange public keys, then encrypted messages are sent.
- P1 to P2: Code is 527
- P1 to P3: Code is 167
- P2 to P1: Code is 502
- P2 to P3: Code is 119
- P3 to P1: Code is 293
- P3 to P2: Code is 954
When resuming, the messages are returned to sender.
- P2 to P1: Your code was 527
- P3 to P1: Your code was 167
- P1 to P2: Your code was 502
- P3 to P2: Your code was 119
- P1 to P3: Your code was 293
- P2 to P3: Your code was 954
When the messages are confirmed, the game resumes.
