Potassium
一款保守的 Minecraft 客户端性能模组,它会削减可选的渲染工作并提供诚实、实时的帧时间诊断——且不会触碰你的视频设置、世界或光影。
Potassium 不承诺带来魔法般的 FPS 提升。它减少游戏非严格必需的工作(如隐藏实体、远处/溢出粒子、冗余遮挡检测)并报告实际发生的情况,以便你自己衡量差异。
要求
- Minecraft 26.3
- Fabric Loader 0.19.3 或更高版本
- Java 25 或更高版本
- 仅限客户端(在专用服务器上无任何作用)
它使用的两个 Fabric API 模块(fabric-command-api-v2 和 fabric-api-base)已打包在 jar 文件中,因此你不需要安装完整的 Fabric API——只需 Fabric Loader 即可。Sodium 是可选的;如果安装了 Sodium,Potassium 的选项将出现在 Sodium 的配置界面中。
功能
保守的实体与区块实体剔除
跳过被地形遮挡的实体渲染,使用有界光线投射和缓存的可见性结果。它故意保持谨慎:
- 仅对有限的原版生物类型进行遮挡剔除;其他实体不受影响。
- 箱子区块实体(箱子、陷阱箱、末影箱)会被剔除;其他区块实体不受影响。
- 缓存采用有界的 LRU 映射,并在相机、模型或地形发生变化时失效。
- 如有疑问,它倾向于少剔除而不是冒险隐藏你能看到的物体。有限采样无法证明每个微小缝隙都被阻挡,因此它倾向于显示实体。
如果安装了 Iris 或 EntityCulling,Potassium 的遮挡剔除会自动禁用以避免冲突。
可选的粒子预算与距离剔除
- 软性粒子上限(一种预算而非硬性限制),以防止粒子密集的场景压倒画面。
- 可选的基于距离的粒子剔除。
- 两者均可配置并可关闭。
基于硬件的配置档案
首次运行时,Potassium 会检测你的 GPU 和系统并建议一个起始配置文件。这是一种启发式方法,而非经过测量的 FPS 保证。提供五种配置文件:
- 兼容性 — 剔除关闭,最小改动
- 平衡
- 性能
- 最大性能
- 自定义 — 你自己的设置
你可以接受建议、自行选择配置文件或完全自定义。自动配置文件选择可以禁用。
可选的自适应工作量管理(默认关闭)
启用后,Potassium 会监控你的帧时间并温和地调整可选工作——包括粒子预算、遮挡光线投射预算和重新检查间隔——以帮助维持目标 FPS。它从不改变分辨率、渲染距离、模拟距离、光影或世界模拟。它只会减少可选效果,并且在菜单中、暂停时或窗口失去焦点时会暂停自身运行。
失焦窗口节流
可选择在游戏窗口位于后台时限制帧率,以节省 CPU/GPU 资源和电力。
FPS 计数器与诊断信息
- 简单的彩色 FPS 计数器(左上角),按 F1/F3 隐藏。
- 可选的详细 HUD(右对齐),包含帧时间和缓存/粒子统计信息。
/potassium stats — 在聊天栏打印完整的诊断快照。
/potassium stats reset — 重置计数器和帧历史记录。
诊断信息是真实测量值,而非伪装成事实的估算值:
- 滚动帧时间窗口,包含平均 FPS、最差帧和峰值次数。
- 真正的 1% 和 0.1% 最低 FPS(从最慢的帧计算得出;在样本不足时显示为
n/a)。
- JVM 进程 CPU 使用率、分配率和垃圾回收计数/时间。
当某个数值无法诚实测量时,它会明确说明:GPU 利用率报告为 n/a,GC 收集器时间标记为收集器时间(而非停顿时间),缓存内存标记为 JVM 布局估算值。
它绝不会做的事
- 更改你的分辨率、渲染距离或模拟距离
- 静默更改光影设置
- 改变世界模拟或游戏玩法
- 禁用重要渲染
- 将质量降低称为“免费”优化
配置
设置保存在 config/potassium.json 中,并且当安装了 Sodium 时也会通过 Sodium 的选项界面暴露出来。每个功能都可以切换,预算/限制会被钳制在安全范围内。如果配置文件损坏或不可读,它将回退到保守的兼容性默认设置,而不会崩溃。
诚实的限制
- 遮挡剔除使用有限采样,因此它倾向于少剔除而不是冒险弹出可见实体。
- 如果存在 Iris 或 EntityCulling,Potassium 的遮挡剔除会退让。
- GPU 利用率无法从 JVM 中测量,因此显示为
n/a。
- 尚未声称经过基准测试的性能提升。 可控、可重复的基准测试仍在进行中;任何性能增益都取决于你的硬件、世界和设置。请使用
/potassium stats 在自己的机器上进行测量。
许可证与作者
MIT 许可证。作者:Doveblond。
Potassium
A conservative, client-side performance mod for Minecraft that trims optional rendering work and gives you honest, real frame-time diagnostics — without touching your video settings, your world, or your shaders.
Potassium does not promise a magic FPS number. It reduces work the game doesn't strictly need (hidden entities, distant/overflowing particles, redundant occlusion checks) and reports what actually happened, so you can measure the difference yourself.
Requirements
- Minecraft 26.3
- Fabric Loader 0.19.3 or newer
- Java 25 or newer
- Client-side only (does nothing on a dedicated server)
The two Fabric API modules it uses (fabric-command-api-v2 and fabric-api-base) are bundled inside the jar, so you do not need the full Fabric API — Fabric Loader is enough. Sodium is optional; if present, Potassium's options appear in Sodium's config screen.
What it does
Conservative entity & block-entity culling
Skips rendering entities that are occluded by terrain, using bounded raycasts and cached visibility results. It is deliberately cautious:
- Only a limited set of vanilla mob types are occlusion-culled; other entities are left alone.
- Chest block entities (chests, trapped chests, ender chests) are culled; other block entities are untouched.
- Caches are bounded LRU maps and are invalidated when the camera, models, or terrain change.
- When in doubt it under-culls rather than risk hiding something you can see. Finite sampling can't prove every tiny gap is blocked, so it errs toward showing entities.
If Iris or EntityCulling is installed, Potassium's occlusion culling disables itself to avoid conflicting with them.
Optional particle budgets & distance culling
- A soft particle cap (a budget, not a hard wall) to keep particle-heavy scenes from overwhelming the frame.
- Optional distance-based particle culling.
- Both are configurable and can be turned off.
Hardware-informed profiles
On first run Potassium detects your GPU and system and suggests a starting profile. This is a heuristic, not a measured FPS guarantee. Five profiles are available:
- Compatibility — culling off, minimal changes
- Balanced
- Performance
- Maximum Performance
- Custom — your own settings
You can accept the suggestion, pick a profile yourself, or go fully custom. Automatic profile selection can be disabled.
Optional adaptive workload management (off by default)
When enabled, Potassium watches your frame times and gently adjusts optional work — the particle budget, the occlusion raycast budget, and the recheck interval — to help hold your target FPS. It never changes resolution, render distance, simulation distance, shaders, or world simulation. It only ever reduces optional effects, and it suspends itself in menus, while paused, or when the window is unfocused.
Unfocused-window throttle
Optionally caps the frame rate while the game window is in the background to save CPU/GPU and power.
FPS counter & diagnostics
- A simple, color-coded FPS counter (top-left), hidden with F1/F3.
- An optional detailed HUD (right-aligned) with frame timing and cache/particle stats.
/potassium stats — prints a full diagnostic snapshot in chat.
/potassium stats reset — zeroes the counters and frame history.
Diagnostics are real measurements, not estimates dressed up as facts:
- Rolling frame-time window with average FPS, worst frame, and spike count.
- True 1% and 0.1% low FPS (computed from the slowest frames; shown as
n/a until enough frames are sampled).
- JVM process CPU usage, allocation rate, and garbage-collection counts/time.
Where a number can't be measured honestly, it says so: GPU utilization is reported as n/a, GC collector time is labeled as collector time (not pause time), and cache memory is labeled as a JVM-layout estimate.
What it will never do
- Change your resolution, render distance, or simulation distance
- Silently change shader settings
- Alter world simulation or gameplay
- Disable important rendering
- Call a quality reduction a "free" optimization
Configuration
Settings live in config/potassium.json and are also exposed through Sodium's options screen when Sodium is installed. Every feature can be toggled, and budgets/limits are clamped to safe ranges. A corrupt or unreadable config falls back to conservative Compatibility defaults rather than crashing.
Honest limitations
- Occlusion culling uses finite sampling, so it under-culls rather than risk popping visible entities.
- With Iris or EntityCulling present, Potassium's occlusion culling steps aside.
- GPU utilization is not measurable from the JVM and is shown as
n/a.
- No benchmarked speedup is claimed yet. Controlled, repeatable benchmarks are still in progress; any performance gain depends on your hardware, world, and settings. Use
/potassium stats to measure on your own machine.
License & author
MIT licensed. Author: Doveblond.
评论 0
登录后参与评分
还没有评论,来抢沙发吧