Skip to content

Rename config types - #3384

Draft
TelepathicGrunt wants to merge 7 commits into
neoforged:26.2.xfrom
TelepathicGrunt:ConfigRenames
Draft

Rename config types#3384
TelepathicGrunt wants to merge 7 commits into
neoforged:26.2.xfrom
TelepathicGrunt:ConfigRenames

Conversation

@TelepathicGrunt

@TelepathicGrunt TelepathicGrunt commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Continuation of neoforged/FancyModLoader#436

SERVER -> SYNCED
COMMON -> LOCAL

The idea here is making it clear that the was SERVER configs are synced between client and server (with the comment on it > explaining the sync direction). And changing COMMON to LOCAL makes it clears COMMON is not a synced config. Rather just a regular default standard config with no sync involved.

Changes were limited to renames to keep PR as small as possible. Any alternative names will need a very strong reason to convince me to change it.

If you wish for a different setup such as sync-ness as part of the config setup or removal of an entire config type, please make a separate PR and post it in comment here so implementations can be judged. Also helps to reduce bikeshedding by pushing forth a "less-talking, more-doing" stance to this.

Ideally we would target 26.3 for this. Once merged, NeoForge will get a PR to use new FML and make the same config name changes (including to the config files and folders to match new name).

This is a large scale breaking change and will need a dev announcement when NeoForge updates.

Closes: neoforged/FancyModLoader#276

NOTE: Do not release with the experimental FML lines. Revert that commit and update to newly released FML once the relevant PR is merged and 26.3 is out. Be sure to retarget this branch to 26.3 and undraft

@TelepathicGrunt TelepathicGrunt added breaking change Breaks binary compatibility 26.3 Targeted at Minecraft 26.3 labels Aug 4, 2026
@neoforged-automation neoforged-automation Bot added enhancement New (or improvement to existing) feature or request 26.2 Targeted at Minecraft 26.2 and removed 26.3 Targeted at Minecraft 26.3 labels Aug 4, 2026
@neoforged-pr-publishing

Copy link
Copy Markdown
  • Publish PR to GitHub Packages

@TelepathicGrunt
TelepathicGrunt marked this pull request as draft August 4, 2026 23:43
@neoforged-compatibility-checks

Copy link
Copy Markdown

@TelepathicGrunt, this PR introduces breaking changes.
Fortunately, this project is currently accepting breaking changes, but if they are not intentional, please revert them.
Last checked commit: fe3e52bdf50dab8d40c9a32556740cb4bd0a3757.

neoforge (:neoforge)

  • net/neoforged/neoforge/common/config/NeoForgeServerConfig
    • ❗ API class no longer exists
  • net/neoforged/neoforge/common/config/NeoForgeCommonConfig
    • ❗ API class no longer exists

@sciwhiz12 sciwhiz12 added 26.3 Targeted at Minecraft 26.3 and removed 26.2 Targeted at Minecraft 26.2 labels Aug 7, 2026
@neoforged-automation

Copy link
Copy Markdown
Contributor

@TelepathicGrunt, this pull request has conflicts, please resolve them for this PR to move forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

26.3 Targeted at Minecraft 26.3 breaking change Breaks binary compatibility enhancement New (or improvement to existing) feature or request needs rebase

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Proposal to be more explicit in naming of ModConfig.Type

2 participants