> For the complete documentation index, see [llms.txt](https://renice-cubed.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://renice-cubed.gitbook.io/wiki/updates-and-versions.md). # Updates and versions ### Version numbers The versioning system of our modpack looks like this: ```txt A.B.C-stage ``` * **A**.B.C - Major update, used only when Renice³ moves to a new [game drop](https://minecraft.wiki/w/Game_drop). * A.**B**.C - Minor update, used for larger changes, such as adding, removing, or replacing mods. * A.B.**C** - Patch update, used for fixes, config changes, updating mods to newer compatible releases, metadata fixes and similar maintenance updates. ### Release stages * `alpha` - early builds of the modpack. For example, when a drop has just released, but most mods are not updated or included yet. Also used when a new mod is added with raw configuration, or when a mod is removed. * `beta` - builds where issues with configuration are partially fixed, but not all mods may be updated for the required drop yet. * `rc` - release candidate, where the mod list is included and the technical side works correctly, but some settings, configs, or defaults still need final review and polish. * `release` - stable, cleanly assembled builds without major known issues or critical conflicts. ### How often are updates released? In the best case, updates are released every 2–4 weeks for the latest Minecraft version. There is no strict schedule. As players and developers, we should respect mod authors and give them time to make finished, high-quality releases. When possible, we also try to help them. After the required mods are updated and ready, their new versions are included in Renice³ through a modpack update. ### Will new features be backported to older modpack versions? Nope. There is simply not enough time and opportunity for this right now. We will wait until the modpack has a contributor base that can help with backporting, when and if that happens. Then we can give this idea a chance and bring it to life. --- # 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://renice-cubed.gitbook.io/wiki/updates-and-versions.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.