FabricProxy-Lite

Same as FabricProxy but only supports Velocity and uses Fabric-API to handle Velocity packets.

This one will have better compatibility with other mods.

Setup

1. Put the mod into the mods folder
2. Start the server to generate the config
3. Configure Velocity player-info-forwarding-mode to modern and setting forwarding-secret
4. Configure secret in config/FabricProxy-Lite.toml to match Velocity config

Config

Here are all the parameters that you can set in the FabricProxy-Lite.toml config file or environment variables. Note that all properties require a value, but if the property isn't specified in the config file it'll just get populated by the default value. So the parameters that are marked as required needs a manually added value i.e. the Velocity forwarding secret.

Name	Environment Variable	Description	Default	Required
hackOnlineMode	FABRIC_PROXY_HACK_ONLINE_MODE	Allows connection through a proxy without disabling online-mode.	true
hackEarlySend	FABRIC_PROXY_HACK_EARLY_SEND	Fabric-API can't send packet before QUERY_START event, so player info(UUID) will not ready at QUERY_START event. Setting hackEarlySend to true will use mixin for early send packet to velocity. This is required for some mods, such as LuckPerms.	false
hackMessageChain	FABRIC_PROXY_HACK_MESSAGE_CHAIN	This option fixes players being kicked for Received chat packet with missing or invalid signature. or Chat message validation failure, which only happens when the player switches to another server. See #30 and #121 for more info.	false
disconnectMessage	FABRIC_PROXY_DISCONNECT_MESSAGE	The custom disconnect/kick message for users that aren't connecting through Velocity.	"This server requires you to connect with Velocity."
secret	FABRIC_PROXY_SECRET	The Velocity forwarding secret. This should be the same random string as in Velocity's forwarding.secret file. Alternatively you could set the FABRIC_PROXY_SECRET_FILE environment variable to read the secret from a file instead of config.		✓

Report Issue

If you have found something wrong, like mod compatibility or login problem, follow the steps below to let us know:

1. Search for the issue, and find if there's already one. You can also add some additional info you got.
2. If there's no such issue matches yours, create an issue ​by clicking the "New issue" button.
3. Summary the problem and write it into the title, then describe the issue as detailed as you can, and make sure to provide any of the logs so we can know what's really happened.
4. Check again the whole thing you have written, use the preview feature to check the composing.
5. Select one or multiple labels if you know what it means. The label isn't required to complete the issue and can leave it empty.
6. Submit the issue and make sure you can get the notification from it.

We thank all the contributions you made, thank you!

也歡迎用中文回報問題喔 ;)