Feature
Add an option to automatically prepend a configurable prefix to cracked player usernames before they join the backend servers.
For example:
- Premium player:
Steve
- Cracked player:
+Steve
- Bedrock player (Floodgate):
.Steve (already handled by Floodgate)
The prefix could be configurable, for example:
offline-prefix:
enabled: true
prefix: "+"
How it would work
Players would still join using the username they chose. During the authentication process, VeloAuth would inject the configured prefix into the username that is forwarded to the backend servers. Everything else (registration, login, UUID handling, etc.) would continue to work as normal.
Benefits
- Cracked players can use virtually any username without conflicting with premium Minecraft usernames.
- Premium usernames remain fully protected.
- It's immediately obvious whether a player is premium, cracked, or Bedrock simply by looking at their name.
- Makes moderation and support easier since staff can instantly identify the account type.
- Avoids confusion on mixed-mode networks where players with similar names may otherwise appear identical.
Why I think this fits VeloAuth
Since VeloAuth already determines whether a player is premium or offline during login, it seems like a natural place to optionally rewrite the username before forwarding the connection.
Of course, this should be entirely optional and disabled by default, so it wouldn't affect existing setups.
I'd definitely use this feature on my network, and I think other mixed-mode server owners would find it useful as well.
Feature
Add an option to automatically prepend a configurable prefix to cracked player usernames before they join the backend servers.
For example:
Steve+Steve.Steve(already handled by Floodgate)The prefix could be configurable, for example:
How it would work
Players would still join using the username they chose. During the authentication process, VeloAuth would inject the configured prefix into the username that is forwarded to the backend servers. Everything else (registration, login, UUID handling, etc.) would continue to work as normal.
Benefits
Why I think this fits VeloAuth
Since VeloAuth already determines whether a player is premium or offline during login, it seems like a natural place to optionally rewrite the username before forwarding the connection.
Of course, this should be entirely optional and disabled by default, so it wouldn't affect existing setups.
I'd definitely use this feature on my network, and I think other mixed-mode server owners would find it useful as well.