server-side pong: develop server-side pong game logic

[trsctr]

Branch Name: feature/006-server-side-game-logic

Description:

Develop the backend business logic to manage game mechanics for a Pong game, including ball movement, paddle interactions, scoring mechanisms, and real-time synchronization of game state between players. Refer to game design doc in wiki for more information.

Tasks:

1. Implement Methods Defined in Previous Issue:

   • [x] Implement the methods defined in the task (feature/004-define-game-mechanics-and-classes) for player paddles, ball, game session, and any other relevant entities.

2. Calculate Ball Movements:

   • [x] Implement algorithms to calculate the trajectory and movement of the ball based on game rules (e.g., bouncing off paddles, walls).

3. Receive and Validate Paddle Positions:

   • [x] Develop server-side logic to receive updated paddle positions from clients.
   • [x] Validate incoming paddle positions to ensure they conform to game rules and prevent malicious inputs.

4. Manage Game State:

   • [x] Design and implement mechanisms to manage and update the game state (e.g., ball position, scores) on the server.
   • [x] Ensure consistency and synchronization of game state updates between players in real-time.

5. Scoring Mechanisms:

   • [x] Implement logic to update scores based on game events (e.g., scoring goals).
   • [x] Ensure accurate scoring updates for player actions during gameplay.

Definition of Done:

• Business logic developed and integrated to enforce game rules effectively.
• Unit tests written and passed to validate game mechanics and rules.
• Code reviewed and approved by team members familiar with game development principles.

Acceptance Criteria:

• Business logic tested and validated through unit tests.
• Code reviewed and approved by team members.
• Integration with WebSocket for real-time synchronization to be completed in a separate task.

[trsctr]

at the moment: ball movement exists, although bounces from collision detection with paddles is missing, as well as bouncing from paddles. collision and bounce with wall exists.

[trsctr]

Game now runs in the server and is already somewhat integrated with channels, but can only run a single game session for now. Ditching django for this and configuring the game server in socket.io, that's a separate task