All versions
1.1.0
Beta
Mentalitys | Chrono Portal 1.1.0last month 5
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
Chrono Portal 1.0.0-alpha Changelog
Summary
First working alpha/MVP release of Chrono Portal.
Added
- Fabric addon scaffold.
- Dependency on Mentalitys | MR Portal.
- Chrono Portal mod metadata.
- MR-Portal teleport handler implementation.
- High-priority handler registration.
- Chrono-owned server teleport sessions.
- Session manager with server tick processing.
- Delayed teleport timing (30 ticks).
- Chrono networking packets:
chrono_portal:chrono_effect_startchrono_portal:chrono_effect_end
- Client networking receiver.
- Client placeholder effect manager.
- Minimal particle/sound feedback.
- Cleanup on completion, timeout, invalid player/world, or server stopping.
- Support for GUI teleport path.
- Support for quick favorite path through MR-Portal routing.
Preserved from MR-Portal
- Base payment/cooldown/resource validation.
- Scroll consumption.
- Ender pearl payment.
- Same-dimension restrictions.
- Waypoint ownership.
- Quick favorite base validation.
Known limitations
- Visuals are placeholder and not final.
- Effect broadcasting/tracking for nearby players is limited.
- Timing and animation style are basic.
- Broader runtime testing is still needed.
Compatibility
- Minecraft 1.20.1
- Fabric
- Requires MR-Portal 2.3.0+
Notes
- This alpha is not the final Chrono visual design.
- Future versions will refine visuals, timing, and player tracking.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| chrono-portal-1.1.0-sources.jar | Source jar | 9.32 KiB |
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:DpPHoHbi:dkK7wopK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DpPHoHbi:dkK7wopK"
}


