TerminatorNL / Tiquality

Make server lag the problem of the source player.
https://www.curseforge.com/minecraft/mc-mods/tiquality
GNU General Public License v3.0
23 stars 12 forks source link

[Bug] Crash on startup with the latest griefdefender and tiquality #58

Open mjra007 opened 3 years ago

mjra007 commented 3 years ago

Describe the bug Crash when I start the server with the latest spongeforge and griefdefender. It can't find the following class net/kyori/event/EventSubscriber. To Reproduce Start a spongeforge server with the latest tiquality and griefdefender.

Which Forge version are you using? 1.12.2 - 14.23.5.2855 Which SpongeForge version are you using? 1.12.2-2838-7.3.1-RC4082 Please provide the early startup messages starting with [Tiquality-Boot] Even tho the version of spongeforge does not match I have no problems when griefdefender is not included

[16:36:19] [main/INFO] [Tiquality-Boot]: I am located here: file:/home/minecraft/multicraft/servers/server16/./mods/Tiquality-THIN-1.12.2-GAMMA-1.8.1-124.jar!/com/github/terminatornl/tiquality/Tiquality.class
[16:36:19] [main/INFO] [Tiquality-Boot]: I am designed for Forge version: 1.12.2-14.23.5.2847
[16:36:19] [main/INFO] [Tiquality-Boot]: Loading server classes
[16:36:19] [main/INFO] [Tiquality-Boot]: SpongeForge is present!
[16:36:19] [main/INFO] [Tiquality-Boot]: I am designed for SpongeForge version: 1.12.2-2838-7.1.11-RC4007
[16:36:19] [main/WARN] [Tiquality-Boot]: SpongeForge version is different than expected!
[16:36:19] [main/WARN] [Tiquality-Boot]: This could result in undefined behavior.
[16:36:19] [main/WARN] [Tiquality-Boot]: 
[16:36:19] [main/WARN] [Tiquality-Boot]: Expected: '1.12.2-2838-7.1.11-RC4007', but you have: '1.12.2-2838-7.3.1-RC4082' installed.
[16:36:19] [main/INFO] [Tiquality-Boot]: We're running in a production environment.

If you used the word 'error' somewhere, always provide the stack trace along with both debug.log and latest.log

latest.log https://paste.ubuntu.com/p/kb2Bn2vQSt/ debug.log https://paste.ubuntu.com/p/5TR98QGQff/

mjra007 commented 3 years ago

Okay, going back to griefdefender 1.5.10 seems to fix this. This seems to only be a problem in 1.5.11-DEV.