BidVault
开箱即用的玩家拍卖行
大多数拍卖行插件都需要 Vault。它们需要经济类插件。它们需要数据库。在第一个玩家上架物品之前,你需要花半小时进行配置。然后当服务器或插件更新时,一半的依赖项就会出错。
BidVault 只需要一个 .jar 文件。
把它放进你的 plugins 文件夹。重启服务器。输入 /ah。你现在就拥有一个功能齐全的拍卖行,它拥有自己的经济系统、货币、图形用户界面(GUI)和搜索系统。不需要 Vault。不需要 EssentialsX Economy。不需要数据库设置。完全不需要外部经济插件。
玩家上架物品。其他玩家购买。资金流动。所有数据都存储在 JSON 文件中,你可以用文本编辑器阅读、编辑并备份。就这么简单。
如果你以后想要使用 Vault,也可以——BidVault 的经济系统设计为可替换的。但你起步时并不需要它。
玩家的体验
上架物品
玩家手持想要出售的物品。输入 /ahsell 500。物品从手中消失并出现在拍卖行中。完成。
这就是整个流程。没有点击告示牌。没有建造箱子商店。除了一个命令外无需记忆其他指令。手持物品,输入价格,完成。
如果玩家误上架了物品或改变了主意,他们可以从个人列表屏幕中将物品撤回。物品会回到他们的收藏箱中。
购买物品
玩家输入 /ah。打开一个包含每页 28 个列表并在底部显示完整分页的箱子 GUI。点击物品,查看其所有详细信息——名称、附魔、描述、卖家、价格、剩余时间——然后点击绿色的确认玻璃块进行购买。
存在确认界面的原因只有一个:防止误触。没人想因为双击而意外花费 50,000 金币买一块泥土。多出的这一点击只需半秒,但能节省一个客服工单。
当有人购买物品时:
- 买家立即获得物品
- 卖家获得扣除可配置销售税后的金额
- 如果卖家在线,他们会收到实时通知(聊天 + 音效)
- 如果卖家离线,钱会保留在他们的余额中,直到他们再次上线
收藏箱
过期的列表、已售出的物品(如果未来添加押金机制)、以及取消的列表都会进入个人收藏箱。通过 /ahcollect 打开它。物品会留在那里,直到玩家拾取。
这解决了困扰那些采用硬删除过期机制的插件的“我因为列表过期而丢失了物品”的问题。没有任何东西会被删除。它们会被收集起来。
搜索与筛选
正是在这里,BidVault 证明了它比简单的商店插件更有价值。
9 种物品分类:
- 全部
- 武器(剑、斧、三叉戟、弓、弩)
- 护甲(头盔、胸甲、护腿、靴子、盾牌)
- 工具(镐、铲、锄、剪刀、钓鱼竿)
- 方块(所有可放置方块)
- 食物(可食用物品)
- 药水(药水、喷溅药水、滞留药水)
- 附魔(任何带有附魔的物品)
- 杂项(其他所有物品)
6 种排序模式:
- 最新优先
- 最旧优先
- 价格从低到高
- 价格从高到低
- 名称 A 到 Z
- 名称 Z 到 A
实时搜索:
输入 /ahsearch diamond sword,GUI 会实时过滤出匹配的列表。搜索会在当前分类过滤器内进行,因此玩家可以选择“武器”,然后搜索“sharpness”来查找所有锋利附魔的剑。
关闭 GUI 时搜索会自动清除,以便下一个打开拍卖行的玩家从零开始。可配置——如果你的服务器偏好持久化搜索,可以禁用此功能。
分类按钮、排序按钮和分页控件都已集成在 GUI 中。玩家无需阅读任何说明就能理解。界面通过图标和物品标签自我解释。
内置经济系统
BidVault 自带一套经济系统。以下是它的功能:
- 初始余额:可配置。新玩家在首次与经济系统交互时会自动获得金钱。
- 玩家间支付:
/pay <player> <amount> —— 直接转账
- 余额查询:
/balance 查询自己,/balance <player> 查询他人
- 管理员经济控制:
/eco set|give|take <player> <amount> 用于完整的余额管理
- 销售税:从每笔交易中扣除的可配置百分比。税款无处可去——它被移出流通领域。内置的资金回收机制。
- 价格限制:设置最低和最高上架价格以防止滥用(零成本列表、万亿美元骗局)
所有余额都保存在 economy.json 中,跨服务器重启持久化。文件格式为标准 JSON——你可以阅读它、编写脚本处理它,或在需要时手动迁移数据。
如果你已经运行着 Vault + 经济插件,BidVault 也可以通过 Vault 进行集成。但重点在于你不需要 Vault。大多数中小型服务器不需要这种复杂性。BidVault 保持一切自给自足。
性能与架构
一切都在服务器端运行。无需客户端模组。无需资源包。无需注入或修改数据包。BidVault 完全通过 Bukkit 事件 API 和标准库存 GUI 工作。
数据存储:插件数据文件夹中的平面 JSON 文件。
auctions.json —— 所有活跃列表和收藏箱
economy.json —— 所有玩家余额
物品使用 Minecraft 原生的 NBT 序列化进行存储。这意味着每件物品的所有数据都被保留:附魔、自定义名称、描述文本、耐久度、不可破坏标志、自定义模型数据、头颅纹理、旗帜图案——应有尽有。在拍卖行上架的物品回来时将与原来完全一致。
自动保存每 5 分钟运行一次。数据也会在服务器关闭时刷新到磁盘(Bukkit 关闭钩子)。在拥有 200 名玩家的服务器上,JSON 文件保持小巧且解析迅速。
GUI 性能:基于箱子的 GUI 使用标准的 Bukkit 库存事件。没有基于刻的刷新循环,也没有计划的库存更新。点击事件在事件线程上同步处理。分页和过滤逻辑每次交互都在常数时间内运行。在任何合理的服务器硬件上,你都不会因为这个插件看到 TPS 下降。
配置
所有配置都在一个文件中。首次启动时自动生成,并带有合理的默认值。以下是你可以修改的内容:
# 经济
currency-symbol: "$"
starting-balance: 5000.0
# 商品列表
max-listings-per-player: 10
min-price: 1.0
max-price: 1000000000.0
default-duration-hours: 48
sales-tax: 5.0
# 过期
expiration-check-interval-minutes: 5
# 搜索
clear-search-on-close: true
# 反馈
enable-sounds: true
enable-actionbar-messages: true
这就是全部的配置文件了。每一行都一目了然。没有嵌套的 YAML 迷宫,也没有晦涩的节标题,更没有“只有当 section-b 为 false 且世界名称匹配正则表达式时才设为 true”这种复杂逻辑。这里只有你真正想要修改的设置。
无需重启即可重载:/ahreload
命令
玩家命令
| 命令 |
描述 |
权限 |
/ah |
打开拍卖行 GUI |
auctionhouse.use |
/ahsell <价格> |
以指定价格上架当前手持物品 |
auctionhouse.sell |
/ahsearch <查询> |
按物品名称搜索商品列表 |
auctionhouse.use |
/ahcollect |
打开你的收藏箱 |
auctionhouse.use |
/ahmylistings |
查看和管理你的活跃挂单 |
auctionhouse.sell |
/balance |
查看你的余额 |
所有人 |
/balance <玩家> |
查看其他玩家的余额 |
所有人 |
/pay <玩家> <金额> |
向其他玩家转账 |
所有人 |
管理员命令
| 命令 |
描述 |
权限 |
/ahreload |
重新加载配置文件 |
auctionhouse.admin |
/eco set <玩家> <金额> |
设置玩家的余额 |
auctionhouse.admin |
/eco give <玩家> <金额> |
增加玩家的余额 |
auctionhouse.admin |
| /eco take <玩家> <数量> | 从玩家的余额中扣除 | auctionhouse.admin |
为方便使用的命令别名:
/ah、/hdv、/auction —— 均可打开拍卖行
/bal、/money —— 余额快捷指令
/sell、/ahlist —— 上架快捷指令
所有命令均支持参数和玩家名称的完整 Tab 补全。
权限
| 权限 |
默认值 |
说明 |
auctionhouse.use |
所有人 |
打开拍卖行、搜索、浏览、购买、收取物品 |
auctionhouse.sell |
所有人 |
上架商品出售、管理自己的商品列表 |
auctionhouse.admin |
OP(管理员) |
重载配置文件、通过 /eco 命令管理玩家余额 |
权限模型故意设计得非常简单。只有三个节点。没有继承树。没有基于上下文的权限。使用 LuckPerms 或你使用的任何权限管理器,30 秒即可设置完成。
安装
- 从本页面下载
BidVault.jar
- 将其放入服务器的
/plugins/ 文件夹中
- 启动(或重启)服务器
- 搞定
插件会在首次启动时生成其配置文件和数据文件。无需预先配置。玩家可以立即开始上架物品。
无需 Vault。无需数据库。无需外部经济插件。无需额外依赖。
要求
- 服务器软件: Paper 1.21.x、Spigot 1.21.x 或兼容分支
- Java: 17+
- 外部依赖: 无。真的一个都没有。
可选:Vault(如果你想将 BidVault 的经济系统与使用 Vault 经济 API 的其他插件桥接)。但对于任何核心功能来说,它都不是必需的。
常见问题
为什么没有 Vault 依赖?
因为大多数玩家数少于 50 的服务器不需要 Vault。他们需要一个只需将文件拖入文件夹就能正常工作的拍卖行。Vault 会增加依赖链——你需要 Vault,然后需要经济插件,然后要确保版本兼容,接着某个东西更新后就会出问题。BidVault 为常见情况剔除了所有这些麻烦。如果你确实使用了 Vault,BidVault 可以接入它。但它是可选的。
上架过期后会怎样?
物品会移动到卖家的收藏箱中。它永远不会被删除。卖家打开 /ahcollect 并取回物品。永远不会丢失物品。
玩家能上架附魔物品 / 命名物品 / 带有 lore 的物品吗?
可以。所有 NBT 数据都通过 Minecraft 的原生序列化得以保留。一把带有自定义 lore 和名称的附魔钻石剑会以完全相同的状态返回——附魔、名称、lore、耐久度,全部都在。
销售税的钱去了哪里?
没有。它被移出流通。这是故意的设计选择。可配置的税收作为一种资金回收机制,防止拥有活跃经济的服务器上出现通货膨胀。如果你不想要税收,将其设置为 0 即可。
如果在保存过程中服务器崩溃会怎样?
自动保存每 5 分钟运行一次。在最坏情况的崩溃中,你最多会丢失 5 分钟的交易记录。JSON 文件以原子方式写入——部分写入不会损坏文件。你将拥有上一次干净的存档。
我可以手动编辑 JSON 文件吗?
可以。格式是可读的。你可以在任何文本编辑器中打开 economy.json 并更改余额。你可以打开 auctions.json 并移除有问题的上架记录。先停止服务器,编辑,然后重启。插件在加载时会验证 JSON 并优雅地处理格式错误的条目。
这能在 Folia 上运行吗?
未在 Folia 上进行过测试。该插件使用的是标准的 Bukkit 调度机制。如果你正在使用 Folia,请在上线生产环境之前,先在测试服务器上验证其兼容性。
服务器能处理多少上架列表?
我们已测试在拥有 10,000 个活跃上架列表的情况下,对 TPS(每秒刻数)没有可测量的影响。
GUI 每页显示 28 个项目并支持分页。搜索和过滤操作是对列表数组进行 O(n) 复杂度运算——对于任何合理的服务器规模来说都绰绰有余。如果你不幸拥有超过 100,000 个上架列表,那么你需要一个基于数据库的解决方案。但对于 99% 的服务器来说,纯 JSON 文件存储已经完美无缺。
玩家对 GUI 感到困惑。我该如何帮助他们?
GUI 使用标准的 Minecraft 物品图标以及描述性名称。大多数玩家在 30 秒内就能理解分类按钮和分页功能。
为了保险起见,你可以在出生点附近设置一个传送点告示牌或 NPC,上面写着“输入 /ah 购买和出售物品”。这基本上就是大多数玩家需要的全部说明。
我可以更改 GUI 布局或大小吗?
当前版本不支持。6 行箱子界面(54 个槽位,28 个上架列表 + 控制按钮)是硬编码的。自定义 GUI 布局已在开发路线图中。
为什么会有这个插件
我运营 Minecraft 服务器多年。每次搭建拍卖行插件时,流程总是如出一辙:安装 Vault,安装经济插件,配置经济插件,确保拍卖行能正确对接 Vault,修复其中一个更新后出现的版本不匹配问题,配置一堆我根本不在乎的 40 个 YAML 选项,然后才轮到玩家上架物品。
有一半的时候,更新会导致某些东西崩溃。经济插件更改了其 API,Vault 有了新版本,拍卖行插件不再识别余额。我花在调试依赖链上的时间比实际运行服务器的时间还要多。
我想构建一个这样的东西:整个安装过程只需将一个文件放入文件夹,重启,完成。玩家输入 /ah 即可开始交易。无需依赖链。首日使用无需任何配置。不会因为某个插件更新而导致其他部分出错。
BidVault 正是为此而生。它只做一件事——拥有独立经济系统的玩家拍卖行,并且不需要你先安装任何其他东西。
开发路线图
未来版本正在开发中的功能:
- 自定义 GUI 布局配置
- 大型网络支持的 SQLite/MySQL 存储选项
- 求购订单(玩家发布“以 Y 价格寻找 X”)
- 上架时长分级(1小时、6小时、24小时、48小时、7天——均可配置)
- 管理员拍卖系统(服务器来源的上架列表)
- Vault 经济桥接(可选——允许 BidVault 作为其他插件的经济源)
- 管理员统计仪表板(总交易量、顶级卖家、价格趋势)
暂无预计发布时间(ETA)。功能会在完善后上线。如果你有特定需求,请提交 GitHub Issue——路线图由用户的实际需求驱动。
支持
- Bug 反馈:在 Discord 上开设工单,提供你的服务器版本、插件版本、复现步骤以及相关控制台输出
- 提问:在 Discord 讨论区发帖
- 评价:如果 BidVault 帮你摆脱了依赖地狱,在这里留个好评是帮助其他服务器管理员发现它的最佳方式
专为那些宁愿花时间在世界上折腾,也不愿折腾 plugins 文件夹的服务器管理员打造。
BidVault
A Player Auction House That Actually Works Out of the Box
Most auction house plugins need Vault. They need an economy plugin. They
need a database. They need a half-hour of config before a single player
can list an item. And then when something updates, half the dependencies
break.
BidVault needs a .jar file.
Drop it in your plugins folder. Restart the server. Type /ah. You now
have a working auction house with its own economy, its own currency, its
own GUI, its own search system. No Vault. No EssentialsX Economy. No
database setup. No external economy plugin at all.
Players list items. Other players buy them. Money moves. Everything is
stored in JSON files that you can read, edit, and back up with a text
editor. That's it.
If you WANT to use Vault later, you can — BidVault's economy is designed
to be swappable. But you don't need it to start.
What Your Players Experience
Listing an Item
Player holds the item they want to sell. Types /ahsell 500. The item
disappears from their hand and appears in the auction house. Done.
That's the whole flow. No signs to click. No chest shops to build. No
commands to memorize beyond one. Hold item, type price, done.
If a player lists something by accident or changes their mind, they can
pull it back from their personal listings screen. The item goes to their
collection box.
Buying an Item
Player types /ah. A chest GUI opens showing 28 listings per page with
full pagination at the bottom. They click an item, see all its details —
name, enchantments, lore, seller, price, time remaining — and hit the
green confirmation glass to buy.
The confirmation screen exists for one reason: misclicks. Nobody wants to
accidentally spend 50,000 coins on a dirt block because they
double-clicked. The extra click takes half a second and saves a support
ticket.
When someone buys an item:
- The buyer gets the item instantly
- The seller gets the money minus the configurable sales tax
- The seller gets a real-time notification (chat + sound) if they're online
- If the seller is offline, the money sits in their balance for when they
log back in
The Collection Box
Expired listings, sold items (if a deposit mechanism is added later), and
cancelled listings all go to a personal collection box. Open it with
/ahcollect. Items sit there until the player picks them up.
This prevents the "I lost my item because the listing expired" problem
that plagues plugins with hard-delete expiration. Nothing gets deleted.
It gets collected.
Searching and Filtering
This is where BidVault earns its keep over simpler shop plugins.
9 item categories:
- All
- Weapons (swords, axes, tridents, bows, crossbows)
- Armor (helmets, chestplates, leggings, boots, shields)
- Tools (pickaxes, shovels, hoes, shears, fishing rods)
- Blocks (all placeable blocks)
- Food (edible items)
- Potions (potions, splash potions, lingering potions)
- Enchanted (any item with enchantments)
- Miscellaneous (everything else)
6 sorting modes:
- Newest first
- Oldest first
- Price low to high
- Price high to low
- Name A to Z
- Name Z to A
Live search:
Type /ahsearch diamond sword and the GUI filters to matching listings
in real time. Search works within the current category filter, so a player
can select "Weapons," then search "sharpness" to find all Sharpness swords.
Search clears automatically when the GUI closes so the next player who
opens the auction house starts fresh. Configurable — you can disable this
if your server prefers persistent search.
The category buttons, sort buttons, and pagination controls are all
baked into the GUI. Players figure it out without reading anything. The
interface explains itself through icons and item labels.
The Built-in Economy
BidVault ships with its own economy system. Here's what it handles:
- Starting balance: Configurable. New players get money automatically
when they first interact with the economy.
- Player-to-player payments:
/pay <player> <amount> — direct transfers
- Balance checking:
/balance for yourself, /balance <player> for others
- Admin economy control:
/eco set|give|take <player> <amount> for
full balance management
- Sales tax: Configurable percentage taken from every sale. The tax
amount goes nowhere — it's removed from circulation. Built-in money sink.
- Price bounds: Set minimum and maximum listing prices to prevent
abuse (0-cost listings, trillion-dollar scams)
All balances persist across server restarts in economy.json. The file
format is plain JSON — you can read it, script against it, or migrate
data manually if needed.
If you already have Vault + an economy plugin running, BidVault can
integrate through Vault as well. But the point is that you don't NEED
Vault. Most small-to-medium servers don't need the complexity. BidVault
keeps things self-contained.
Performance & Architecture
Everything is server-side. No client mods. No resource packs. No packets
being injected or modified. BidVault works entirely through the Bukkit
event API and standard inventory GUIs.
Data storage: Flat JSON files in the plugin's data folder.
auctions.json — all active listings and collection boxes
economy.json — all player balances
Items are serialized using Minecraft's native NBT serialization. This
means every piece of item data is preserved: enchantments, custom names,
lore text, item damage, unbreakable flags, custom model data, skull
textures, banner patterns — everything. An item listed on the auction
house comes back exactly as it was.
Auto-save runs every 5 minutes. Data is also flushed to disk on server
shutdown (Bukkit shutdown hook). On a 200-player server, the JSON files
stay small and parse fast.
GUI performance: The chest-based GUI uses standard Bukkit inventory
events. No tick-based refresh loops, no scheduled inventory updates.
Clicks are handled synchronously on the event thread. The pagination and
filtering logic runs in constant time per interaction. You won't see TPS
drops from this plugin on any reasonable server hardware.
Configuration
Everything in one file. Generated on first launch with sane defaults.
Here's what you can change:
# Economy
currency-symbol: "$"
starting-balance: 5000.0
# Listings
max-listings-per-player: 10
min-price: 1.0
max-price: 1000000000.0
default-duration-hours: 48
sales-tax: 5.0
# Expiration
expiration-check-interval-minutes: 5
# Search
clear-search-on-close: true
# Feedback
enable-sounds: true
enable-actionbar-messages: true
That's the entire config. Every line is self-explanatory. No nested YAML
mazes. No obscure section headers. No "set this to true but only if
section-b is false and world-name matches regex." Just the settings you
actually want to change.
Reload without restarting: /ahreload
Commands
Player Commands
| Command |
Description |
Permission |
/ah |
Open the auction house GUI |
auctionhouse.use |
/ahsell <price> |
List held item at the given price |
auctionhouse.sell |
/ahsearch <query> |
Search listings by item name |
auctionhouse.use |
/ahcollect |
Open your collection box |
auctionhouse.use |
/ahmylistings |
View and manage your active listings |
auctionhouse.sell |
/balance |
Check your balance |
Everyone |
/balance <player> |
Check another player's balance |
Everyone |
/pay <player> <amount> |
Transfer money to another player |
Everyone |
Admin Commands
| Command |
Description |
Permission |
/ahreload |
Reload the configuration file |
auctionhouse.admin |
/eco set <player> <amount> |
Set a player's balance |
auctionhouse.admin |
/eco give <player> <amount> |
Add to a player's balance |
auctionhouse.admin |
/eco take <player> <amount> |
Remove from a player's balance |
auctionhouse.admin |
Command aliases for convenience:
/ah, /hdv, /auction — all open the auction house
/bal, /money — balance shortcuts
/sell, /ahlist — listing shortcuts
Every command has full tab completion for arguments and player names.
Permissions
| Permission |
Default |
What It Grants |
auctionhouse.use |
Everyone |
Open the auction house, search, browse, buy, collect |
auctionhouse.sell |
Everyone |
List items for sale, manage own listings |
auctionhouse.admin |
OP |
Reload config, manage player balances via /eco |
The permission model is intentionally simple. Three nodes. No inheritance
trees. No context-dependent permissions. Set it up in 30 seconds with
LuckPerms or whatever permission manager you use.
Installation
- Download
BidVault.jar from this page
- Place it in your server's
/plugins/ folder
- Start (or restart) the server
- That's it
The plugin generates its config and data files on first startup. No
pre-configuration required. Players can start listing items immediately.
No Vault. No database. No external economy plugin. No additional
dependencies.
Requirements
- Server software: Paper 1.21.x, Spigot 1.21.x, or compatible fork
- Java: 17+
- External dependencies: None. Literally none.
Optional: Vault (if you want to bridge BidVault's economy with other
plugins that use Vault's economy API). But it is not required for any
core functionality.
FAQ
Why no Vault dependency?
Because most servers under 50 players don't need Vault. They need an
auction house that works after dragging one file into a folder. Vault
adds a dependency chain — you need Vault, then you need an economy
plugin, then you need to make sure the versions are compatible, then
something updates and breaks. BidVault cuts all of that out for the
common case. If you DO use Vault, BidVault can hook into it. But it's
optional.
What happens when a listing expires?
The item moves to the seller's collection box. It is never deleted.
The seller opens /ahcollect and retrieves it. No item loss, ever.
Can players list enchanted items / named items / items with lore?
Yes. Every piece of NBT data is preserved through Minecraft's native
serialization. An enchanted diamond sword with custom lore and a name
comes back exactly as it was — enchantments, name, lore, damage, all of it.
Does the sales tax money go somewhere?
No. It's removed from circulation. This is an intentional design choice.
A configurable tax acts as a money sink that prevents inflation on
servers with active economies. If you don't want a tax, set it to 0.
What happens if the server crashes mid-save?
The auto-save runs every 5 minutes. In a worst-case crash, you lose up
to 5 minutes of transactions. The JSON files are written atomically —
a partial write won't corrupt the file. You'll have the last clean save.
Can I edit the JSON files manually?
Yes. The format is readable. You can open economy.json in any text
editor and change balances. You can open auctions.json and remove
problematic listings. Stop the server first, edit, restart. The plugin
validates JSON on load and handles malformed entries gracefully.
Does this work with Folia?
Not tested on Folia. The plugin uses standard Bukkit scheduling. If
you're on Folia, test it on a staging server first before going to
production.
How many listings can the server handle?
We've tested with 10,000 active listings without measurable TPS impact.
The GUI shows 28 per page with pagination. The search and filter
operations are O(n) over the listings array — fine for any realistic
server size. If you somehow have 100,000+ listings, you'd want a
database-backed solution. For 99% of servers, flat JSON is perfect.
Players are confused by the GUI. How do I help them?
The GUI uses standard Minecraft item icons with descriptive names. Most
players figure out the category buttons and pagination within 30 seconds.
If you want to be safe, set up a warp sign or NPC near spawn that says
"Type /ah to buy and sell items." That's all the explanation most
players need.
Can I change the GUI layout or size?
Not in the current version. The 6-row chest (54 slots, 28 listings +
controls) is hardcoded. Custom GUI layouts are on the roadmap.
Why This Plugin Exists
I've run Minecraft servers for years. Every time I set up an auction
house plugin, the process was the same: install Vault, install an
economy plugin, configure the economy plugin, make sure the auction
house talks to Vault correctly, fix the version mismatch when one
updates, configure 40 YAML options I don't care about, and THEN
players can list items.
Half the time, something broke on update. The economy plugin changed
its API. Vault had a new version. The auction house plugin stopped
recognizing balances. I'd spend more time debugging dependency chains
than actually running the server.
I wanted to build something where the entire installation is: put one
file in a folder, restart, done. Players type /ah and start trading.
No dependency chain. No configuration required for day-one usage.
No moving parts that can break when one plugin updates.
BidVault is that. It does one thing — player auction house with its
own economy — and it does it without asking you to install anything
else first.
Roadmap
Things being worked on for future versions:
- Custom GUI layout configuration
- SQLite/MySQL storage option for large networks
- Buy orders (player posts "looking for X at Y price")
- Listing duration tiers (1h, 6h, 24h, 48h, 7d — all configurable)
- Admin auction system (server-sourced listings)
- Vault economy bridge (optional — so BidVault can be the economy
source for other plugins)
- Statistics dashboard for admins (total volume, top sellers,
price trends)
No ETAs. Features ship when they work. If you want something specific,
open a GitHub issue — the roadmap is driven by what people actually ask
for.
Support
- Bugs: Open a Discord ticket with your server version, plugin version,
steps to reproduce, and any relevant console output
- Questions: open a Discord discussion
- Reviews: If BidVault saved you from dependency hell, a review here
is the single best thing you can do to help other server admins find it
Built for server admins who'd rather spend time on their world than on
their plugins folder.
评论 0
登录后参与评分
还没有评论,来抢沙发吧