Tags
Creators
Details
Licensed MPL-2.0
Published 4 years ago
All versions
v4.1.0-1.19.1-Fabric
Release
[FABRIC] [1.19.1] PuzzlesLib-v4.1.04 years ago 158
Compatibility
Minecraft: Java Edition
1.19.1
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.
[v4.1.0-1.19.1] - 2022-07-30
- Compiled for Minecraft 1.19.1
Changed
- Cleaned up networking classes
- Made config annotations more powerful, removing the need to set category names and comments on config objects
Removed
- Remove deprecated methods and classes
[v4.0.18-1.19] - 2022-07-26
Added
- Added a utility class for creating and registering new game rules
Changed
- Switched
CommonScreensclass back to using an SPI - Renamed config related helper methods
[v4.0.17-1.19] - 2022-07-20
Changed
- Allow final category fields in annotated configs
Fixed
- Fixed crash on dedicated servers due to faulty import
[v4.0.15-1.19] - 2022-07-19
Added
- Added access for screen buttons to
Screensutility class - Added a way for registering search trees
[v4.0.14-1.19] - 2022-07-19
Changed
- Made sure mods always use the correct mod event bus when registering game content
Fixed
- Fixed bug in registry manager that would result in game content being registered for the wrong mod id
[v4.0.13-1.19] - 2022-07-19
Added
- Added a helper method for registering a material to the proper texture atlas
Changed
- Moved method for baking configs into base interface
Fixed
- Fixed a bug where
ConfigDataHolderV2would always throw aNullPointerExceptionduring config load - Fixed
ModEntityTypeBuilderbeing created from supplier too early on Forge
[v4.0.12-1.19] - 2022-07-18
Added
- Added overhauled config system to allow for as many configs as desired regardless of type
[v4.0.11-1.19] - 2022-07-17
Added
- Added the mod loader type to the current mod loader environment context
Fixed
- Fixed type arguments when registering placeholder registry references
[v4.0.10-1.19] - 2022-07-17
Changed
- Adjusted a few internal names for registering game content
[v4.0.9-1.19] - 2022-07-17
Added
- Added mod base interfaces for common and client with many new helper methods for registering content
- Added helper class for client factory methods
Changed
- Converted
FuelManagerandScreensto no longer use a Service Provider Interface
Fixed
- Fixed possible start-up crash on Forge due to methods in mixin classes not being properly obfuscated
[v4.0.8-1.19] - 2022-07-13
- Fully compatible with Forge 41.0.98+ which is also now required
Added
- Added a way for registering particle types
Changed
- Renamed
ServicestoCoreServices, old classes remain as overloads for now
Fixed
- Fixed
RegistryManagernot returning the exact type it was provided - Should no longer show as incompatible with servers that don't have Puzzles Lib
[v4.0.7-1.19] - 2022-07-11
Changed
- Small code clean-ups
[v4.0.6-1.19] - 2022-07-11
Added
- Added a few more utility methods for registering game content
Fixed
- Fixed RegistryReference::placeholder always throwing an exception when used
[v4.0.5-1.19] - 2022-07-09
Fixed
- Attempt to fix common jar not being deobfuscated when applying from Maven in dependant projects
[v4.0.4-1.19] - 2022-07-09
Fixed
- Fixed common project depending on Quilt
[v4.0.3-1.19] - 2022-07-09
Added
- Added a utility class for registering client side content
Fixed
- Fixed Modrinth upload tasks
[v4.0.2-1.19] - 2022-07-07
Changed
- Renamed internal base classes to follow mod loader specific names
[v4.0.1-1.19] - 2022-07-07
Fixed
- Fixed maven dependency for Forge version
[v4.0.0-1.19] - 2022-07-07
- Ported to Minecraft 1.19
- Split into multi-loader project
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| PuzzlesLib-v4.1.0-1.19.1-Fabric-sources.jar | Unknown | 83.78 KiB |
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:w1IA6pkN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QAGBst4M:w1IA6pkN"
}


