Tags
Creators
Details
2.0.0
Compatibility
Changes
Changelog 2.0.0
New Features
- Favorite Star Directly in the List: The favorite marker toggle has been moved to the beginning of the teleport point line. An empty star,
☆, is now used for a regular point, and a yellow filled star,★, is used for a favorite point. - Fast Favorite Portal Delay: The fast favorite portal bind no longer opens the portal instantly. By default, 30 ticks (1.5 seconds) pass, during which sparks are visible in the center of the future portal, and only then does the portal begin opening.
- Custom Exit Portal Offset: The new
portalExitBehindDistanceparameter (default 0.2) controls how far behind the player the destination portal appears after a teleport. - Customizable Quick Favorite Portal DelayTicks: The newquickFavoritePortalDelayTicksparameter (default 30) controls the delay before the portal starts opening after pressing the quick bind.
Fixes
-
Extra Sound at Exit Portal: The destination portal no longer plays an opening sound when appearing after a teleport.
-
Interdimensional Markers for Common Items: For the common staff and scroll, the selection screen and teleport logic are now limited to markers in the current dimension. The Infinite Staff can still work between dimensions.
-
Favorite Quick Bind and Other Dimensions: If the favorite marker is in another dimension, the quick bind now correctly displays a limitation message instead of attempting to open the portal with a common item. ## Technical Changes
-
PendingTeleportManagerhas received aPendingFavoriteActivationqueue for delayed opening of a favorite portal with pre-sparks. -
PortalSessionhas been extended with a separatedestinationExitPosexit point, allowing the visual portal to be moved back without moving the player's spawn point. -
The
playChimeandplayOpenSoundflags have been added to the portal creation network packets to separately control the appearance sounds of the source and output portals. -
sendWaypointScreen()now filters the list of markers by the current dimension if the player does not have creative access to inter-world portals.
Changed files
- src/main/java/com/mentality/mrportal/config/MRPortalConfig.java
- src/main/java/com/mentality/mrportal/network/MRPortalNetworking.java
- src/main/java/com/mentality/mrportal/portal/PendingTeleportManager.java
- src/main/java/com/mentality/mrportal/portal/PortalSession.java
- src/client/java/com/mentality/mrportal/client/config/MRPortalConfigScreen.java
- src/client/java/com/mentality/mrportal/client/render/ClientPortalEffectManager.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:cEOEDyfg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mdzZXhdv:cEOEDyfg"
}

