Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 10 months ago
All versions
1.2.2
Release
customportalapi-reforged 1.2.2last year 20.4K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
v1.2.2
✨ New Features
-
Added Ignite Events
- Implemented
PortalIgniteEventandPortalPreIgniteEventinterfaces. - Included corresponding handlers and invokers.
- 🔧 These events allow:
- Executing custom logic before and after portal ignition.
- Cancelling the ignition entirely, if desired.
- Implemented
-
Player Entity in Ignite Context
- The player is now included as part of the ignition source in item-use events.
- ✅ Matches upstream behavior.
- 🔍 Enables event consumers to identify which player attempted to light the portal.
⚠️ Breaking Change
- Fixed Item Usage Behavior on Failed Portal Lighting
customportalapi-reforgedpreviously cancelled item usage when ignition failed, which is opposite of upstream behavior.- This has been reversed: item usage is now only cancelled if the portal is successfully lit.
- Example: Using an Eye of Ender to light a portal will no longer cause it to fly off and possibly break—it will be consumed only when ignition succeeds.
Credit murderspagurder for this PR!
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:VepYPOdy:lowfyLfO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VepYPOdy:lowfyLfO"
}

