Player commands

.perk menu
.perk status [page]
.perk search <text>
.perk sync

.perk bufflist [page]
.perk buffdet <buffKey>
.perk buffbuy <buffKey>
.perk buffremove <buffKey>

.perk statlist [page]
.perk statdet <statKey>
.perk statbuy <statKey>
.perk statremove <statKey>

Admin commands

.perk admin
.perk info <player>
.perk reload
.perk validate
.perk diag
.perk syncall

.perk giftbuff <player> <buffKey>
.perk revokebuff <player> <buffKey>
.perk addbuff <player> <buffKey>
.perk clearbuff <player> <buffKey>

.perk giftstat <player> <statKey> <ranks>
.perk revokestat <player> <statKey> <ranks>
.perk addflat <player> <UnitStat|statKey> <amount>
.perk clearflat <player> <UnitStat|statKey>

Whitelist commands

.perk wlstatus
.perk wlcheckbuff
.perk wlcheckstat
.perk wlcheckall

.perk wlplayer <player>
.perk wladdbuff <player>
.perk wlremovebuff <player>
.perk wladdstat <player>
.perk wlremovestat <player>

PerkShop has optional whitelist controls for limiting who can use the buff shop, stat shop, or both.

Whitelist behavior is controlled in BepInEx/config/PerkShop/perkconfig.json.

Typical whitelist fields are:

{
  "EnableBuffWhitelist": false,
  "EnableStatWhitelist": false,
  "BuffWhitelist": [],
  "StatWhitelist": []
}

When a whitelist is disabled, everyone can use that shop if the shop itself is enabled.

When a whitelist is enabled, only players in that whitelist can buy/use that shop.

Check whitelist state

.perk wlstatus

Shows whether buff/stat whitelists are enabled and how many players are listed.

.perk wlcheckbuff
.perk wlcheckstat
.perk wlcheckall

Checks whether your current character is allowed to use the buff shop, stat shop, or both.

Check a specific player

.perk wlplayer <player>

Shows whether a player is currently allowed to use PerkShop features.

Add or remove a player

Allow a player to use the buff shop:

.perk wladdbuff <player>

Remove a player from the buff shop whitelist:

.perk wlremovebuff <player>

Allow a player to use the stat shop:

.perk wladdstat <player>

Remove a player from the stat shop whitelist:

.perk wlremovestat <player>

Recommended whitelist setup

For a public server, a common setup is:

{
  "EnableBuffWhitelist": false,
  "EnableStatWhitelist": false
}

For a donor/event/admin-only perk shop, enable one or both whitelists and add players with the commands above.

Whitelist data is saved in PerkShop's config/data files and persists across restarts.

Main config file:

BepInEx/config/PerkShop/perkconfig.json

Recommended live-server defaults:

{
  "EnableDebugLogging": false,
  "AutoDetectConfigChanges": false,
  "ReapplyOwnedBuffsWhenMissing": true,
  "ReapplyCheckIntervalSeconds": 60,
  "ReapplyMaxUsersPerCycle": 5,
  "OwnershipSaveDebounceSeconds": 2,
  "PlayerCacheSaveDebounceSeconds": 30,
  "RenewableTimedBuffDurationSeconds": 7200
}

After editing the config, reload and validate:

.perk reload
.perk validate
.perk diag

Adding buffs to the shop

PerkShop buffs are configured under the Buffs object. Each entry key is the command key players use with .perk buffbuy <key>.

Minimal example:

"myBuffKey": {
  "Enabled": true,
  "DisplayName": "My Custom Buff",
  "Category": "misc",
  "BuffPrefab": 123456789,
  "Cost": 100,
  "PersistentPurchase": true,
  "PreventDuplicate": true,
  "DurationSeconds": 7200,
  "PersistThroughDeath": false,
  "MutateAppliedBuffLifetime": true,
  "Notes": "Short explanation shown in .perk buffdet."
}

Recommended process:

1. Pick a short, clear key such as ragePotion, sunImmune, or warriorT1.
2. Set BuffPrefab to the V Rising PrefabGUID for the buff.
3. Choose an existing category such as potion, elixir, blood_buff, or misc.
4. Set Cost and Enabled.
5. Run .perk reload, then .perk validate.
6. Test with .perk buffdet <key> and .perk buffbuy <key>.

Important fields:

Potions, elixirs, and blood buffs use renewable timed mode by default. They keep a visible countdown and are reapplied by ownership when missing or expired. This is intentional and safer than stripping vanilla lifetime cleanup.

Avoid adding exotic or scripted buffs unless you test them carefully. Good candidates are passive stat buffs, consumable-style buffs, blood-tier buffs, and simple utility buffs. Avoid shapeshift, travel, channel, summon, boss phase, quest, tutorial, or temporary spell-execution buffs.

Stat keys

Players use these keys with:

.perk statbuy <key>
.perk statdet <key>
.perk statremove <key>

Common stat keys:

Some stats are gameplay-active but may not appear in TAB/Eclipse if the client UI does not render that stat type.

Blood-buff keys

Players use these keys with:

.perk buffbuy <key>
.perk buffdet <key>
.perk buffremove <key>

Examples:

warriorT1
warriorT2
warriorT3
warriorT4

rogueT1
rogueT2
rogueT3
rogueT4

bruteT1
bruteT2
bruteT3
bruteT4

Default blood families:

bruteT1-T4
corruptionT1-T4
creatureT1-T4
draculinT1-T4
mutantT1-T4
rogueT1-T4
scholarT1-T4
warriorT1-T4
workerT1-T4

Disabled by default:

draculaT1-T5
generalT5

For the complete key list, see docs/KEYS.md.