Implementation Plan for Tournaments in Mankala Engine
We are almost at the end of our community bonding period. Itās been nearly 1 month since GSOC 2026 results, and the time to formulate a proper plan for the future plan of action regarding our projectš”
Here is the breakdown of a rough plan of what I want to achieve during these 12 weeks.
(Project Setup and Implementation Plan) š»
Week 1:
- Set up the project environment and go through the implementation of https://kibao.org/
- Discuss and plan the changes to be started first based on priority.
- Examine āmain.cppā and other game files to understand how the working and how ātournaments.cppā can be implemented.
Week 2:
- Fix the user registration page with options for username and icons.
- Design pre-defined selectable icons in āKritaā.
- Write a blog post about āhow to add tournamentsā.
Week 3:
- Start with ātournaments.cppā and check if the strings like āusernamesā and āiconsā can be retrieved from the user pages.
Week 4:
- In ātournaments.cppā, make the logic for detecting players online or joining tournaments with āroom codesā.
- Create a Blog post on current progress.
Week 5:
- Create a page for users to host and enter tournaments. In the hosted ātournamentā, allow superusers/organizers to edit rules like number of days, variant type, and number of players.
Week 6:
- Filling empty spots with computerized opponents using the same logic as the āPlay with AIā option.
- Examine and fix matchmaking between the players in tournaments, if the elimination and hierarchy work after elimination.
Week 7:
- Design the UI for ātournaments.qmlā, integrating the logic of the.cpp file.
Week 8:
- Make the leaderboard where the winner rankings show up.
- Create a Blog post describing the implementation.
Week 9 and 10:
- Examine the working and the build after completing the tournaments.cpp and tournaments.qml.
- Test and play with others in demo tournaments to get feedback on the working process.
- Add Voice chat for users playing the game. (if possible)
Week 11 and 12:
- Document the changes made, review the overall codebase, and finalize it for the submission.
- Create a Final Blog post summarizing all work.
Thanks for reading. Happy codingš