RFSF National SKILLS Competition 2025:

CATEGORY OF PROGRAMMING

GAME PROGRAMMING: Artifacts collecting game

LEVELS: TSS

Goal of the Challenge

Design and build a compact, browser-based labyrinth game named FutureskillsArtifact. The
game simulates a futuristic journey where the player must navigate three procedurally generated
labyrinth stages, collect all hidden artifacts, and learn a new digital skill in each stage. Players
race against time to unlock the mythical Final Certification.
All assets: visuals, animations, sound effects, music must be procedurally generated via code
only. No external image, audio, or font files.
Submission Format: A .zip archive containing an index.html file at the root. Opening the file
should immediately launch the playable game.
COMPETITORS:
 TSS category
Individual competitors from TSS school will independently compete to develop a game.
Games will be judged based on final outcomes, creativity, technical implementation, as well as
innovation.
The game file must be only in HTML, JavaScript (vanilla framework optional) and CSS, and
contain an index.html file in the top-level directory. Opening this file in a web browser should
immediately allow the game to be played without any additional steps.
CORE GAME FEATURES
 3 Randomized Labyrinth Stages, each with its own procedural map and visual theme.
 Collectibles: 3 Future Skills Artifacts per stage (e.g., AI, Cybersecurity, Machine
Learning).
 Countdown Timer: Time-limited challenge to complete each labyrinth.
 Failure Condition: If the timer hits 0 before collecting all artifacts and reaching the exit.
 Win Condition: Collect all artifacts and reach the exit within time.
 Learn & Progress: Upon collecting each artifact, display a fun fact or micro-lesson
about a future skill.
 Final Certification Screen: Celebratory finish screen after stage 3.
CONTROLS
 Arrow Keys: Move (Up, Down, Left, Right)
 Spacebar: Jump
 Hit Artifact: Collect it and unlock a new skill
 ESC: Pause / Return to Menu
TECHNICAL RULES

Feature Requirement
Entry Point Must be index.html
File Type HTML, CSS, JS only
No external images/sounds; all generated
Assets
by code
Audio Generated using javascript library
Rendering Canvas/WebGL
File Size Preferably under 31KB (ZIP format)
localStorage can be used for best times
Storage
or completion status
Procedurally rendered with canvas or
UI
WebGL only

COMPETITION SCHEDULE & MILESTONES

Day 1: Setup & Core Movement
Objectives:
 Set up HTML/JS/CSS project structure.
 Create game loop and rendering engine using canvas/WebGL.
 Implement player (in Rwanda national flag colors) movement (arrow keys + jump).
 Generate random maze (labyrinth) procedurally.
 Create and place 3 collectible artifacts in maze.
 Implement basic HUD with timer and score.
Expected Output:
 Working player movement within a maze.
 Procedural map with visible artifacts.
 Timer countdown and artifact counter UI.
Day 2: Gameplay Mechanics & Skill Reveal
Objectives:
 Enable artifact collection and display micro-lesson on new skill.
 Add jump animation and basic physics (jumping over obstacles).
 Add traps or obstacles that delay or reduce time.
 Implement stage completion logic (all artifacts collected + reach exit).
 Implement fail state (timer runs out).
 Begin working on sound for feedback and ambient music.
Expected Output:
 Full game loop for 1 stage (collect → learn → exit → next).
 Artifacts trigger animated skill popup.
 Obstacles introduce challenge.
 Sound effects working.

Day 3: Final Polish & Certification Stage

Objectives:
 Implement all 3 stages with increasing difficulty.
 Add aesthetic themes (e.g., Colorful Rwanda, Digital Sky, Future Campus).
 Add celebratory final stage (“Final Certification” unlocked).
 Implement final sound/music layers.
 Save score and stats using localStorage.
 Final code optimization and packaging.
Expected Output:
 Complete game with 3 playable stages.
 Educational facts appear with each artifact.
 Procedurally beautiful visuals of Rwanda’s digital future.
 Final “Certification Achieved” screen.
 Fully zipped project ready for judging.
