Links
Tags
Creators
Details
All versions
1.3.0+26.1.2-neoforge
Release
Paper Plane 1.3.0 — 26.1.2 Neoforge2 weeks ago 9
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
ftb-library-neoforge-26.1.2.7.jarAny compatible version
ftb-essentials-neoforge-26.1.2.4.jarAny compatible version
Changes
Paper Plane 1.3.0
New Features
- Back Paper Plane & Ender Back Paper Plane: Added two new items providing return teleportation via right-click.
- Uses FTB Essentials' native previous-position history and configured rules.
- Back Paper Plane: Single-use item crafted with 4 Bone Meal in a cross pattern around a Paper Plane. Consumed only after a teleport completes successfully.
- Ender Back Paper Plane: Reusable item crafted by surrounding a Back Paper Plane with 8 Ender Pearls. Never consumed.
- Visuals retain the exact existing 16x16 silhouette, folds, and alpha, using recolored palettes.
- Server Configuration: Added
enableTpaandenableBacktoggles inconfig/paper_plane.tomlto enable or disable plane abilities independently of FTB public command registration. Settings load on server start (server restart required after edits).
Fixes & Improvements
- Consumption Timing: Single-use paper planes now consume only upon actual movement completion. Warmup cancellations, interruptions, or failed teleports no longer consume the item.
- Item Behavior: Retains non-throwable, right-click interaction established in 1.2.0 across all 17 supported combinations, including original TPA planes and the Soggy variant.
- Corrected the minimum FTB Essentials runtime dependency for Minecraft 1.21.1 (Fabric and NeoForge) to 2101.1.10 or newer within the 2101 series.
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:Ead9jIT4:67Tf2FAp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ead9jIT4:67Tf2FAp"
}

