How sarum4n3/ft_transcendence works
Transcendence is an early-stage multiplayer game project with a placeholder web deliverable. The current web workflow is a browser request routed through nginx to a Node.js static-file server, which serves files from web/public; the intended WebGL game is served as part of those assets. Separately, Unity source contains player movement, combat, stats, and procedural terrain; networking and the advertised game modes are not yet wired in. The graph reflects README documentation and sampled server code; unsampled Unity behavior and deployment configuration are not inferred.
Main entry points: UnityProject Unity source · nginx HTTPS proxy · server.js Static server · public Static assets
Components 15
Web delivery
- Web browser
- HTTPS proxy
web/nginx - Static server
web/server.js - Static assets
web/public - WebGL game build
web/public/game
Unity game
- Unity source
UnityProject - Player movement
UnityProject/Assets - Combat and stats
UnityProject/Assets - Procedural terrain
UnityProject/Assets/Prefabs/Terrain - Multiplayer modes
UnityProject
Game content
- Class kits
UnityProject/Assets/Data/Player/ClassKits - Enemy kit
UnityProject/Assets/Data/EnemyKits - Character animations
UnityProject/Assets/Animations - Terrain assets
UnityProject/Assets/Resources/Terrain
Other components
- Player
Connections 10
- Player → Web browser: uses
README.md - Web browser → HTTPS proxy: requests app
README.md - HTTPS proxy → Static server: proxies requests
README.md - Static server → Static assets: serves files
web/server.js - Static assets → WebGL game build: includes game
README.md - Unity source → WebGL game build: produces build
README.md - Unity source → Player movement: implements
README.md - Unity source → Combat and stats: implements
README.md - Unity source → Procedural terrain: generates
README.md - Unity source → Multiplayer modes: plans modes
README.md