> For the complete documentation index, see [llms.txt](https://codyfight.gitbook.io/white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codyfight.gitbook.io/white-paper/gameplay/in-game-assets/codyfighter.md). # Codyfighter **Codyfighters have native and learnable skills that help players build their strategies in the gameplay.** For example, the native skill of the engineering class is building. This allows the construction of new map tiles - blocks to alter the flow of the game (e.g., blocking the enemy player or a hostile Special Agent). The learnable skills, on the other hand, can be unlocked as players rank up or participate in more battles. An example is overheating, an ability that allows players to attack their opponents and block them from using skills in the next round. Codyfighter’s ownership is visible in the [Launchpad](/white-paper/gameplay/player-dashboard/launchpad.md) where players can take various actions to optimize their in-game experience such as repairing and changing their Codyfighter or pairing it up with a new [Operator](/white-paper/gameplay/player-dashboard/inventory.md) to participate in new Leagues. The game's team, along with the community, will enrich the metagame even more by releasing new Special Agents, [map tiles](/white-paper/gameplay/metagame/map-tiles.md), special abilities, and so on. This will lead to constant variability in players’ decisions in the game and keep [metagame](/white-paper/gameplay/metagame.md) strategies in balance at all times. --- # 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://codyfight.gitbook.io/white-paper/gameplay/in-game-assets/codyfighter.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.