Gem Vault

Accessing the Gem Vault

Location:

• Gringotts Bank page
• Footer navigation (footer-bank hook)
• Link: "Gem Vault" or similar (appears after account created)

Initial Visit (No Account):

• Goblins offer vault service
• Explains gem protection benefits
• Account creation prompt
• Cost displayed: gemaccountcost (default: 1000 gold)

After Account Exists:

• Vault access interface
• Shows current gems in vault (gemsinbank pref)
• Shows gems on hand (player inventory)
• Deposit/withdraw options (no fee)

Creating a Vault Account

One-Time Setup:

• Cost: gemaccountcost setting (default: 1000 gold)
• Must have sufficient gold
• If insufficient: "You don't have enough gold" message
• Cannot proceed without payment
• Must already own at least 1 gem — the "Open new account" option is only offered to players who are already carrying a gem. You can't bootstrap a vault from zero gems.

Account Creation Process:

• 1. Visit Bank, click Gem Vault (requires already having a gem on hand)
• 2. Goblins explain service
• 3. Confirm account creation
• 4. Gold deducted: -1000 gold (default)
• 5. cacc (Created Account) pref set to 1
• 6. Account active immediately
• 7. gemsinbank pref initialized to 1, not 0 — the goblins throw in one complimentary gem as a welcome bonus

Not-So-Permanent Account:

• The account record is not permanent: the dragonkilltext hook sets cacc back to 0 unconditionally on every single VE dragon kill, regardless of the dktake setting
• No recurring fees while the account is active — but a fresh VE effectively closes it
• No account closure option, but the goblins will close it for you at every VE anyway
• If you still have gems sitting in the vault after a VE (dktake = 0), your next visit silently flips cacc back to 1 for free — the vault "remembers" you because you still have a balance
• If your gems were wiped along with the account (dktake = 1), you're back to square one: no gems, no account, and you'll need another gem in pocket plus another 1000 gold to reopen

Depositing Gems

Interface:

• Form: Enter number of gems to deposit
• Shows current gems on hand: "You have X gems"
• Shows vault capacity: "Vault holds Y gems (max: maxgemsinbank)"
• No fee charged for depositing — the game defines a gemtransfercost setting, but the deposit code never reads or applies it

Deposit Process:

