You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an unfortunate bug with Bungeecord where medium-large scale operations with Axiom result in a kick. The root of the problem appears to be this Bungeecord issue - though swapping Proxy2 to a Velocity server is not a trivial task, and would break many of our core plugins.
Considering Axiom on Creative is a small perk to the community, and not something longer-term, this may have to be a "Won't Fix" :(
The text was updated successfully, but these errors were encountered:
I missed this at first, but the dev for Axiom has implemented a max-block-buffer-packet-size setting in the config.yml to circumvent this issue. Changing the value from 0x100000 to 31000 appears to have fixed the problem.
In chatting to the dev, I have been advised that this can have a performance degradation for the server and network, but given the limited throughput the Creative server gets, this should be fine, yet one to keep an eye on.
Moving to review for a while, we'll see where this is at come the staff meeting.
We have an unfortunate bug with Bungeecord where medium-large scale operations with Axiom result in a kick. The root of the problem appears to be this Bungeecord issue - though swapping Proxy2 to a Velocity server is not a trivial task, and would break many of our core plugins.
Considering Axiom on Creative is a small perk to the community, and not something longer-term, this may have to be a "Won't Fix" :(
The text was updated successfully, but these errors were encountered: