> For the complete documentation index, see [llms.txt](https://cs2ctf.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cs2ctf.gitbook.io/docs/development/development-progress.md). # Development Progress **Current Features** * [x] Spawning flags for each team with an easy editor * [x] Picking up flags for each team * [x] Respawning when a player was killed * [x] If a flag was lost, return it either after X seconds as set by the ConVar or return it if a team member touched it and play the return sound plus text message * [x] Awarding MVPs for secured flags * [x] Securing flags, including playing a sound and chat messages * [x] Awarding a point per secured flag * [x] When the scorelimit is hit as per the config, the endscreen is shown (won/lost) and game freezes everybody and re-starts the map after 30 seconds **Required todo for core gameplay** * [ ] The editor does need a command to create spawns, as default spawns will usually not work for this type of game mode * [ ] Editor needs to save the base location as well as spawn locations into a .json file for every map * [ ] If CTF is enabled on map start, it needs to load the locations from the editor and spawn entities * [ ] Buyzones need to be added dynamically around the bases * [ ] Existing buyzones, hostage zones and bomb zones need to be removed from the maps at map start (They sometimes prompt messages) **What would be nice to include the vanilla gameplay feeling and extension** * [ ] Check for info\_target. There should be at least 2 entities on the map with the name ctf\_ct\_base and ctf\_t\_base marking the flag locations, then taking buyzones, spawns and such into account for CTF * [ ] Teleport the top 5 players of each team towards the end screen positions as in the vanilla gameplay --- # 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://cs2ctf.gitbook.io/docs/development/development-progress.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.