All versions
2.0.4
Release
TP HOME 2.0.47 months ago 32
Compatibility
Minecraft: Java Edition
1.21.10
Platform
NeoForge
Supported environments
Client and server
Changes
Update Log
sethomelimit Command Enhancements:
- Removed Global Override: The sethomelimit <limit> all option has been removed as per the user's request.
- Granular Limit Control: The command now provides more refined control over home limits:
- /sethomelimit <limit> admins: Sets the default home limit for all players with administrator privileges (OP level 2+).
- /sethomelimit <limit> regulars: Sets the default home limit for regular players.
- /sethomelimit <limit> <playername>: Allows setting a specific home limit for an individual player.
- Priority Mechanism:
- The command now adheres to a clear priority for applying limits: Specific Player Limit > Role-Based Limit (Admins/Regulars) > Default (if no specific/role limit is set).
- Feedback messages in-game clarify this priority.
- Impact Notifications: When setting role-based limits (admins or regulars), the system will now inform you how many players have specific limits set and thus will not be affected by the role-based change.
- Offline Player Limitation: Due to observed API limitations in Minecraft 1.21.10 NeoForge regarding reliable GameProfileCache access for offline players, the /sethomelimit <limit> <playername> and /listcustomlimits clear <player> commands currently only support online players.
New listcustomlimits Command for Management:
- A new command, /listcustomlimits, has been added to help manage players with specific home limits:
- /listcustomlimits count: Displays the total number of players who currently have a custom home limit configured.
- /listcustomlimits view <start> <end>: Shows a paginated list of players with custom limits. For online players, their current role (Admin/Regular) is displayed. For offline players, their role is listed as "Unknown (Offline)" due to API constraints in determining their OP status when not online.
- /listcustomlimits clear <player>: Removes a custom limit previously set for a specific player (currently supports online players only).
- /listcustomlimits clearrange <start> <end>: Allows for batch removal of custom limits for players within a specified range from the view list.
Backend Refactoring (HomeStorage.java):
- Hierarchical Limit System: HomeStorage has been refactored to support the new limit hierarchy, including dedicated fields for adminLimit and regularLimit.
- Dynamic Limit Retrieval: The getEffectiveLimit method now dynamically calculates a player's active home limit based on the defined priority.
- Data Persistence: The storage mechanism has been updated to correctly save and load the new limit configurations.
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:wDbytaJP:Abo37lmU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wDbytaJP:Abo37lmU"
}

