Skip to content

Could not check whether Bedrock player's name conflicts a premium Java player's name #982

@paj1s

Description

@paj1s

What happened?

After update to 1.19.3 i can't join because of this. (well not necessary by the update, i havent tried in a while)

What did you expect?

To join as usual.

Steps to reproduce

I have auto-register and auto-login to no-conflict, allowFloodgateNameConflict was to false but i also tried linked. The floodgate is set to have no prefix and my username has no special characters. It worked with this config so maybe something changed in mojangs api or maybe the account itself? I have the newest everything.

Plugin list

No response

Configuration file

No response

Server log

No response

Plugin version

Newest

Platform

BungeeCord

Relevance

  • I tried the latest build (build refers to development builds not necessary a release version)
  • I checked for existing tickets -
    If there are, please vote them with a thumps reaction and not create new ones

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions