multiplayer distinction

This commit is contained in:
Shaheed Azaad
2025-07-16 16:46:27 +02:00
parent dc2f68a2b4
commit 02734040cb
9 changed files with 678 additions and 239 deletions

View File

@@ -1,12 +1,11 @@
---
description: General structure of the app
globs:
alwaysApply: true
---
# Structure
- Read, but don't edit @README.md to get an idea of how the app should work.
- Where possible, the app should be separated into an API and frontend components.
- Tests should be written as the app is developed.
- Use package.json to ensure you're using the correct packages to implement features and not installing redundant packages or reinventing the wheel.
- User superforms for all forms
- User superforms for all forms
- For now, we will keep multiplayer and single player experiment serving, queuing, and session logic completely separate, even if it means overlapping and redundant code. We will optimise later.