VotingPlugin identifies a Bedrock player by the prefix used by Geyser/Floodgate.
The default is a period, so a Bedrock player whose base name is Example votes
as .Example.
These instructions describe the latest public release, VotingPlugin 7.1.1.
Set BedrockPlayerPrefix to the prefix actually used for Bedrock player names.
On a standalone server, configure it in Config.yml. On a proxy network, use
the same value in the proxy bungeeconfig.yml and every backend Config.yml:
BedrockPlayerPrefix: '.'
Restart the affected proxy and servers after changing the value. Players must
enter the complete in-game name, including the prefix, on every voting site.
If a voting site rejects or removes the prefix character, it cannot reliably
address that Bedrock identity.
Treat the prefixed and unprefixed names as different accounts. For example,
.Example (Bedrock) and Example (Java) may both exist. Do not remove the
prefix to work around a voting-site form, because the vote could be credited to
the Java identity instead.
Choose the prefix before players begin voting and keep it consistent. Changing
it later can leave existing vote data under the old player name; back up the
VotingPlugin data and plan an identity/data migration before doing so.
Development only — not in release 7.1.1: the unreleased
7.1.2-SNAPSHOTline adds strict validation for usernames received from
Votifier while allowing the configured Bedrock prefix (VotingPlugin commits
935ea656,
8aaf1eb9,
and0a344625).
It also preserves an exact known Java identity before trying a prefixed
Bedrock fallback, preventing a shared base name from redirecting that vote
(AdvancedCore commit
4e81f7d4and
VotingPlugin commit
2ac38e81).
Release users do not have these hardening changes yet.
BedrockPlayerPrefix is identical on the proxy and all backends.