Tags
Creators
Details
Licensed CC0-1.0
Published 7 months ago
Updated 5 months ago
All versions
1.4.0
Release
Mentalitys | MR-portal 1.4.07 months ago 7
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Changes
Changelog 1.4.0
GUI
- Completely redesigned waypoint selection interface
- Waypoints are now grouped by dimensions with section headers
- The player's current dimension is always displayed first in the list
- The waypoint name is requested via a modal dialog only when adding a new waypoint
- Removed the name input field from the main screen — it no longer gets in the way
- Added a "Name" button for renaming existing waypoints
- Improved waypoint selection — clickable lines with correct positioning
- Added a scrollbar for long waypoint lists
- Confirmation dialogs (delete, enter name, rename) overlay the interface with a semi-transparent background
Portal
- The portal now always collapses smoothly at the end of its lifespan, even if no one has accessed it
- The server begins closing after the active period (portalOpenDelay + portalActiveTicks) ends, then waits for portalCloseDelayTicks before sending PORTAL_CLOSE
- The client-side portal effect receives an increased lifetime (+40 ticks) to ensure smooth shutdown on server command
Network
- Added RENAME_WAYPOINT_C2S package for waypoint renaming
- The server normalizes the name when renaming (trim, 32-character limit, fallback to autoname)
Storage
- ServerWaypointStore: Added renameWaypoint method for updating waypoint names by UUID
Localization
- Added keys: screen.mr_portal.rename, screen.mr_portal.rename_title, screen.mr_portal.dialog_ok, screen.mr_portal.dialog_cancel
- Updated both localization files (ru_ru.json, en_us.json)
Other
- Updated version to 1.4.0
- Updated readme.md and readme_en.md
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:mdzZXhdv:N5YfNEuh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mdzZXhdv:N5YfNEuh"
}

