> For the complete documentation index, see [llms.txt](https://docs.kepler.homes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kepler.homes/roadmap/2022.md). # 2022 ### 2022 Q1-Q2 * Static rendering of characters and rendering of different presentation styles Development of character attribute functions * Development of game weapons, equipment, fashion and other items and accessories * Development of the game's combat system and skills * Complete the design and development of NPC and scene related functions * Complete the design and development of NPCs and in game scenarios * Development of the game's homepage interface ### 2022 Q3-Q4 * Complete the development of the quest system * Completed the beta version V1 * Completed the beta version V2 * Completed the beta version V3 * Building the Kepler Game Map M3 * Added new gameplay prototyping * Development and testing completed Aptos chain related modules: MarketPlace, Passport --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kepler.homes/roadmap/2022.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.