F**kSable

一个专门修 Sable 的 mod / A mod that fixes Sable 因为 Sable 的作者挖坑不填，我来填 / Because Sable's author left holes, I'm filling them

Sable 是个让 Minecraft 方块物理化的 mod，想法很酷。但 Rust + Java 的缝合架构嘛……你懂的。这个 mod 的存在就是为了补那些能让服务器血压直接拉满的洞。

Sable is a Minecraft mod that adds physics to blocks — a cool concept. But the Rust + Java hybrid architecture... you know the drill. This mod exists to patch the holes that'll send your server's blood pressure through the roof.

前置 / Dependency

• Sable — 不是可选，毕竟我存在的意义就是擦它的屁股 / Not optional, after all, my whole reason for existing is to clean up its mess

版本说明 / Version Notes

当你发现某个版本标记为 Alpha（例如 v1.0.0-alpha.1），那大概是一个存在已知问题但未被下架的版本。Alpha 版本可能包含未完成的功能、已知的崩溃风险或性能问题，主要用于早期测试和反馈收集。

但请注意：Alpha 也包含 Beta 版本 —— 实际上某些 Beta 反而比 Alpha 更稳定。版本号只是个标签，不代表一切。

详细信息以 GitHub Releases 为准 —— 每个版本的发布说明都会清楚列出已知问题、适用范围和建议。不要只看版本号，看发布说明。也可从 OLKMO/FuckSable-Unofficial 获取。

生产环境请优先选择经过充分测试的版本。如果你在 Alpha/Beta 版本中遇到了问题，请理解——测试版就是测试版，崩了别意外。

When you see a version marked as Alpha (e.g., v1.0.0-alpha.1), it's probably a version with known issues that hasn't been taken down yet. Alpha releases may contain incomplete features, known crash risks, or performance problems — they're intended for early testing and feedback collection.

But note: Alpha includes Beta releases — in fact, some Betas are actually more stable than certain Alphas. Version numbers are just labels, they don't tell the whole story.

For detailed information, refer to GitHub Releases — each release's notes clearly list known issues, scope, and recommendations. Don't just look at the version number, read the release notes. Also available from OLKMO/FuckSable-Unofficial.

For production environments, choose thoroughly tested releases. If you encounter issues in an Alpha/Beta version, please understand — a test version is a test version, don't be surprised if it breaks.

修复项 / Fixes

默认全开，可通过配置文件单独关闭。依赖其他 mod 的修复项，缺 mod 会自动禁用。少数修复项因涉及前置依赖关系或基于 bug 的玩法，默认关闭（见下表标注）。

Enabled by default, can be disabled individually via config. Fixes that depend on other mods auto-disable if the mod is missing. A few fixes are disabled by default due to prerequisite dependencies or bug-based gameplay (see notes in the table below).

Sable 核心修复 / Core Fixes

兼容性修复 / Compatibility Fixes

调试命令 / Debug Commands

国际化 / Internationalization (i18n)

FuckSable 支持自定义语言包。所有可打印信息（命令反馈、日志等）都可以通过语言文件覆盖。

FuckSable supports custom language packs. All printable messages (command feedback, logs, etc.) can be overridden via language files.

使用方法 / Usage

/fucksablelang <语言文件名>

• <语言文件名>: 语言文件的名称（不含路径，不含扩展名）/ Language file name (without path, without extension)

语言文件位于 .minecraft/config/fucksable/lang/（服务端则为 config/fucksable/lang/）。

Language files are located in .minecraft/config/fucksable/lang/ (or config/fucksable/lang/ for servers).

默认语言包 / Default Language Packs

创建自定义语言包 / Creating Custom Language Packs

1. 进入 config/fucksable/lang/ 目录
2. 复制 en.yml 或 zh.yml 作为模板
3. 重命名为你想要的语言文件名（例如 ja.yml、es.yml、fr.yml）
4. 翻译 YAML 文件中的值（键名不要改）
5. 在游戏中执行 /fucksablelang <文件名> 切换

