Tags
Creators
Details
1.2.0
Compatibility
Changes
New HashMap on LocateHashMap for dialogPerEntityType & dialogPerCompoundTag
Created codec folders for filemanager classes
Created methods registerDatapack for dialogs, quests, npc (entity type and compound tag)
Created classes LoadDialogList & LoadTagDialogList for loading npc dialogs from datapack and resources
Changes on screens
Renamed classes on dialogoption folder
Command quest reward (Support for @p)
Multistage quests via quest reward
Changes on AbstractQuest:
-
Added completeQuest method per quest type instead of having a single class CompleteQuest
-
Added enhancedCompleteQuest method if your QuestType needs extra code, like remove items on complete quest
Datapack support:
- 4 new classes for JSON Listener with datapacks
Added packet OpenVanillaEntityScreen to change between dialog screen and entity default screen (if it has)
If npc has dialog screen and his own screen, player can open default screen directly with interact + shift
Added methods to MCUtil: - hasQuest (Checks if player has active or completed X quest)
Added methods to MCUtilClient for render text
Added reloadQuests command for reload resources folder (dev run + debug mode)
Added new events on ServerEvent:
-
loadDialogPerEntityType: Checks if there's any json in npc-entity_type_list that fetchs with interacted entity and display his dialogs
-
loadDialogPerCompoundTag: Checks if interacted entity has fetched tags with any json in npc-compound_tag_list and display his dialogs
Added new paths to QuestApiMain Added enums for Logic_Gates (Used on CompoundTagList)
Fixed quest log, data keep even if quest was deleted/completed
Fixed some minor bugs
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:nWdqkLZN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6FVcnRyT:nWdqkLZN"
}