CONCLUSION
The three-day game development competition is designed not only to test participants’
programming skills but also to foster creativity, problem-solving, and teamwork through
progressive and hands-on challenges. By structuring the competition into distinct daily tasks
from building foundational mechanics to integrating AI, UI, sound, and advanced features,
participants at TSS levels are encouraged to apply their knowledge in a practical, engaging, and
scalable way.
The competition aims to:
 Promote logical thinking and algorithmic reasoning.
 Encourage clean, maintainable, and efficient coding practices.
 Introduce participants to real-world software development workflows including testing,
debugging, and optimization.
 Inspire innovation and creativity through open-ended challenges.
Through the detailed judging criteria and assessment checklist, this competition ensures a fair
and comprehensive evaluation of both the technical and creative aspects of each game project. It
sets the stage for young developers to showcase their talents and gain valuable experience in
game development, software engineering, and collaborative problem-solving.
Ultimately, this initiative contributes to nurturing the next generation of tech innovators and
provides a platform to bridge academic learning with industry-relevant skills in a fun and
competitive environment.
IN SUMMARIES
Sample screenshot
 Judging Criteria & Assessment Checklist
Competitor’s name: ………………………………………………………………..
Day 1: Setup & Core Movement

Max Awarded
Criteria Assessment Checklist
Points Points
Creativity & Maze structure is procedurally generated
10
Originality and visually distinct
Effective Procedural Maze layout varies on every load with
10
Generation no fixed pattern
Player can move smoothly using arrow
Game Mechanics 10
keys and jump with spacebar
Artifacts are visible and reachable inside
Basic Interaction 10
the labyrinth
Code is structured (clear, commented,
Code Quality 5
and modular)
HTML-based Game launches directly from index.html
5
Execution in browser without error
Total 50

Assessor’s name:

Signature:
Day 2: Gameplay Mechanics & Learning Experience
Competitor’s name: ………………………………………………………………..

Max Awarded
Criteria Assessment Checklist
Points Points
Each artifact shows a short informative
Interactive Learning 10
popup on skill (e.g., ML, AI)
Obstacles and traps are randomly placed
Procedural Challenge 10
and functional
Game progresses correctly when all
Game Loop Logic 10
artifacts are collected + exit is reached
Game ends with a message when time
Fail Condition 5
runs out
Game introduces engaging elements
Creativity & Fun beyond basic logic (animations, 10
feedback)
Procedural sound or background audio
Sound Effects 5
implemented (e.g., ZZFX)
Total 50

Assessor’s name:

Signature:
Day 3: Final Polish & Certification Stage
Competitor’s name: ………………………………………………………………..

Max Awarded
Criteria Assessment Checklist
Points Points
Final Game All 3 stages are complete, distinct, and
10
Completion increasing in difficulty
Each stage artifact teaches a new skill in
Fun & Learning 10
a fun, clear way
Performance & Smooth performance with optimized
10
Optimization assets and efficient logic
End screen presented clearly after final
Final Certification 5
stage
File Size Complete project ZIP <= 31 KB 10
Game works on major browsers without
Compatibility 5
setup or external dependencies
Total 50

Assessor’s name:

Signature:
 Final Judging Criteria & Assessment Checklist
Programming Skills
Competitor’s name: ………………………………………………………………..

Max
Awarde
Criteria & Assessment Focus Point
d Points
s
1. Problem Solving & Algorithmic Thinking 20
Clear application of logical structures, algorithms (e.g., maze generation) 6
Effective handling of game states and conditions 6
Efficient data structures used where applicable 7
2. Code Quality & Readability 15
Well-organized, clean, and commented code 5
Meaningful naming conventions for variables/functions 5
Modular design with reusable functions or components 5
3. Technical Proficiency 20
Proper use of HTML, CSS, JavaScript for procedural graphics 6
Effective use of canvas/WebGL and in-browser APIs 6
Implements features (game loop, HUD, sound, etc.) without external
7
libraries
4. Testing & Debugging 10
Code demonstrates awareness of error handling 3
Game handles edge cases and unexpected inputs gracefully 3
Debugging strategies evident or described 4
5. Performance & Optimization 15
Smooth gameplay with no noticeable lag 5
File size optimized (≤ 31 KB where possible) 5
Redundant or heavy operations minimized 5
6. Creativity & Innovation 10
Unique take on theme or game design- Imaginative use of procedural
5
visuals/sound
Adds extra features beyond base requirements (e.g., mini-map,
5
achievement badges, etc.)
TOTAL 90

Assessor’s name:

Signature: