JourneyMap compat is going to break.

[mysticdrew]

Hey guys, sorry I thought this project was dead at 1.18.2.
I have removed NBTChunkMD and rewrote my whole caching system.

Currently, I am looking into if i can bring it back in via a compatibility layer. I think I can, but no promises.
Otherwise, you can adapt to the new caching system based on the version of JM.
If I can revert it, it will only be for 1.21.1(if you are supporting it) and 1.21.11, since that looks like your current target.

I will not add it past 1.21.11 though. you'll need to look into JMChunkSnapshot which uses a new binary model that contains enough data for JM to map all layers and maptypes. Much smaller than all the other region cache files combined, though individually chunks in the cache are a little larger.
I've added encode/decode methods for easy conversion to friendByteBuffer, these chunks are usually less than 20kb. over the wire.

[Protonull]

As long as there's still a way to arbitrarily render chunks, it shouldn't be a problem to switch over the integration code.

As an aside, is there a way to have JourneyMap as a runtime dependency (./gradlew runClient)? I've tried and I get issues with dependency resolution because of JM's jar-in-jar dependencies. This is a known problem with Fabric, but do you have a workaround for this? Is there a repository I can add that can resolve the internet jij dependencies?

[mysticdrew]

you should just be able to throw journeymap in the mods folder, and compileOnly or modCompileOnly in your build.gradle.

Are you in discord so we can chat about the changes and so I can give you a pre-release build?

[mysticdrew]

otherwise the api and common-network are on
maven {
url = 'https://maven.blamejared.com'
}