Please sign in to comment.
Load at startup to stay compatible with startup plugins.
Earlier versions of ProtocolLib would in fact load at startup, but due to an experimental change (ffd920e) - where ProtocolLib injected code into DedicatedServerConnectionThread in order to intercept pending connections - the load order had to be set to world. This injection was later removed, but the load order was never reinstated. This causes problems with plugins that load on startup, but also depend on ProtocolLib as load order trumpts dependency. This change reintroduces startup load order.
- Loading branch information
Showing with 2 additions and 0 deletions.