All versions
1.1.0
Release
Create: FlyHigher-直上九霄 1.1.0last week 1,998
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
1.1.0 — Dimension & Altitude Sensor support
Added
- Per-dimension pressure adaptation: dimensions without their own Sable
dimension_physicsentry now receive Fly Higher's curve automatically. - The 1.0 atm anchor is placed at each dimension's sea level (
Level.getSeaLevel()), so the Nether, the End and modded dimensions no longer fall back to Sable's default pressure. - The Altitude Sensor's air-pressure readout now follows the same per-dimension curve. Height still reports the sensor's true world Y.
- New common config option:
[dimensions] adaptOtherDimensions(defaulttrue). Set it tofalseto keep Sable's defaults outside the Overworld.
Changed
- Dimension entries are injected before Sable builds its datapack sync packet, so clients receive the adjusted values on join or
/reload. - Existing
config/flyhigher.jsonfiles and node format remain compatible.
Notes
- Dimensions with an explicit
dimension_physicsdatapack entry are left untouched. - No per-tick work: adaptation runs only on datapack sync.
- Tested with Create Aeronautics / Sable 2.0.6 on NeoForge 1.21.1.
1.1.0 — 多维度与高度传感器适配
新增
- 没有自定义 Sable
dimension_physics的维度会自动套用 Fly Higher 的气压曲线。 - 1.0 atm 锚点放到各维度海平面(
Level.getSeaLevel()),下界、末地和模组维度不再回退到 Sable 默认气压。 - 高度传感器的气压读数使用同一套按维度曲线;高度读数仍为真实世界 Y。
- 新增通用配置
[dimensions] adaptOtherDimensions,默认true;设为false可在主世界以外保留 Sable 默认值。
变更
- 维度条目在 Sable 构建同步包之前注入,玩家加入或
/reload时客户端即可收到调整后的数值。 - 现有
config/flyhigher.json与节点格式保持兼容。
说明
- 带有显式
dimension_physics数据包的维度不会被覆盖。 - 没有逐 tick 逻辑,只在 datapack sync 时处理。
- 已在 NeoForge 1.21.1 + Create Aeronautics / Sable 2.0.6 下测试。
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:cePRJjRZ:WPBGGFVT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cePRJjRZ:WPBGGFVT"
}

