Tags
Creators
Details
All versions
1.4.0
Release
1.4.09 months ago 30
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.4–1.21.11
Platforms
Folia
Paper
Changes
What's Changed
- Added
/portal notificationcommands- Added
/portal notification list <portal> [<trigger>]- list entries are clickable to make editing notifications easier
- Added
/portal notification remove <portal> <trigger> <notification> - Added
/portal notification set <portal> <trigger> (sound|actionbar|message|title)- sound:
<sound> [<sound-source>] - actionbar:
<message> - message:
<message> - title:
<title> [<subtitle>] [<fade-in>] <stay> <fade-out>
- sound:
- Added
- Portal triggers:
entry_failure-> triggered when portal entry was denied (e.g. insufficient funds, lacking permission)entry_success-> successfully entered portalexit-> exited portalteleport_failure-> action failed (for custom implementations / future updates)teleport_success-> action succeeded (e.g. successfully teleported)warmup_failure-> warmup was interrupted by entity leaving the portalwarmup_success-> warmup was fully awaited
- Placeholders that are usable in all applicable notifications:
<cooldown>-> the portal cooldown in seconds<warmup>-> the portal warmup in seconds<remaining-cooldown>-> the entity's remaining cooldown for the portal in seconds<remaining-warmup>-> the entity's remaining warmup for the portal in seconds<entity>-> the entity's name<entry-cost>-> the formatted entry cost of the portal<permission>-> the entry permission of the portal (or "undefined" if not set)<portal>-> the name of the portal
- Message
portal.warmup.startwas removed in favor of this feature The same message can be recreated by adding aentry_successmessage to your portals:/portal notification set <portal> entry_success message <gray><blue>Portals</blue> <dark_gray>»</dark_gray> Do not leave the portal for <green><warmup:'#.##'></green> seconds…</gray>
Full Changelog: https://github.com/TheNextLvl-net/portals/compare/1.3.0...1.4.0
Optional dependencies
Any compatible version
Any compatible version
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:R2dgUCYq:Pzu4llYZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:R2dgUCYq:Pzu4llYZ"
}

