Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Old clients can't join on PaperSpigot 1.15.2 if disable-player-collisions is true #403

Closed
camdenorrb opened this issue Jun 9, 2020 · 6 comments
Labels
awaiting testing The fix to the issue has yet to be tested by the user bug This is a confirmed bug user vanished The user is not replying, the issue will be closed 30 days after their last response

Comments

@camdenorrb
Copy link
Contributor

camdenorrb commented Jun 9, 2020

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

Problem Description

Players running below server version can't join if disable-player-collisions is true

To Reproduce

Steps to reproduce the behavior:

  1. Install combat mechanics
  2. Set disable-player-collisions to true
  3. Watch as your playerbase slowly dies

Expected Behaviour

Player base not to die

Actual Behaviour

Player base dies :(

@kernitus
Copy link
Owner

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?

@LeehamElectronics
Copy link

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?

@foxfirecodes foxfirecodes added bug This is a confirmed bug investigate We have yet to investigate this issue labels Jun 30, 2020
@kernitus
Copy link
Owner

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?

@kernitus kernitus added not enough info We still need more information about the user's environment and removed investigate We have yet to investigate this issue labels Jul 12, 2020
@I-Al-Istannen
Copy link
Contributor

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.

@kernitus
Copy link
Owner

kernitus commented Oct 3, 2020

@camdenorrb @LeehamElectronics could you please try the test version with the new patch? We think it might fix this issue.

@kernitus kernitus added awaiting testing The fix to the issue has yet to be tested by the user and removed not enough info We still need more information about the user's environment labels Oct 3, 2020
@kernitus kernitus added the user vanished The user is not replying, the issue will be closed 30 days after their last response label Oct 24, 2020
@LeehamElectronics
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting testing The fix to the issue has yet to be tested by the user bug This is a confirmed bug user vanished The user is not replying, the issue will be closed 30 days after their last response
Projects
None yet
Development

No branches or pull requests

5 participants