KnownPacksFix

Update - v1.2.1

New Commands

- /knownpacksfix reload — Reloads config.yml and re-applies the patch instantly, no proxy restart needed - /knownpacksfix status — Shows the current patch state, active limit, which field was patched, and whether the patch was verified - /kpf is available as a short alias for both commands - Permission node: knownpacksfix.admin (console always has access by default)

New Config Options

- patch-all-matches — Patches every matching field found instead of stopping at the first. Default: false - custom-field-names — Comma-separated list of extra field name candidates, useful for Velocity forks with different internals. Default: empty

Config Auto-Update

- config.yml now automatically updates itself when the plugin is updated - Any new options added in a newer version are appended to the bottom of your existing file with their full comments - Your existing settings are never changed or removed - A separator line marks auto-added entries so they are easy to spot - A console message is logged telling you how many new options were added

Improvements

- Patch is now verified after applying by reading the field value back and confirming it changed - If verification fails, a warning is logged so you know something may be interfering - Previously patched fields are cached so reloads skip the discovery step entirely - Velocity version is now detected and logged on startup - If KnownPacksPacket is not found, a clean error is shown with the Velocity version instead of a raw stack trace - Config validation now warns if pack-limit is at or below 64 or above 10000 - Invalid config values now print a specific warning naming the bad key instead of silently falling back

Notes

- Core patching behavior is unchanged - Fully backwards compatible with config.yml files from v1.1.0 - No configuration changes are required for the plugin to work out of the box

Update - v1.1.0

What's New

- Added config.yml automatically generated in the plugin data folder on first run - Pack limit, field logging, and debug output are now fully configurable

Configuration Options

- pack-limit — sets the maximum number of resource packs a client can declare. Default: 1024 - log-fields — logs all fields found inside KnownPacksPacket on proxy startup. Default: true - debug — logs detailed patch output including old and new values. Default: false

Improvements

- Hardcoded values replaced with named constants - Field detection strategies cleaned up and restructured - Patch limit now fully driven by config.yml instead of being hardcoded - Config loading uses no external libraries - Improved naming consistency throughout the codebase

Notes

- Core patching behavior is identical to the previous release - A config.yml will be created automatically on next proxy startup if upgrading - No configuration changes are required for the plugin to work out of the box

Initial Release

- First public release of KnownPacksFix for Velocity proxies.

Features

- Patches Velocity KnownPacksPacket limit (default: 64) - Allows higher modded client known pack counts - Improves compatibility with large modded Minecraft setups - Uses reflection-based patching with fallback detection - Automatically applies patch on proxy startup

Default Behavior

- Raises known packs limit to 1024 - Prevents "too many known packs" disconnect errors for modded clients

Notes

- Designed for modded Minecraft networks using Velocity - Should improve compatibility with large modpacks - Use with caution on public/untrusted networks