> For the complete documentation index, see [llms.txt](https://aincrad-legacy.gitbook.io/aincrad-legacy-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aincrad-legacy.gitbook.io/aincrad-legacy-docs/combat-system/monster-essence.md). # Monster Essence Every monster in Aincrad carries the very essence of the source code that gave it life. Sometimes those data fragments do not vanish completely when the monster falls - they condense into a material form called a **Monster Essence**, or **ME** for short. ## Assembling an Essence * Every piece of equipment has a small **port** in which a Monster Essence fits perfectly. Each item has exactly **one** port. * Once assembled, the Essence is **absorbed** - it becomes part of the item and grants its power permanently. * Assembling another Essence into the same item **overrides the previous one**: the old Essence is **destroyed in the process**, never returned, never recovered. In other words, a Monster Essence is a **consumable**. Once it goes into an item, using that port again means losing the previous Essence forever. ## Practical advice * **Use what helps you now.** Essences are consumables, not ultra-rare treasures - an Essence sitting in your inventory does nothing for you. * Found a better one later? Just assemble it over the old one. Losing the previous Essence is simply the cost of the upgrade, not a mistake. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://aincrad-legacy.gitbook.io/aincrad-legacy-docs/combat-system/monster-essence.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.