Skip to content

Revert Ad Astra from the server so existing packs work again - #19

Closed
OpenSource-For-Freedom wants to merge 1 commit into
mainfrom
fix/revert-ad-astra
Closed

Revert Ad Astra from the server so existing packs work again#19
OpenSource-For-Freedom wants to merge 1 commit into
mainfrom
fix/revert-ad-astra

Conversation

@OpenSource-For-Freedom

Copy link
Copy Markdown
Owner

Merge this and everyone can play on the pack they already have. No installs, no re-imports.

Why

Ad Astra is client_side: required, so adding it locked out every player who had not re-imported. That is all of them, on top of two days of connection trouble. Not a trade worth making for an optional feature.

Removes the four jars from the server list only. 31 mods to 27.

The pack keeps them, deliberately

data/EduCraftClient.mrpack stays at 1.1.0 with all four mods. Re-importing it is still harmless, it just carries four mods the server does not load. So Ad Astra can be switched back on later by re-adding four URLs, with no second pack update and no second round of asking families to act.

What actually went wrong

The pack was verified correct at the exact URL the website gives families:

versionId: 1.1.0   mods: 26   x-cache: MISS
ad_astra / resourcefullib / resourcefulconfig / botarium  ALL PRESENT

The defect is distribution, not the artifact. The Modrinth App creates a NEW instance when you import a .mrpack rather than updating the existing one. A player who correctly re-downloads ends up with two instances and launches the old one. That will catch every family the same way.

Before re-enabling

Publish the pack as a real Modrinth project so launchers offer an in-place Update button, then roll it out when the family is together rather than mid-evening.

Verified

parity test  PASS (27 server mods, 26 client pack)
compose      renders
safety       online-mode, whitelist, PvP off, flight, gamemode, spawn-protection unchanged

When Dungeons Arise and Terralith are untouched. Both are server-side only, so they need nothing from players and keep working.

Adding a client_side=required mod locked out every player who had not
re-imported the modpack, which is all of them. The server has been
unreachable in practice for the family since it deployed, on top of two
days of connection trouble. That is not a trade worth making for an
optional feature.

Removing the four jars from the server list restores compatibility with
pack 1.0.0 immediately. Nobody has to install anything, and nobody has to
understand the difference between updating an instance and importing a
new one.

The mods stay in data/EduCraftClient.mrpack deliberately. The pack is
already published at 1.1.0 and re-importing it remains harmless: it
simply carries four mods the server does not currently load. That means
Ad Astra can be switched back on later by re-adding these four URLs, with
no second pack update and no second round of asking families to act.

What went wrong is worth recording. The Modrinth App creates a NEW
instance when a .mrpack is imported rather than updating the existing
one, so a player who correctly re-downloaded the pack ends up with two
instances and launches the old one. The pack itself was verified correct
at the URL the website serves: versionId 1.1.0, 26 mods, all four space
mods present, x-cache MISS. The distribution mechanism is the defect, not
the artifact.

Before re-enabling: publish the pack as a real Modrinth project so
launchers offer an in-place Update, and roll it out when the family is
together rather than mid-evening.
@OpenSource-For-Freedom

Copy link
Copy Markdown
Owner Author

Not reverting. Ad Astra stays on the server; fixing the client side instead.

@OpenSource-For-Freedom
OpenSource-For-Freedom deleted the fix/revert-ad-astra branch August 14, 2026 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant