1.1.0
Compatibility
Changes
Version 1.1.0 Changelog
This update introduces a robust inventory scanning system, closing the major loophole of carrying forbidden items inside backpacks.
š”ļø New Features Deep Backpack Scanning: The system now inspects the contents of container items. It can detect forbidden items hidden inside Useful Backpacks or other similar mods.
Server Configuration: Added a TOML config file. You can now easily whitelist specific Mod IDs via serverconfig/twilightinventorylock-server.toml
āļø Technical Improvements NBT Brute-force Scanning: Implemented a deep-scan algorithm that searches for item signatures within NBT/Component data. This ensures compatibility with various modded containers without requiring direct dependencies.
Better Feedback: Players now receive a detailed list of specific items causing the entry block.
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:JsuQavql:szLXb98V"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JsuQavql:szLXb98V"
}