1. Navigate to `config/fucksable/lang/`
2. Copy `en.yml` or `zh.yml` as a template
3. Rename it to your desired language file name (e.g., `ja.yml`, `es.yml`, `fr.yml`)
4. Translate the values in the YAML file (don't change the keys)
5. Run `/fucksablelang <filename>` in-game to switch

注意事项 / Notes

• FuckSable 的可打印信息不是很多，所有文本加起来也就几十行

• 你完全可以直接丢给 GPT 去翻译，几秒钟搞定

• 切换语言后立即生效，不需要重启服务器

• 如果语言文件格式错误（无效 YAML），会自动回退到默认语言（英文）

• FuckSable's printable messages are not that many — all text combined is only a few dozen lines

• You can just throw it at GPT for translation, takes a few seconds

• Language switching takes effect immediately, no server restart required

• If a language file has invalid YAML, it will automatically fall back to default language (English)

示例：自定义语言文件结构 / Example: Custom Language File Structure

# zh.yml - 简体中文示例 / Simplified Chinese example

command:
  fucksable:
    title: "=== FuckSable 修复状态 ==="
    fix:
      enabled: "✓ %s 已启用"
      disabled: "✗ %s 已禁用"
      missing_dep: "⚠ %s 已禁用 (缺少依赖: %s)"
    invalid_fix: "无效的修复项: %s"
    set:
      enabled: "已将 %s 设置为 %s"
    lang:
      switched: "语言已切换至: %s"
      file_not_found: "语言文件不存在: %s"
      invalid_yml: "语言文件格式错误，已回退至默认语言"

# en.yml - 英文示例 / English example

command:
  fucksable:
    title: "=== FuckSable Fix Status ==="
    fix:
      enabled: "✓ %s is enabled"
      disabled: "✗ %s is disabled"
      missing_dep: "⚠ %s is disabled (missing dependency: %s)"
    invalid_fix: "Invalid fix: %s"
    set:
      enabled: "Set %s to %s"
    lang:
      switched: "Language switched to: %s"
      file_not_found: "Language file not found: %s"
      invalid_yml: "Invalid YAML format, falling back to default language"

为什么是 All-in-One？/ Why All-in-One?

Q: 为什么不写单独的 mod 逐个修复，而是全部打包在一起？

A: 因为我讨厌为了修复几个问题还要到处找补丁、一个个安装、反复排查冲突。

Q: Why not write separate mods for each fix?

A: Because I'm tired of hunting down patches, installing them one by one, and debugging conflicts just to fix a few issues.

FuckSable 是全部打包：

• 一个 mod，一次安装，所有修复同时生效
• 每一个修复都在真实服务端环境测试过，不是纸上谈兵
• 配置文件可以单独开关，不需要就不开
• 不用记这个 bug 归哪个 mod 管，一个命令全看见

FuckSable is all-in-one:

• One mod, one installation, all fixes work together
• Every fix has been tested on a real server environment, not just theory
• Config file lets you toggle individual fixes on/off
• No need to remember which bug belongs to which mod — one command shows everything

简单说就是：省事。

Simply put: Less hassle.

吐槽 / Rant

Sable 的 Rust + Java 架构本身不是问题。问题在于两边几乎都没有错误处理：

Sable's Rust + Java architecture isn't the problem. The problem is the near-total lack of error handling on both sides:

• Rust 侧 panic → 直接带走 JVM / Rust-side panic → directly takes down JVM
• Java 侧对 Rust 返回值校验 ≈ 不存在 / Java-side validation of Rust return values ≈ nonexistent
• 服务端引用客户端类？这不是边缘 case，是专用服务器一启动就崩的程度 / Server referencing client classes? Not edge cases, they crash dedicated servers at startup

依赖管理也是一坨屎：API 类散落在各种包路径下 —— SubLevelContainerHolder 在 mixinterface.plot 而不是 api.sublevel，JOMLConversion 在 companion.math。你永远猜不到下一个类在哪个包里。

Dependency management is also a mess: API classes scattered across random package paths — SubLevelContainerHolder in mixinterface.plot instead of api.sublevel, JOMLConversion in companion.math. You never know where the next class will be hiding.

但话说回来，方块物理化这个想法确实很酷。只是希望作者能多花点时间在稳定性上，而不是只追求功能。

But that said, the idea of block physics is indeed really cool. I just wish the author would spend more time on stability instead of just chasing features.

附加说明 / Additional Note

更新检查通过 GitHub Releases API（HTTPS）获取最新版本信息，启动时自动检查并在日志中提示。默认关闭，可通过配置文件开启。

Update checking uses the GitHub Releases API (HTTPS) to fetch the latest version info, automatically checks on startup and logs a notice if a new version is available. Disabled by default, can be enabled via config.

代码已开源，欢迎提交 Issue 和 PR。

• 主仓库 / Main repo: https://github.com/XSY-Team/fuck-sable
• 个人仓库 / Personal repo: https://github.com/OLKMO/FuckSable-Unofficial

The code is open source, feel free to submit Issues and PRs.

• Main repo: https://github.com/XSY-Team/fuck-sable
• Personal repo: https://github.com/OLKMO/FuckSable-Unofficial

许可证 / License

MIT License - 详见 LICENSE 文件。

MIT License - see LICENSE file for details.