How iee-ihu-gr-course1941/adise24_cubus works
Cubus is a turn-based Blokus game with a Laravel backend, React client, REST API, and WebSocket updates. Players authenticate, create or join a lobby, then request moves; the backend validates moves, updates game state, and broadcasts lobby or board changes for other players to display. The graph includes the documented profile, lobby, game, and real-time capabilities. Several client modules and route details were not excerpted, so their internal call relationships are omitted or marked unverified.
Main entry points: web.php Web Routes · AuthService.php Authentication · GameSessionController.php Lobby API · GameController.php Game API
Components 24
Backend API
- Web Routes
routes/web.php - Authentication
app/Http/Controllers/AuthService.php - Profile API
app/Http/Controllers/UserController.php - Lobby API
app/Http/Controllers/GameSessionController.php - Authorization
app/Http/Middleware/ManageAuthorization.php
Game State
- Game API
app/Http/Controllers/GameController.php - Game Sessions
app/Models/GameSession.php - User Model
app/Models/User.php - Database
config/database.php
React Client
- Client Entry
resources/js/app.tsx - Game Pages
resources/js/Pages/Game.tsx - 3D Experience
resources/js/Game/Experience.tsx - Game Interface
resources/js/Game/Interface.tsx - Board Rendering
resources/js/Game/Board/Board.tsx - Board State
resources/js/Store/board_state.ts - Session Network
resources/js/network/session_network.ts
Realtime
- Server Events
resources/js/Connection/useServerEvents.ts - User Events
resources/js/Connection/useUserEvents.ts - Broadcast Events
app/Events/BoardUpdateEvent.php - Lobby Events
app/Events/ConnectEvent.php - Login Event
app/Events/LoginEvent.php
Other components
- Player
- IEE Login
- WebSockets
Connections 30
- Player → Web Routes: requests API
- Web Routes → Profile API: routes profile
routes/web.php - Web Routes → Lobby API: routes lobby
routes/web.php - Web Routes → Game API: routes game
routes/web.php - Web Routes → Authorization: applies middleware
routes/web.php - Profile API → Authentication: uses authentication
app/Http/Controllers/UserController.php - Lobby API → Authentication: gets user
app/Http/Controllers/GameSessionController.php - Game API → Authentication: gets user
app/Http/Controllers/GameController.php - Authentication → IEE Login: requests login profile
app/Http/Controllers/AuthService.php - Authentication → User Model: finds or creates
app/Http/Controllers/AuthService.php - Authorization → Authentication: checks identity
app/Http/Middleware/ManageAuthorization.php - Lobby API → Game Sessions: creates and updates
app/Http/Controllers/GameSessionController.php - Game API → Game Sessions: reads and updates
app/Http/Controllers/GameController.php - User Model → Game Sessions: queries current session
app/Models/User.php - Game Sessions → Database: persists state
- Lobby API → Lobby Events: broadcasts lobby changes
app/Http/Controllers/GameSessionController.php - Game API → Broadcast Events: broadcasts valid move
app/Http/Controllers/GameController.php - Profile API → Login Event: broadcasts login result
app/Http/Controllers/UserController.php - Lobby Events → WebSockets: broadcasts
- Broadcast Events → WebSockets: broadcasts
- Login Event → WebSockets: broadcasts
- Client Entry → Game Pages: starts client pages
- Game Pages → 3D Experience: renders game
- Game Pages → Game Interface: renders controls
- 3D Experience → Board Rendering: renders board
- Board Rendering → Board State: reads game state
- Session Network → Web Routes: requests game API
- User Events → Server Events: uses event listener
resources/js/Connection/useUserEvents.ts - Server Events → WebSockets: listens for updates
- Server Events → Board State: updates client state