Latest Bluemap version is incompatible with latest full release of MTR (v3.0.1)
sleepysapph opened this issue ยท 4 comments
Expected Behaviour
Bluemap 3.2.0 behaves nicely with MTR, and integrates its stations onto the Bluemap.
Actual Behaviour
Because MTR 3.0.1 is using an older version of the Bluemap API, there is a crash due to
java.lang.NoSuchMethodError: 'de.bluecolored.bluemap.api.marker.MarkerAPI de.bluecolored.bluemap.api.BlueMapAPI.getMarkerAPI()'..
and Minecraft suspects MTR as the compatibility issue
Suspected Mods: Minecraft Transit Railway (mtr)
Reproduction Steps
Steps to reproduce the behaviour:
- Install MTR v3.0.1 on server
- Install Bluemap v3.2.0 on server
- Watch server crash
Crash Report
(https://gnomebot.dev/paste/1011441975456706660)
Environment
I have also tested this with only MTR, Joban Client, and LU and Bluemap on an empty server and I get the same results.
Additional Information
According to the owner of Bluemap,
"well Minecraft Transit Railway depend on the old API version .. and the new bluemap version uses a newer one ^^'"
https://github.com/BlueMap-Minecraft/BlueMapAPI Bluemap has their API public on their Github. I've already mentioned this on the MTR discord however I feel it would be more conducive to have it as an actual issue report on this Github :D
Since I posted this issue, Bluemaps has officially released their version 3.3. Just wanted to make sure the upcoming MTR v3.1.0 was compatible with Bluemaps v3.3.0
Latest release of Bluemap on their Github
Fixed in ac23c35