How samer-gharsalli/final-projet works
The tree contains several SDL/C programs rather than one clearly integrated game: a TUNESCA application, a character-creation program, a samurai player demo, and standalone options and score screens. The sampled TUNESCA code places menu, character creation, options, and score behavior in one large source file; its full event flow is not shown, so no internal scene transitions are asserted. The samurai demo’s calls into its player module are explicit. The README is empty.
Main entry points: stat_game.c Character creation · samurai/main.c Demo loop · score.c Score screens · main menu/main.c Game app
Components 9
TUNESCA app
- Game app
main menu/main.c
Character creator
- Character creation
satar game/stat_game.c
Samurai demo
- Demo loop
samurai/main.c - Player runtime
samurai/player.c
Standalone screens
- Options screen
option/option.c - Score screens
score/score.c - Score file
score/score.c
Other components
- Player
- Image host
Connections 8
- Player → Game app: uses
main menu/main.c - Player → Character creation: uses
satar game/stat_game.c - Character creation → Image host: downloads images
satar game/stat_game.c - Player → Demo loop: controls
samurai/main.c - Demo loop → Player runtime: calls player API
samurai/main.c - Player → Options screen: uses
option/option.c - Player → Score screens: uses
score/score.c - Score screens → Score file: reads and writes
score/score.c