安裝Installation

關閉伺服器。用正常的 /stop，不要強制終止 —— 關服流程會做最後一次完整存檔。
把 jar 放進 plugins/。
啟動伺服器，插件會產生 plugins/Vault/config.yml 與 messages/。
編輯設定檔後執行 /vault reload。

確認安裝成功

啟動時 console 應該出現：

[Vault] Loaded 128 balances from MySQL.
[Vault] PlaceholderAPI expansions registered: %vault_*%, %vault3_*% and %vault2_*% (legacy).
==============================
Vault3
Version: 3.0.0
Status: ENABLED
==============================

執行 /version Vault 應顯示 3.0.0。

換版本

若新舊 jar 檔名不同，新檔不會覆蓋舊檔。請先刪除 plugins/ 裡的舊 jar，否則兩個都會被載入並產生重複插件衝突。

上傳損毀

若 console 出現這個，代表 jar 在傳輸過程中壞了，不是插件的問題：

InvalidPluginException: java.util.zip.ZipException:
  ZipFile invalid LOC header (bad signature)

用 FTP 時務必選 Binary 模式，ASCII 模式會改寫換行位元組而毀掉 jar。傳完後比對 SHA-256 是唯一能確認檔案完整的方法。

Stop the server with a normal /stop — not a forced kill. The shutdown path performs a final full save.
Drop the jar into plugins/.
Start the server; plugins/Vault/config.yml and messages/ are generated.
Edit the config, then run /vault reload.

Verifying the install

The console should show:

[Vault] Loaded 128 balances from MySQL.
[Vault] PlaceholderAPI expansions registered: %vault_*%, %vault3_*% and %vault2_*% (legacy).
==============================
Vault3
Version: 3.0.0
Status: ENABLED
==============================

/version Vault should report 3.0.0.

Upgrading

If the new jar has a different filename it will not replace the old one. Delete the old jar from plugins/ first, or both will load and collide as duplicate plugins.

Corrupted uploads

If the console shows this, the jar was damaged in transfer — it is not a plugin fault:

InvalidPluginException: java.util.zip.ZipException:
  ZipFile invalid LOC header (bad signature)

Always use binary mode for FTP; ASCII mode rewrites newline bytes and destroys the jar. Comparing SHA-256 after upload is the only reliable integrity check.