Tags
Creators
Details
0.1.0-1.21.1-neoforge
Compatibility
Changes
Changelog
Added
-
Message Registration:
-
Registered
Messagesclass for managing server and client communication usingPayloadRegistrarandPacketDistributor. -
Methods:
sendToServer: Sends packets from client to server.sendToPlayer: Sends packets from server to specific players.
-
Built on NeoForge's
RegisterPayloadHandlersEvent.
-
-
Client Setup Enhancements:
- Added
onClientSetupmethod to handle client-side setup tasks usingFMLClientSetupEvent. - Registered cutout render layers for all torch block variants (
Normal,Medium,Small,Mini, and their compressed forms).
- Added
-
Modular Content Registration:
-
EntityReg:- Registers block entities for all torch types and their wall-mounted variants, including compressed versions.
-
BlockReg:- Efficient management of torch blocks and their wall-mounted variants via
DeferredRegister.
- Efficient management of torch blocks and their wall-mounted variants via
-
ItemReg:- Handles item registration for all torch types and sizes.
-
-
- Torch Configurations:
- Introduced
NormalTorchScreenfor managing base torch entity settings when activated in the configuration. - Features:
-
Adjustable X & Z range slider directly within the screen.
- Y range adjustments remain disabled unless explicitly enabled in the configuration.
-
Torch speed is determined by the configuration and cannot be changed via the screen.
-
Sliders and settings are only accessible if the feature is activated in the configuration.
-
Utilizes a grid-based layout for scalable and modular UI design.
-
- Introduced
- Torch Configurations:
-
Rework: Modular Utility Classes:
CallConstants: Utility class for consistentResourceLocationcreation usingMODID.ConfigSlider: A custom slider widget with adjustable ranges and dynamic text for configuration control.
Improved
-
Code Maintainability:
- Modularized and consolidated content registration into separate
Regclasses (e.g.,BlockReg,EntityReg,ItemReg) for improved readability and scalability. - Refactored
Messagesfor modular communication and simplified packet handling.
- Modularized and consolidated content registration into separate
-
Customizability:
- Enhanced configuration system via
NormalTorchScreenandConfigSlider. - Support for fine-tuning entity settings, ranges, and speeds directly within the UI.
- Enhanced configuration system via
-
Scalability:
- Simplified the addition of new variants for torches (sizes, types) with the modularized registration and configuration system.
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:feN02VQ8:WCqucbku"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:feN02VQ8:WCqucbku"
}

