Tags
Creators
Details
1.3.0
Compatibility
Changes
Renamed ServerDialog into NPCConversation and NPCDialog
Fixed an bug on register dialogs and quests via your own Mod
Added TextButton - Similar to normal Button but renders normal text, not centered
Improved DialogScreen.class
Added DefaultTargetType if your goal dont need a custom one
Added MoveToTargetTyp
Added new Server events for new goals
Improved registry. Automatically registered all Enums per Enum.class
Added a render to check what entity can give player a quest.
Added methods to check if an entity can give a quest
WIP - Quest Maker In-Game
Added RenderConfig for questmarker reload
Added new packets (There are a lot, check network-message)
Added MenuHandler for QuestMaker
Added staticc instance for Gson
Added Mathematic#vec3NumberBetween
Added Mathematic#simpleMatrixToVec3 - Convert Matrix4f to Vec3
Removed MCUtil constructor
Added MCUtil#nextQuestTracked to display next QuestTracked in HUD
Added MCUtil#findSlotMatchingItemStack to check if inventory has an concrete ItemStack with NBT
Removed MCUtilClient constructor
Fixed MCUtilClient#RenderLine methods
Added MCUtilClient#formatString to create a MutableComponent from 2 texts and 2 ChatFormattings
Added MCUtilClient#RenderEntity/Item to render an Item or Entity with added constant rotation
Added MCUtilClient#createButton as a replace of new button builder
Added GsonManager#writeJson to write a file into an existing path
Added QuestCommand#openQuestMaker (WIP for QuestMaker menu)
Mixed QuestApiMain & ClientEventHandlerRegister
Added a way to create NPC that gives quests to player without coding (With JSON)
Added a new IEnum inteface for register Dialog and Quest enums
Added EnumRegistry..class for automatically register Enums - Classes inside IEnum interfaces
Changed Enum.classes implementing IEnum Interfaces
Added additionalFields
Added LootTableReward
Added CollectNBTGoal
Added translatable text to quests (Dialogs left)
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:6FVcnRyT:kfpMf19k"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6FVcnRyT:kfpMf19k"
}

