Tags
Creators
Details
All versions
1.7.0
Release
PPE Essentials 1.7.02 months ago 36
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
New
- Added interactive player menus for
/tpaand/tpaherewhen used without a player name - Added player list pagination, refresh controls, automatic TPA acceptance toggle, and safe inventory locking
- Added translated menu text for all supported languages
Improved
- Unified TPA and TPAhere request handling for more consistent validation, expiration, acceptance, and denial behavior
- Derived commands now follow their core command’s enabled state and permission level:
tpaa,tpad, andtpaautofollowtpatpahereaandtpaheredfollowtpaheredbackfollowsback
- Existing configuration files now automatically remove options and sections that are no longer supported
- A backup named
ppe_essentials-common.toml.pre-config-migration.bakis created before the first configuration cleanup - Reduced unnecessary Fabric configuration file checks
- Improved consistency between NeoForge and Fabric runtime events
- Updated loader and API compatibility
Fixed
- Fixed
/back,/tback,/home, and/warpreporting success when teleportation failed because the saved dimension was unavailable - Fixed duplicate or inconsistent TPA request behavior
- Fixed teleport menu refreshes unnecessarily reopening the interface
- Prevented moving, dragging, or collecting menu items from the teleport interface
Compatibility
- Minecraft
1.21.11is no longer supported - The temporary Minecraft
26.1.2importer for legacy player-data locations has been removed. If your data still exists only in an old location, migrate it with an earlier compatible build before updating
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:NB24iBsK:mHB9YVoL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NB24iBsK:mHB9YVoL"
}