• 1. Enter gem amount (0 or blank deposits everything you're carrying)
• 2. Vault capacity check (gemsinbank + amount ≤ maxgemsinbank; overflow amounts are clamped down to whatever fits)
• 3. Gem-on-hand check (can't deposit more than you're carrying)
• 4. If valid: gems move from your inventory straight into gemsinbank pref — no gold changes hands
• 5. Confirmation message

Deposit Restrictions:

• Insufficient Gems: Can't deposit more than you have
• Vault Full: Can't exceed maxgemsinbank (default 500) — excess is silently clamped to the remaining space
• Error messages for each failure case

Example Deposit:

• You have: 15 gems, 2000 gold
• Vault has: 50 gems (max 500)
• Deposit: 10 gems
• Result: 5 gems in pocket, 2000 gold (unchanged), 60 gems in vault

Withdrawing Gems

Interface:

• Form: Enter number of gems to withdraw
• Shows vault contents: "Vault contains X gems"
• No fee charged for withdrawing — same story as deposits, the gemtransfercost setting exists but is never applied

Withdrawal Process:

• 1. Enter gem amount (0 or blank withdraws the entire vault balance)
• 2. Vault balance check (gemsinbank >= amount)
• 3. If valid: gems move from gemsinbank pref straight into your inventory — no gold changes hands
• 4. Confirmation message

Withdrawal Restrictions:

• Insufficient Vault Gems: Can't withdraw more than stored
• Withdrawing your own gems back out is entirely free

Example Withdrawal:

• You have: 5 gems, 800 gold
• Vault has: 60 gems
• Withdraw: 7 gems
• Result: 12 gems in pocket, 800 gold (unchanged), 53 gems in vault

Death Protection

Gems Lost on Death (Without Vault):

• Normal death: All gems in pocket lost (standard LoGD mechanic)
• No protection for carried gems
• PvP deaths, forest deaths, event deaths all cost gems

Gems Protected in Vault:

• Vault gems NEVER lost to death
• Safe regardless of death cause
• gemsinbank pref unchanged on death
• Can withdraw after resurrection

Strategic Implications:

• Store gems before dangerous activities (PvP, hard forest fights)
• Keep only needed gems in pocket
• Vault acts as death insurance
• No fee to weigh against the risk — depositing and withdrawing cost nothing, only the initial 1000-gold account fee does

VE Dragon Kill Behavior

dktake Setting:

• Controls whether the gem balance empties at VE (dragon kill)
• Default: 1 (gems DO empty)
• If dktake = 0: Vault gems carry over to next VE
• Important: regardless of dktake, the account record (cacc) is unconditionally reset to 0 by every dragon kill — the goblins "forget" you every single VE

If dktake = 1 (Default - Gems Empty):

• On VE dragon kill: gemsinbank pref reset to 0, AND cacc reset to 0 (dragonkilltext hook)
• All stored gems lost, and the account is gone with them
• Because gemsinbank is now 0, nothing auto-reactivates cacc on your next visit — you must pay the full 1000 gold (and be carrying a gem) to reopen
• VE resets the vault like death resets pocket gems, only worse — it takes the account with it

If dktake = 0 (Gems Persist):

• On VE: gemsinbank unchanged, but cacc is still reset to 0 by the hook
• Because you still have a positive gem balance, the very next time you open the Gem Vault page the module notices gemsinbank > 0 and silently flips cacc back to 1 for free — no repayment needed
• Net effect: your gems and your account both survive, it just takes one extra page load to "reactivate"
• Admin decision for server economy balance

Server Balance Consideration:

• dktake = 1: Fresh start each VE — no gem accumulation, and you're paying the 1000-gold account fee again from scratch
• dktake = 0: Rewards vault investment, creates gem wealth gap, and spares you from repaying the account fee
• Most servers use dktake = 1 (reset)

Admin Configuration

Settings:

• gemaccountcost: Account creation cost (int, default: 1000 gold)
• gemtransfercost: Defined in the module's settings (int, default: 100 gold), but never read by the deposit or withdraw handlers — it has no effect on anything. A vestigial setting.
• maxgemsinbank: Maximum vault capacity (int, default: 500 gems)
• dktake: Empty the gem balance at VE? (bool, default: 1 - yes, empty). The account record itself resets at VE regardless of this setting.

User Preferences:

• gemsinbank: Gems currently in vault (int, default: 0; set to 1 the moment an account is opened)
• cacc: Has created account (bool, default: 0)

Hooks Used:

• footer-bank: Adds Gem Vault navigation link
• dragonkilltext: Unconditionally resets cacc to 0 every VE, and additionally zeroes gemsinbank if dktake = 1

Cost Analysis

Account Creation Investment

Setting	Default Cost	Equivalent In
gemaccountcost	1000 gold	~1 gem value, several forest fights

Is 1000 gold worth it?

• If you die frequently: YES (protects gems from all deaths)
• If you hoard gems: YES (prevents loss of valuable stockpile)
• If you rarely die: MAYBE (less urgent, but still insurance)
• If you never have gems: NO (nothing to protect)

Break-Even Analysis

When does vault pay for itself?

• Account cost: 1000 gold (one-time), plus already owning a gem to even open it
• If you would have lost even one gem to death without vault: Vault saved you gem value against a 1000 gold cost, and every deposit/withdrawal after that is free
• Frequent deaths make vault economical quickly
• Rare deaths make vault a luxury — though a cheap one, since there's no ongoing cost once you've opened it

Strategy & Best Practices

For New Players

Should I Get a Vault Early?

• YES if:
  • You die often (learning forest combat)
  • You PvP frequently
  • You're accumulating gems (quests, donations)
  • 1000 gold is affordable (not breaking your budget)
• WAIT if:
  • You have 0 gems (nothing to protect — and you literally can't open the account without one anyway)
  • 1000 gold would bankrupt you (need gold for healing/equipment)
  • You rarely die (low risk)

For Experienced Players

Optimal Vault Usage:

• Keep small working inventory in pocket (2-5 gems)
• Store bulk gems in vault (protect hoard)
• Withdraw only when needed for purchases
• Deposit after gem acquisition (quest rewards, donations)
• Pre-deposit before risky activities (PvP, dangerous forest, experimental events)

Transfer Timing:

• Deposit: After earning gems (quest completion, finding gems) — costs nothing, so there's no reason to delay
• Withdraw: Before gem purchases (shops, potions, services) — also free
• No need to batch transfers to save on fees, since there are none

For High-VE Players

VE Planning:

• If dktake = 1: Expect the gem balance and the account itself to be wiped at dragon kill — you'll need a gem in pocket plus another 1000 gold to reopen
• Withdraw gems before VE attempt if planning major post-VE purchases
• Or accept gem loss as VE cost
• If dktake = 0: Vault becomes a long-term gem savings account across VEs, and the account quietly reactivates itself on your next visit — no repayment needed

For Admins

Economy Tuning:

• gemaccountcost: Higher = exclusive feature, Lower = accessible to all
• gemtransfercost: Configurable but currently dead weight — the deposit/withdraw code never applies it. Changing it has no in-game effect unless the module is patched to actually charge it.
• maxgemsinbank: Higher = unlimited hoarding, Lower = forces gem spending
• dktake: 1 = VE resets both gems and account (fresh start, repeat account fee), 0 = wealth accumulation (gap between veterans/newbies) with a self-healing account

Recommended Settings:

• New Server: Low account cost (500g), dktake = 1
• Established Server: Default settings work, adjust based on gold inflation
• High Economy: Increase account cost to match gold availability

Common Questions

Q: Do I lose vault gems when I die?
A: No. Vault gems always protected from death. Only pocket gems lost.

Q: Do I lose vault gems at VE?
A: Depends on dktake setting. If dktake = 1 (default): Yes, gemsinbank empties. If dktake = 0: No, gems carry over.

Q: Does withdrawing MY OWN gems cost gold?
A: No. Deposits and withdrawals are both free — the module has a gemtransfercost setting on the books, but the code never actually charges it.

Q: Can I increase my vault capacity beyond 500 gems?
A: Only if admin increases maxgemsinbank setting. Player cannot expand vault individually.

Q: What happens if I try to deposit more than the vault can hold?
A: The excess is silently clamped down to whatever space remains — you're not blocked outright, you just don't get to stuff in more than fits.

Q: Can I transfer gems to another player via vault?
A: No. Vault is personal storage only. Use gem transfer features (if available) for gifting.

Q: Does vault account persist across VEs?
A: No, not automatically. Every VE dragon kill resets the account flag (cacc) to 0 unconditionally. If you had gems left in the vault (dktake = 0), the account silently reactivates for free next time you visit. If your gems were also wiped (dktake = 1), you need a gem in hand and another 1000 gold to reopen.

Q: Can I get a refund if I close my account?
A: No account closure mechanism. The 1000 gold is nonrefundable — and the goblins will effectively "close" it for you at the next VE anyway.

Q: Do I need to already have a gem to open a vault account?
A: Yes. The option to open an account only appears if you're already carrying at least one gem. Show up empty-handed and Gringotts won't even offer you the paperwork.

Limitations

• Chicken-and-Egg Entry Cost: You need a gem to open an account that's meant to protect your gems
• Capacity Limit: 500 gem cap (default) prevents unlimited hoarding
• VE Account Vulnerability: Every dragon kill wipes the account flag outright; if dktake = 1 your gems go with it and you're paying the 1000-gold fee again
• No Partial Transfers: Can't set automated rules (e.g., "always keep 10 in vault")
• No Interest/Growth: Gems don't multiply or gain value in vault (static storage)
• One Account Only: Cannot create multiple vaults or sub-accounts