Tags
Creators
Details
All versions
1.2.0
Release
NexusLib 1.2.0last month 9,608
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Nexuslib version 1.2.0
Fixes
- Fixed an issue where planks blocks weren't being added to the axe_mineable tag
- Fixed particles using the PARTICLE_SHEET_CLOUD particle render type rendering as black when any particle with the CUSTOM render type is being rendered as well (picking up items, Elder Guardian jumpscare, etc.) on neoforge
- Fixed NullPointerExceptions related to NexusLib services that could occur intermittently
Changes
- Added argument
ofThisModtogenerateBlockFamilyModelsinNLModelProvider,generateBlockFamilyBlockTagsinNLBlockTagProvider, andgenerateBlockFamilyItemTagsinNLItemTagProvider- When true, only files of the matching mod id will be generated (default behavior in previous versions)
- Added argument
woodSuffixto the methodlogsinBlockFamilyCreator- When false, the "_wood" suffix on wood log blocks will not be added (for when a wood type already has the word wood in it, for example Redwood)
- Added map
LOG_TO_WOODwhich the methodlogsadds to
- Added toggleable model generation for logs
- Changed private fields in
BlockFamilyCreatorto be protected - Tags for a block family block to be added to in
addExistingBlockis now a function which passes in the block family to allow non static block lists to be accessed - Reworked
addItemsToItemGroupinREGISTRYservice- Item origin and the stack to add are now handled through a
ItemGroupAdditionrecord - Position relative to the origin item can now be specified through the
ItemGroupAdditionTypevalue:ADD_AFTERadds the item stack after the specified originADD_BEFOREadds the item stack before the specified originADD_LASTignores the origin and force adds the item to the end of the item group
- Item origin and the stack to add are now handled through a
New Features
- Added a contributor cape switcher settings option (thanks to Yirmiri)
- Those who have contributor capes can now enable/disable/switch between available capes in a new menu item in "Skin Customization"
- Added contributor capes "Subterrous" and "Subterrous Super"
- Added NLFluidInteractionRegistry
- For defining interactions of a fluid when spreading, such as when cobblestone is made when water and lava meet
- Supplies the fluid type, level, and block position, should return true (interaction was a success), or false
- Added NLDripstoneConversionRegistry
- For adding custom dripstone block conversion interactions
- Takes in the input block, the fluid type (what kind of particles the pointed dripstone should drip) and the resulting block state
- Added the Palette Template Matrix (
"nexuslib:palette_template_matrix") sprite source, a dynamic and compatibility-friendly version of paletted permutations- Similarly to
paletted_permutations, this applies a set of given color palettes to a set of given template textures - Can be defined as such:
"id"- the identifier for the specific use case"palette_key"the template color palette sprite directory"palette_definition_directory"the directory to search for palette definition files"template_definition_directory"the directory to search for template definition files
- Instead of defining permutations in the sprite source definition, separate json files within specified directories are used
- For palettes:
"definition"- a resource location used to id the palette or link it back to some definition"palette_location"- the location of the palette resource
- For template textures:
"template_location"- the location of the template resource
- Additional json elements in these providers can be read through PTMEvents for specific functionality of features that use this sprite provider
- For palettes:
- Textures are saved to the location
assets/[template modid]/[template path]/[template texture name]_[palette modid]_[palette path] - Event listeners for additional functionality/reading additional json elements in definition files can be done through PTMEvents
registerPaletteDiscoveryCondition- function that adds a condition to whether or not a certain palette should be discovered, provides the sprite source id, palette provider path, palette resource location, and the JsonObjectregisterTemplateDiscoveryCondition- function that adds a condition to whether or not a certain template should be discovered, provides the sprite source id, template provider path, template resource location, and the JsonObjectregisterOnPaletteDiscoveryEvent- runs when discovering palette definition files, provides the sprite source id, palette resource location, and the JsonObjectregisterOnTemplateDiscoveryEvent- runs when discovering template definition files, provides the sprite source id, template resource location, and the JsonObject
- Similarly to
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:bgDhVmqz:KZh9Z9Sd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bgDhVmqz:KZh9Z9Sd"
}

