Tags
Creators
Details
0.4
Compatibility
Changes
π¦ Changelog β WorldAccessBlocker
[0.4] β 2025-06-07
β¨ Added
-
π Time Zone Support
Addedtime-zoneoption inconfig.ymlto specify a custom time zone for restriction dates (e.g.,UTC,Europe/Moscow).
β Includes reference link to the IANA Time Zone Database. -
π Granular Restrictions
Introduced detailed restriction toggles for:- Nether:
portal-creation,teleportation - End:
portal-activation - Elytra:
equipping,flight
- Nether:
-
π‘οΈ Bypass Command
New command:
/wab bypass <player> <feature> <duration>
Temporarily allows a player to bypass restrictions for Nether, End, or Elytra.
-
β¨οΈ Tab Completion
Added intelligent tab suggestions for/wabcommand: -
Subcommands (e.g.
bypass) -
Online player names
-
Features:
nether,end,elytra -
Durations (e.g.
3600,86400) -
π¨ Active Restriction Check
Plugin now periodically checks if players are inside restricted dimensions (Nether or End) and teleports them out if needed.
π Fixed
-
Nether Portal Creation
Fixed exploit where players could still create Nether portals by handlingPortalCreateEvent. -
Vehicle Teleportation
Resolved issue allowing teleportation into the Nether using boats or minecarts viaEntityPortalEvent. -
Elytra Equipping
Fixed bypass where players could equip elytra using off-hand right-click (handled viaPlayerInteractEvent).
π§ Changed
-
β‘ Performance Optimizations
Improved event handlers with early-exit conditions to reduce CPU usage on high-player servers. -
π Language Enhancements
Updateden.ymlandru.ymlto display remaining restriction time in days and hours for clearer user messages. -
π Configuration Layout
Restructuredconfig.yml: -
Grouped features under
nether,end,elytrasections -
Added clear comments and descriptions for easier customization
π Notes
- β
Plugin now supports Folia, though Nether portal blocking may still be limited due to
PlayerPortalEventbehavior. - π§ Make sure to set a valid IANA time zone in the config (
time-zone: Europe/Moscow, etc.). - π Check
config.ymlfor new nested options and adjust your settings accordingly.
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:chVqXf9e:iEVUZQUP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:chVqXf9e:iEVUZQUP"
}

