Tags
Creators
Details
Licensed CC0-1.0
Published 7 months ago
Updated 5 months ago
All versions
1.9.0
Beta
Mentalitys | MR-portal 1.9.07 months ago 19
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Changes
Changelog 1.9.0
Fixes
- Portal Hitbox Too Large: Teleportation no longer triggers early when simply approaching. The entry check has been rewritten from a large cylinder around the portal's center to an intersection with the portal's thin plane, taking into account the yaw rotation.
- Staff in Inventory: The staff search logic now considers not only hands but also the inventory, making the binding behavior more consistent.
New Features
- Favorite Marker: You can now mark a single teleport point as a favorite. The favorite point is saved on the server, highlighted with a star in the list, and displayed in the sidebar.
- Quick Portal to Favorite Point: A second configurable bind has been added. The default key is the 'ё' key (the same physical keycode as the grave accent).
- Quick Open Item Priority: When activating a quick portal, the following order is used: infinite staff, regular staff, teleport scroll.
Behavior
- If the favorite waypoint is in another dimension, the quick bind will only work if the player has an infinite staff or creative access.
- If the favorite waypoint is not selected, the player receives a separate message about it.
Technical Changes
WaypointDatahas been expanded with thefavoriteflag, serialization to NBT, network buffer, and server JSON storage have been updated.ServerWaypointStorehas been updated with thesetFavoriteWaypoint,clearFavoriteWaypoint, andgetFavoriteWaypointmethods.MRPortalNetworkinghas been updated with new packages:set_favorite_waypointandquick_teleport_by_keybind. - InPendingTeleportManager, portal hit checking now uses the entity's AABB, portal plane, and bounded thickness instead of a circular zone with no direction.
Changed files
- src/main/java/com/mentality/mrportal/portal/PendingTeleportManager.java
- src/main/java/com/mentality/mrportal/network/MRPortalNetworking.java
- src/main/java/com/mentality/mrportal/waypoint/WaypointData.java
- src/main/java/com/mentality/mrportal/waypoint/ServerWaypointStore.java
- src/client/java/com/mentality/mrportal/MRPortalClient.java
- src/client/java/com/mentality/mrportal/client/screen/MRPortalClientNetworking.java
- src/client/java/com/mentality/mrportal/client/screen/WaypointScreen.java
- src/main/resources/assets/mr_portal/lang/en_us.json
- src/main/resources/assets/mr_portal/lang/ru_ru.json
- gradle.properties
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:YpoBz3ma"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mdzZXhdv:YpoBz3ma"
}

