Tags
Creators
Details
Licensed CC0-1.0
Published 7 months ago
Updated 5 months ago
All versions
2.1.0
Release
Mentalitys | MR-portal 2.1.07 months ago 26
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Changes
Changelog 2.1.0
Fixes
- Clicking on the favorites star now simultaneously selects the marker: Clicking on the star immediately sets the marker as the currently selected marker, as if the player had clicked the teleport line itself.
- Removed unnecessary text about favorites in the right GUI panel: The message indicating whether a marker is a favorite is no longer displayed—it's already clear from the star in the list.
- Portal remains passable for other entities until it actually closes: Checking the owner's position no longer blocks passage through an already open portal for other entities and players. While the portal is visually open, other entities can enter it for the rest of its life.
Technical Changes
WaypointScreen.mouseClicked()now first selects the marker and then switches favorites when clicking on the star. - Added an update to the local selection status inWaypointScreen.toggleFavorite()so that the GUI immediately behaves as if a label was selected normally.- Separated the logic for the owner's progress through the portal from the logic for other entities in
PendingTeleportManager.tickInternal(): the absence of the owner in the source dimension no longer interrupts processing of other entities.
Changed files
- src/client/java/com/mentality/mrportal/client/screen/WaypointScreen.java
- src/main/java/com/mentality/mrportal/portal/PendingTeleportManager.java
- gradle.properties
- readme.md
- 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:ogqf94NG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mdzZXhdv:ogqf94NG"
}

