Vault3選單與請款Menus and charge requests
付款選單
直接輸入 /pay 開啟分頁式玩家列表。點選玩家會進入子選單，可以：
- 付款 —— 直接轉帳給對方
- 請款 —— 要求對方付錢給你
- 查看餘額
選擇動作後在聊天欄輸入金額，輸入 cancel 可取消。
選單大小與是否顯示自己由 pay_menu.size 與 pay_menu.show_self 控制。
請款
| 對象狀態 | 行為 |
|---|---|
| 線上 | 對方立即收到一則可點擊的訊息，點下即完成付款 |
| 離線 | 請款被儲存，對方下次登入時送達 |
每次登入最多送出 pay_pending.max_on_join 筆，其餘留在佇列中。
使用 MySQL 時請款存在 vault_charge_requests；未啟用 MySQL 時存在記憶體中，
重啟會遺失。
額度限制
付款與請款都受 pay_limits 約束。
擁有 vault.pay.bypass_min 或 vault.pay.bypass_max 的玩家可略過。
設定編輯選單
/vault 開啟主選單，OP 可在其中直接修改部分設定並即時套用，
不需要離開遊戲編輯 YAML。
Payment menu
/pay with no arguments opens a paginated player list. Selecting a player opens a
submenu where you can:
- Pay — transfer money to them
- Charge — request money from them
- View balance
After choosing an action, type the amount in chat; typing cancel aborts.
Menu size and whether your own head is shown are controlled by pay_menu.size and
pay_menu.show_self.
Charge requests
| Target | Behaviour |
|---|---|
| Online | Receives a clickable message immediately; one click pays |
| Offline | The request is stored and delivered on their next login |
At most pay_pending.max_on_join requests are delivered per login; the rest stay
queued.
With MySQL, requests are stored in vault_charge_requests. Without it they are held
in memory and lost on restart.
Limits
Both paying and charging respect pay_limits. Players with
vault.pay.bypass_min or vault.pay.bypass_max are exempt.
Config editor
/vault opens the main menu, where operators can change selected settings in game
and have them applied immediately, without editing YAML.