> For the complete documentation index, see [llms.txt](https://wiki.navenro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.navenro.com/gameplay-systems/custom-combat-mechanics.md). # Custom Combat Mechanics NavenRO introduces selected combat changes to create a different PvE progression experience while preserving Ragnarok Online's familiar combat system. ## Progression Matters Character level plays a larger role when fighting monsters above your level. The further ahead the monster is, the greater the advantage it can gain through the **Level-Difference System**. This encourages players to progress through suitable leveling areas instead of immediately skipping far ahead to much stronger monsters. ## What Stays Familiar The custom systems are intended to work around normal Ragnarok Online mechanics rather than replace them. Players will still build characters around familiar elements such as: * stats * skills * equipment * cards * elements * race and size modifiers * party composition * consumables Custom mechanics add another progression layer on top of those familiar systems. See **Level-Difference System** for the exact player-facing level brackets. --- # 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://wiki.navenro.com/gameplay-systems/custom-combat-mechanics.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.