rpo: add required:true to force-enable CC pack #31

Merged
Matt merged 1 commits from feature/rpo-required-true into main 2026-05-23 17:05:53 +00:00
Owner

For existing players whose options.txt already exists, default_packs doesnt apply. Adding required:true as the best-guess RPO key for force-on behavior. Pack 0.21.2 -> 0.21.3.

For existing players whose options.txt already exists, default_packs doesnt apply. Adding required:true as the best-guess RPO key for force-on behavior. Pack 0.21.2 -> 0.21.3.
Matt added 1 commit 2026-05-23 17:05:53 +00:00
Players with an existing options.txt (i.e. anyone who has launched MC
once) don't get the 'default_packs' applied -- RPO only treats those as
defaults for fresh installs.

Adding 'required: true' to the override entry on the assumption that
the field forces the pack to be enabled on every launch regardless of
player choice. Decompiled the jar for string constants and 'required'
appears alongside 'force_compatible' as a known key.

If the field name is wrong RPO will silently ignore it -- no harm, easy
iteration.
Matt merged commit 804d085e36 into main 2026-05-23 17:05:53 +00:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: minecraft/brass-and-sigil#31