> For the complete documentation index, see [llms.txt](https://mhnt.gitbook.io/metahunt-wp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mhnt.gitbook.io/metahunt-wp/skins/dynamic-skins.md). # Dynamic Skins A cool feature that will add a unique layer of strategy and depth to our game: weapon skin quality. Just like in the real world, weapons in our game can show signs of wear and tear. The more a player uses a skin in battle, and the more times they fall in combat, the more the quality of their weapon skin will diminish. This wear and tear won't just be cosmetic - it will also affect the rarity and value of the "Condition" trait of the weapon skin (**Deadstock (DS), Very Near Deadstock (VNDS), Excellent (EX), Good (GD), Beat (B)** ) . To restore a weapon skin to its former glory, players can visit the Armory/Blacksmith and use MHNT tokens to repair their skins. This introduces a new utility for MHNT tokens and adds a strategic element to the game. Just like the real-world market for collectibles, where savvy collectors buy, restore, and resell valuable items, players can employ similar strategies with their weapon skins. For example, a player might find a rare but worn weapon skin being sold for a low price. They could buy it, spend MHNT to restore it, and then resell it at a higher price for a profit. Whether you're a collector who likes to keep their prized skins in pristine condition, or a warrior who wears their battle scars with pride, this new feature offers exciting new opportunities for all our players. --- # 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://mhnt.gitbook.io/metahunt-wp/skins/dynamic-skins.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.