Tags
Creators
Details
Licensed MPL-2.0
Published 4 years ago
All versions
v6.0.5-1.19.4-Fabric
Release
[FABRIC] [1.19.4] PuzzlesLib-v6.0.53 years ago 133
Compatibility
Minecraft: Java Edition
1.19.4
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Required content
Changes
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
[v6.0.5-1.19.4] - 2023-05-24
Added
- Added
ItemTossCallback
Changed
- Allow retrieving an actual
BlockColor/ItemColorfromColorProviderContext - Some more internal clean-ups
Fixed
- Prevent
CustomizeChatPanelCallbackfrom interfering with more than the chat panel - Fixed faulty
BowItemmixin on Fabric
[v6.0.4-1.19.4] - 2023-05-22
Added
- Added a few new rendering related client events
- Added
ScreenElementPositionerhelper class - Added a bunch of new
Levelrelated events
Changed
- Refactored a lot of mod construction contexts
Fixed
- Fixed
NullPointerExceptionwhen firingComputeFovModifierCallbackon Fabric - Fixed
ComputeFovModifierCallbackdividing by zero when fov effects are disabled - Fixed
Screen::initevents not providing a view ofAbstractWidgets on Forge
[v6.0.3-1.19.4] - 2023-05-20
Fixed
- Fixed
ClassCastExceptionforRenderGuiElementEvents
[v6.0.2-1.19.4] - 2023-05-20
Changed
- Implemented
RenderGuiElementEventsfor item name - Moved
SpawnDataMobimplementation to Fabric, the nativeMob::getSpawnTypemethod is now used on Forge - Allow more context for
RenderGuiElementEventsto ease implementations on different mod loaders
Fixed
- Fixed
ClassCastExceptionfor after events inScreenMouseEvents
[v6.0.1-1.19.4] - 2023-05-19
Added
- Added events for when the player is being cloned and for after respawning
Changed
- Some internal clean-up for capabilities and networking
[v6.0.0-1.19.4] - 2023-05-18
- Ported to Minecraft 1.19.4
Changed
- Internal changes to capability implementation on Fabric to make capabilities other than for entities actually usable and not result in class loading errors
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:QAGBst4M:6As7amla"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QAGBst4M:6As7amla"
}


