feat(config): include Render/Fun modules in .localconfig save

[CompileRider]

Adds support for including Render and Fun modules when saving local configs through .localconfig save.

Summary

• New enum OptionalInclusion in config/ package with RENDER and FUN entries.
• Refactored IncludeConfiguration from individual boolean fields (includeRender, includeFun) to Set<OptionalInclusion> — rendering, fun, and future groups handled uniformly.
• Removed dead code includeAction: Boolean from IncludeConfiguration.
• Added render and fun tokens to the .localconfig save include options.
• Moved Render/Fun public-config exclusion into ClientModule via inclusionGroup propagation from ModuleCategory.
• Renamed ModeValueGroupSerializer.PUBLIC_SERIALIZER to PUBLIC_CONFIG_SERIALIZER to avoid confusion with ValueGroupSerializer.PUBLIC_SERIALIZER.
• Moved OptionalInclusion from config/autoconfig/ to config/ package — used across 3 subpackages.
• Consolidated checkIfInclude() into Value.kt — serializers now call it.checkIfInclude() instead of duplicating the logic.

Behavior

• .localconfig save <name> — previous behavior, excludes Render/Fun modules.
• .localconfig save <name> true render fun — includes Render and Fun modules.
• .localconfig save <name> true binds hidden render — combines all include options.
• Existing binds and hidden options keep their behavior.

Mechanism

• ModuleCategory.inclusionGroup: OptionalInclusion? — Render/Fun categories tag themselves with their group.
• ClientModule.init {} propagates category.inclusionGroup to the module.
• ValueGroup and ModeValueGroup propagate inclusionGroup to their inner values.
• Value.checkIfInclude() returns false if doNotInclude is set, otherwise checks whether the value's inclusionGroup is in IncludeConfiguration.optionalInclusions.
• The new PUBLIC_CONFIG_SERIALIZER (with includePrivate = false) respects checkIfInclude(), so Render/Fun values are excluded from public configs unless their group is in the set.

Fixes #8398

[minecrrrr]

Yooo! Absolute lifesaver, thx man

[MukjepScarlet]

To be honest there are also a lot of render configs in other categories. I think we need a better way to handle it

[CompileRider]

To be honest there are also a lot of render configs in other categories. I think we need a better way to handle it

Fair point. Since render settings are indeed everywhere, maybe we can just tag individual settings as 'visual'?

Instead of filtering entire modules, we could add a simple property to the Value class to mark it as visual. That way, the render flag can surgicaly filter out things like 'Range Circles' in Combat modules or 'Line Colors' in Movement, while keeping the functional settings intact.

It keeps the configs much cleaner and addresses the 'scattered settings' problem without needing a massive overhaul. What do you think of this approach?

[MukjepScarlet]

1.
enum class OptionalInclusion {
  RENDER,
  FUN,
}

2.
val ModuleCategories.Render = ModuleCategory("Render", inclusionGroup=RENDER)

3.
open class Value {

fun inclusionGroup(group) { ... }

Like this? This is a draft

Or simpler just remove the enum

[TssCode]

will it also save HUD configurations?

[CompileRider]

will it also save HUD configurations?

Yes, it does save HUD configurations.