Old clients can't join on PaperSpigot 1.15.2 if disable-player-collisions is true
camdenorrb opened this issue · 6 comments
We wanted to disable collisions so we set disable-player-collisions to true, it ended up making majority of players unable to join. Mainly ones under 1.15.2
Information
- Server Version: Paper 1.15.2 Build # 343
- OldCombatMechanics version: 1.8.0
- Server Log File: https://pastebin.com/9y7i6Ec0
- OldCombatMechanics config file: https://pastebin.com/9y7i6Ec0
Problem Description
Players running below server version can't join if disable-player-collisions is true
To Reproduce
Steps to reproduce the behavior:
- Install combat mechanics
- Set disable-player-collisions to true
- Watch as your playerbase slowly dies
Expected Behaviour
Player base not to die
Actual Behaviour
Player base dies :(
Coming back to my first issue on GitHub, well this is embarrassing. iirc this issue had nothing to do with OCM, it was simply a configuration option in the TAB plugin by NEZNAMY. Sorry for wasting your time.
I don't see anything in the server log that points to this being and OCM issue, which makes me think it could be a conflict between plugins. Have you tried disabling some of the other plugins while disable-player-collisions
is on?
I’m having this issue too and I have verified that it is OCM causing it. Players are kicked when joining a mini game with a score board error, it does not happen when disable player collisions is set to false in the OCM config, also disabling player collisions with OCM or the paper mc config don’t seem to work at all, any ideas?
Any ETA on when this will be fixed? My players are getting really annoyed at players pushing each other off bridges while spectating.
Thanks
Please don't ask for ETAs on a free and open source project, if the issue is so urgent you can submit a fix yourself.
Other than that, in order to fix a bug we must first know what is causing it. The server log @camdenorrb provided doesn't seem to show any useful error, so if you could provide yours when the issue occurs we might get somewhere.
Also, it seems this may be a conflict with another plugin, are you using any other plugin that modifies the scoreboard in any way?
I can not reproduce this error. Knowing the exact scoreboard configuration would help, i.e. what plugin sets the scoreboard and what it is set to.
@camdenorrb @LeehamElectronics could you please try the test version with the new patch? We think it might fix this issue.