0.0.1-26.1.2
Compatibility
Changes
Added:
Calibrated Compass
-New recipe! Have you ever use your amethyst shards and your copper chains? YES? so you can use them to craft the Calibrated Compass following this recipe on your crafting table:
copper chain | compass | copper chain
compass | amethyst shard | compass
copper chain | compass | copper chain
-You´ll get a brand new compass with 4 memory slots (cycle between them by shift + righ clic!), It is calibrated, if a slot is not linked to a lodestone it will point to true north!
-Name every slot! You won't get lost if you can see where are you going in your compass, will you? You can name your compass slots in a simple, but nice GUI made with all of my hearth.
*Ehhm, this is hard to say, you must have to pay an xp level every time you want to relabel your compasses slots.
** Default names are "Calibrated Compass: Lodestone N". (N=slot number)
*** If no lodestone is assigned, it shows simply "Calibrated Compass".
New craftings🙹
- Well you already read the Calibrated Compass recipe BUT did you expect it to be upgradable?
I was feeling like using the smithing table, so you can use yours:
paper+calbirated compass+copper ingot = A brand new slot!
*Currently this is limited up to 6 slots max. (The original 4 + 2 upgrades)
New Command
problems with the gui? (I hope not)
Name your compass with /namecompass (...yes, this will also take an xp level from you; or it should)
You might want to read this too
-
Calibrated Compass dimensions restiction: If one slot is linked to a lodestone in dimension Q, all other slots must also belong to the same dimension.
-
Of course, the Calibrated Compass texture is functional, each slot shall point correctly to its lodestone (if it is empty, norh)
- The mod is coded by using AI Google assistant.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:UwvRj4ZN:q96YH6xD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UwvRj4ZN:q96YH6xD"
}

