How pioix/2026-tpf-g02 works
Gartic Pio is a multiplayer drawing-and-description game. The player flow runs from account entry through room creation or joining, alternating text and drawing rounds, then synchronized album revelation; the product also includes past-album browsing and administrator tools. The backend combines HTTP routes with Socket.IO room and round logic, while MySQL supports account and administration data. Some frontend pages and persistence features are documented but not sampled, so those links reflect README statements rather than inspected implementation details.
Main entry points: index.js Express and Socket.IO · app/page.js Login and signup · useSocket.js Socket client · menu/page.js Game menu
Components 21
Player experience
- Login and signup
frontend/src/app/page.js - Game menu
frontend/src/app/menu/page.js - Room lobby
frontend/src/app/salas/page.js - Socket client
frontend/src/hooks/useSocket.js - Write phase
frontend/src/app/escribir/page.js - Draw phase
frontend/src/app/dibujar/page.js - Album reveal
frontend/src/app/albumsrevelacion/page.js - Past albums
frontend/src/app/albumsrevelacion/page.js
Realtime game
- Express and Socket.IO
backend/index.js - Room HTTP routes
backend/routes/salas.js - Room state
backend/modulos/logicaSalas.js - Round and album logic
backend/modulos/logicaPartida.js
Accounts and admin
- Authentication routes
backend/routes/auth.js - Admin panel
frontend/src/app/admin/page.js - Admin operations
backend/routes/admin.js - MySQL access
backend/modulos/mysql.js - MySQL database
Shared interface
Other components
- Player
Connections 26
- Player → Login and signup: opens
README.md - Login and signup → Authentication routes: HTTP login
frontend/src/app/page.js - Authentication routes → MySQL access: queries
backend/routes/auth.js - MySQL access → MySQL database: reads and writes
- Login and signup → Game menu: routes player
frontend/src/app/page.js - Game menu → Room HTTP routes: creates room
README.md - Player → Room lobby: joins room
README.md - Room lobby → Socket client: uses sockets
README.md - Socket client → Express and Socket.IO: sends events
README.md - Room HTTP routes → Room state: creates and checks
backend/routes/salas.js - Express and Socket.IO → Room state: manages room state
backend/index.js - Express and Socket.IO → Round and album logic: requests round tasks
backend/index.js - Express and Socket.IO → Write phase: sends round task
README.md - Express and Socket.IO → Draw phase: sends round task
README.md - Write phase → Socket client: submits text
README.md - Draw phase → Socket client: submits drawing
README.md - Express and Socket.IO → Album reveal: synchronizes albums
README.md - Player → Past albums: browses albums
README.md - Login and signup → Admin panel: routes admin
frontend/src/app/page.js - Admin panel → Admin operations: fetches admin data
frontend/src/app/admin/page.js - Admin operations → MySQL access: queries
backend/routes/admin.js - Express and Socket.IO → Authentication routes: registers routes
backend/index.js - Express and Socket.IO → Admin operations: registers routes
backend/index.js - Login and signup → Button: renders
frontend/src/app/page.js - Login and signup → Avatar: shows user identity
README.md - Game menu → Logo: shows branding
README.md