Discuss potentially reworking Rekindled's release strategy #7

New issue

Open

opened 2026-07-21 18:12:45 -05:00 by Cjnator38 · 0 comments

Cjnator38 commented

2026-07-21 18:12:45 -05:00

Owner

What is the issue?

In Rekindled current interation, we've inherited Legacy Reborn's release strategy of releasing multiple different Title Update implementations per modpack update.
With Rekindled's ultimate goal of recreating a large portion of these LCE updates (if not up to Village & Pillage), I personally think it'd be better to consider an incremental content update system, similar to how 4J/Mojang actually updated LCE, rather than splitting a single modpack update across distinct content updates.

For this to work out, we'd have to:

Ensure the "Release Build" is stable enough to upgrade content-wise
- This means we would likely have to run through a long beta/pre-release phase, in case core features need to be refined or developed on the mod-side
  - Could pose a problem if mod development becomes stagnant
Move "special" builds (pre-TU0 or even alternate timeline builds) to a separate project page to ensure they still get coverage
- We could probably keep Rekindled's current update strategy here
Work out some kind of "Milestone" system, where milestones would represent a significant content update
- Milestone 1 based on TU0-2, Milestone 2 based on TU3-4, etc.
- Would have to find a way to clearly communicate this to the end-user, likely through what versioning scheme we use
Work out config management past just using Config Manager, since we would likely have to be toggling a lot of individual features within mods between updates to get them working seamlessly
- Could benefit other modpacks and modpack creators, similarly to YOSBR and Config Manager

A huge benefit to this kind of system (in my opinion) is that it would let players experience these updates as they come out, just like with the standard game, with servers even having the ability to evolve alongside the features available to them.

To Reproduce

blah

Modpack

Rekindled Legacy (list TU in your bug report)

Pack Version

Discuss ig

Minecraft Version

26.1.2

ModLoader

Fabric

Log and crash report

idk

Additional Context

omo please add empty template

Acknowledgement

I understand and have fully filled out the form, including the issue name.

### What is the issue? In Rekindled current interation, we've inherited Legacy Reborn's release strategy of releasing multiple different Title Update implementations per modpack update. With Rekindled's ultimate goal of recreating a large portion of these LCE updates (if not up to Village & Pillage), I personally think it'd be better to consider an incremental content update system, similar to how 4J/Mojang actually updated LCE, rather than splitting a single modpack update across distinct content updates. For this to work out, we'd have to: - Ensure the "Release Build" is stable enough to upgrade content-wise - This means we would likely have to run through a _long_ beta/pre-release phase, in case core features need to be refined or developed on the mod-side - Could pose a problem if mod development becomes stagnant - Move "special" builds (pre-TU0 or even alternate timeline builds) to a separate project page to ensure they still get coverage - We could probably keep Rekindled's current update strategy here - Work out some kind of "Milestone" system, where milestones would represent a significant content update - Milestone 1 based on TU0-2, Milestone 2 based on TU3-4, etc. - Would have to find a way to clearly communicate this to the end-user, likely through what versioning scheme we use - [Work out config management past just using Config Manager](https://git.nostalgica.net/Reverie-Projects/monorepo/issues/6), since we would likely have to be toggling a lot of individual features within mods between updates to get them working seamlessly - Could benefit other modpacks and modpack creators, similarly to YOSBR and Config Manager A huge benefit to this kind of system (in my opinion) is that it would let players experience these updates as they come out, just like with the standard game, with servers even having the ability to evolve alongside the features available to them. ### To Reproduce blah ### Modpack Rekindled Legacy (list TU in your bug report) ### Pack Version Discuss ig ### Minecraft Version 26.1.2 ### ModLoader Fabric ### Log and crash report idk ### Additional Context omo please add empty template ### Acknowledgement - [x] I understand and have fully filled out the form, including the issue name.

Cjnator38 added this to the Rekindled Legacy project

2026-07-21 18:12:45 -05:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Reverie-Projects/monorepo#7

No description provided.

Rows
Columns