CASE STUDY · 1337 / 42 validated project
so_long
A 2D top-down game built with MiniLibX.
- Role
- 1337 / 42 Developer
- Access
- 1337 / 42 validated project
Context
A 2D top-down game built with MiniLibX. It includes map parsing, path validation, sprite rendering, keyboard input, collision handling, collectible tracking, and clean shutdown behavior.
My responsibility
Built and validated through the 1337 / 42 project curriculum, with direct responsibility for implementation, debugging, testing, and evaluation requirements.
System scheme
Engineering scheme
Validated 2D game loop
Map correctness is established before the render loop begins, keeping movement, collision, collection, and exit state deterministic.
- 01
Map loader
Read and normalize the level file.
- 02
Map validator
Check shape, walls, entities, and reachable objectives.
- 03
Scene setup
Load textures and initialize the MiniLibX window.
- 04
Input loop
Translate keyboard events into candidate player movement.
- 05
Collision state
Update movement, collectibles, and exit eligibility.
- 06
Frame render
Draw tiles, sprites, and counters, then cleanly shut down.
Technical scope
Implementation details
- ✓Map loader: Read and normalize the level file.
- ✓Map validator: Check shape, walls, entities, and reachable objectives.
- ✓Scene setup: Load textures and initialize the MiniLibX window.
- ✓Input loop: Translate keyboard events into candidate player movement.
- ✓Collision state: Update movement, collectibles, and exit eligibility.
- ✓Frame render: Draw tiles, sprites, and counters, then cleanly shut down.
Engineering focus
- →Path validation remained an explicit concern across the implementation.
- →Resource cleanup remained an explicit concern across the implementation.
- →Event handling remained an explicit concern across the implementation.
- →Frame state remained an explicit concern across the implementation.
Project gallery
Need a system like this?
Tell me about the workflow, integration, or backend problem.