Skip to content

Compatibility with Ambassador Plugin for forge backend server #63

Description

@AitShiroKu

My server information

Velocity version 3.4.0 SNAPSHOT Build 528
Fallback server version 3.2.0 Release
Ambassador version 1.4.5

Backend server

Lobby paper 1.21.8 build 35
Roleplay Mohist version 1.20.1-6e92c504 and (Pure) Forge version 1.20.1-47.4.4

I Found some issue after update Fallback server from 3.2.0 beta 3 to 3.2.0 Release on my server network with Ambassador plugin.
I think hybrid server software has no effect with this issue Because the problem is likely to be plugin compatibility on Velocity.
The issue is when the player joining server with forge client to backend forge server (by click on NPC on lobby server or use /server command), Ambassador will kick player and req a player to rejoin, but when the player rejoins, the player is still on lobby. but with Fallback server version 3.2.0 beta 3 is work normally with Ambassador

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions