Figure out a more seamless way of managing configurations between modpack updates #6

New issue

Open

opened 2026-07-21 17:44:12 -05:00 by Cjnator38 · 0 comments

Cjnator38 commented

2026-07-21 17:44:12 -05:00

Owner

What is the issue?

In a lot of cases, updating config files would be as simple as overwriting them in the modpack (like when updating a global item/block whitelist).

In cases where we'd need to toggle specific features within a mod's config file (notably with Legacy4J with stuff like Legacy Item Pickup), we'd have to work out a way to toggle only what needs to toggled within a single update, or have some record of configuration changes available when migrating from a really old version to the latest, all without affecting some of the user-facing options.

A big concern with this would be the handling of different configration formats, but it'd be best to start with the usual JSON structure and work our way through others if need be

To Reproduce

update
we made a change
user dont see the change until configs are reset etc

Modpack

Rekindled Legacy (list TU in your bug report)

Pack Version

"26.1.2-based"

Minecraft Version

26.1.2

ModLoader

Fabric

Log and crash report

nuh uh

Additional Context

bruh idk how to do issue templates so im just doing it through the modpack template

Acknowledgement

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

### What is the issue? In a lot of cases, updating config files would be as simple as overwriting them in the modpack (like when updating a global item/block whitelist). In cases where we'd need to toggle specific features within a mod's config file (notably with Legacy4J with stuff like `Legacy Item Pickup`), we'd have to work out a way to toggle only what needs to toggled within a single update, or have some record of configuration changes available when migrating from a _really_ old version to the latest, all without affecting some of the user-facing options. A big concern with this would be the handling of different configration formats, but it'd be best to start with the usual JSON structure and work our way through others if need be ### To Reproduce 1. update 2. we made a change 3. user dont see the change until configs are reset etc ### Modpack Rekindled Legacy (list TU in your bug report) ### Pack Version "26.1.2-based" ### Minecraft Version 26.1.2 ### ModLoader Fabric ### Log and crash report nuh uh ### Additional Context bruh idk how to do issue templates so im just doing it through the modpack 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 17:44:12 -05:00

Cjnator38 modified the project from Rekindled Legacy to Re-Console/Simply Legacy

2026-07-21 17:45:43 -05:00

Cjnator38 modified the project from Re-Console/Simply Legacy to Rekindled Legacy

2026-07-21 17:45:49 -05:00

Cjnator38 referenced this issue

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

Discuss potentially reworking Rekindled's release strategy #7