RewardCore
三个奖励系统,让玩家流连忘返——只需一个插件,无需安装其他任何东西。
RewardCore 为 Paper 服务器整合了每日登录奖励、宝箱和投票奖励。它没有任何运行时依赖:不需要 Vault、不需要经济插件、不需要权限插件、不需要数据库,也不需要 NuVotifier。所有配置都使用可读的 YAML 文件进行设置,且玩家看到的所有文本均内置英文和荷兰文。
? 每日登录奖励
一个重复的奖励周期,玩家每天通过 /daily 领取一次。
- 连续签到(Streaks) — 连续天数领取会建立连续记录;错过一天则重置。
- 宽限天数 — 可选地原谅一或两天未领取的情况,这样即使有一周表现不佳,也不会毁掉长达 60 天的连续记录。
- 里程碑奖励 — 每连续 7 天、30 天或任意指定天数,在正常每日奖励之外额外发放奖励。
- 日历菜单 — 显示周期中每一天的内容(如“3-8x 钻石”、“+100 XP”、“1x 每日钥匙”)、当前/最佳连续记录,以及距离下次领取的实时倒计时。
- 加入提醒 — 一条可配置的延迟消息,告知玩家他们的奖励正在等待领取。
- 该周期无限循环,且更改其长度永远不会重置任何人的连续记录。
? 宝箱
通过账户绑定的钥匙开启的加权奖励宝箱。
- 钥匙不会丢失 — 它们是账户上的计数器,而非物品。死亡不会掉落它们,熔岩中不会丢失它们,不存在复制漏洞,也没有诈骗风险。
- 公开概率 — 预览屏幕显示每个奖励的确切百分比,数据取自与抽奖相同的表格。没有隐藏此信息的选项。
- 稀有度等级 — 根据稀有度分级显示颜色,并可选择发送全服公告(例如“Steve 刚刚抽到了鞘翅!”)。包含五个预设等级;你也可以添加自己的等级。
- 开启动画 — 一段简短的旋转卷轴。结果在开始之前就已确定,因此关闭窗口的玩家仍会获得奖品,而在旋转过程中断连则会退还钥匙。
- 免费钥匙计时器 — 针对每个宝箱单独设置,例如每 24 小时或每周赠送一把免费钥匙。
- 实体宝箱 — 使用
/crate setblock <crate> 绑定任意方块;右键点击打开,左键点击预览。上方会出现浮动标签,方块受到保护防止被破坏,且永远不会留下孤立的实体。
- 仅限特定等级的宝箱 — 你可以为任何宝箱分配你想要的权限节点。
- 钥匙可以授予离线玩家,因此像
crate givekey {player} vote 1 这样的网页商店命令可以直接生效。
?️ 投票奖励
奖励服务器列表的投票——插件内置了一个 Votifier 服务器。
- 无需 NuVotifier。 RewardCore 运行自己的 Votifier v1/RSA 监听器,在首次启动时生成密钥对,并通过
/vote key 将公钥交给你。
- 已经在使用 NuVotifier? 保留它:RewardCore 可以使用相同的配置来奖励该插件接收到的投票。
- 投票连胜 — 一个滚动窗口(默认为 48 小时),即使投票时间相差几小时也能保持连贯,每 N 次连续投票可获得额外奖励。
- 不惩罚离线投票者 — 宝箱钥匙和指令奖励立即生效;物品和经验值会被保存并在其下次登录时交付。
- 投票派对 — 每次投票都计入共同目标,奖励所有在线玩家,并有进度公告(例如“还差 12 票!”)。
/vote 中的可点击投票链接,以及每位玩家的总投票数和连胜记录。
/vote test 模拟真实投票的代码路径,以便你在调整防火墙之前验证奖励是否正常工作。
统一的所有奖励格式
每日奖励、宝箱奖品、投票 payout 和投票派对均使用相同的结构。只需学习一次:
give:
items:
- type: DIAMOND
min: 1
max: 3
xp: 100
levels: 0
keys:
vote: 1
commands:
- 'eco give {player} 500'
messages:
- '&aThanks for voting, {player}!'
控制台命令是有意设计的备用方案。与其依赖某一个经济或权限插件,任何奖励都可以执行命令——因此 RewardCore 兼容 EssentialsX、CMI、LuckPerms 或你已运行的任何其他插件:
commands:
- 'eco give {player} 2500' # 任意经济插件
- 'lp user {player} parent addtemp vip 7d' # 作为宝箱奖品的 VIP 一周权限
物品支持数量范围、自定义名称、描述文本、附魔以及虚假发光效果。溢出部分会掉落在玩家脚下,而不会消失。
命令
| 命令 |
别名 |
描述 |
/daily |
dailyreward, dailyrewards |
打开奖励日历 |
/daily claim | streak |
|
领取今日奖励 · 查看你的连续记录 |
/crate |
crates, key, keys |
打开宝箱菜单 |
/crate keys | preview <crate> | open <crate> | claim |
|
查看钥匙 · 概率 · 开启 · 免费钥匙 |
/vote |
votes, voting |
投票链接、你的统计数据、派对进度 |
/rewardcore status | reload |
rc, rewards |
模块状态 · 重新加载所有内容 |
管理员: /crate givekey|takekey|setblock|removeblock|reload, /daily reset|reload,
/vote test|key|reload. 所有命令均支持自动补全。
权限
| 节点 |
默认值 |
控制内容 |
rewardcore.daily.use |
所有人 |
/daily 及领取功能 |
rewardcore.crate.use |
所有人 |
/crate、开启、预览 |
rewardcore.vote.use |
所有人 |
/vote |
rewardcore.admin |
op |
/rewardcore |
rewardcore.daily.admin · rewardcore.crate.admin · rewardcore.vote.admin |
op |
管理员子命令 |
rewardcore.lang.<code> |
关闭 |
强制为某个组别设置语言 |
宝箱访问权限使用你在 crates.yml 中编写的任何节点,因此绝不会与你的现有设置冲突。
模块化设计
每个功能都是一个模块,你可以在 config.yml 中将其关闭:
modules:
crates:
enabled: true
daily:
enabled: true
vote:
enabled: false # 此服务器不使用投票列表
已禁用的模组不会注册任何命令、监听器或任务——其数据会被保留,因此重新启用后,所有连续记录、密钥和投票计数都会恢复。模组之间仅可选引用:如果禁用木箱功能,其他地方的密钥奖励将被跳过,并在控制台发出警告,而不会导致崩溃。
开箱即用的双语支持
所有面向玩家显示的文本均位于 lang/messages_en.yml 和 lang/messages_nl.yml 中——包括菜单标题、物品名称、描述、聊天内容,甚至 d/h/m/s 倒计时后缀。没有任何硬编码文本。玩家的语言优先通过 rewardcore.lang.<code> 权限确定,其次是客户机本地设置,最后是默认语言。添加第三种语言只需复制一个文件并翻译其中的值即可。
安装
- 将 jar 文件放入
plugins/ 目录。
- 启动服务器。
- 编辑
daily-rewards.yml、crates.yml 以及 config.yml 中的 vote: 部分。
- 执行
/rewardcore reload。
对于投票功能,请打开 TCP 端口 8192,运行 /vote key,并将生成的密钥粘贴至你的投票网站。
兼容性
|
|
| 服务端 |
Paper 1.21+(及其分支:Purpur、Pufferfish)。不支持 Spigot。 |
| Java |
21 或更高版本 |
| 客户端 |
仅限服务端 —— 玩家无需安装模组 |
| Folia |
不支持 |
| 依赖项 |
无 |
| 存储方式 |
扁平化 YAML 格式,可直接打开阅读 |
数据文件
daily-data.yml(连续记录)· crate-data.yml(密钥与计时器)· vote-data.yml(投票、派对计数器、待处理的离线奖励)· crate-blocks.yml(实体木箱)。请将它们随世界一起备份;插件在更新时绝不会覆盖你的配置文件。
常见问题
我需要经济类插件吗? 不需要。使用控制台命令发放奖励金币即可兼容任何经济系统。
木箱密钥是玩家可交易物品吗? 不是——它们是绑定账号的,这也正是它们无法被复制或丢失的原因。
我需要 NuVotifier 吗? 不需要,监听器已内置。如果你已经安装了它,RewardCore 也可以使用其提供的投票数据。
如果玩家在离线状态下投票怎么办? 密钥和命令会立即生效;物品和经验将在他们下次登录时自动送达。
我可以隐藏木箱概率吗? 不行。展示概率是一个有意为之的设计决策——玩家可以检查的木箱更能赢得信任,且多个司法管辖区要求公开披露这些信息。
它在 Spigot 上能用吗? 不能。请使用 Paper 或其分支。
RewardCore
Three reward systems that keep players coming back — in one plugin, with nothing else to install.
RewardCore bundles daily login rewards, crates, and vote rewards for Paper servers. There are no
runtime dependencies at all: no Vault, no economy plugin, no permissions plugin, no database, and
no NuVotifier. Everything is configured in YAML you can read, and every word a player sees ships
in English and Dutch.
? Daily login rewards
A repeating reward cycle players claim once per day with /daily.
- Streaks — claiming on consecutive days builds a streak; missing a day resets it.
- Grace days — optionally forgive one or two missed days, so a single bad week does not
destroy a 60-day run.
- Milestone bonuses — an extra reward every 7, 30, or any number of days in a row, paid on
top of the normal daily reward.
- Calendar menu — every day of the cycle with its contents in plain words ("3-8x Diamond",
"+100 XP", "1x daily key"), the current/best streak, and a live countdown to the next claim.
- Join reminder — a configurable, delayed message telling players their reward is waiting.
- The cycle repeats forever, and changing its length never resets anyone's streak.
? Crates
Weighted reward crates opened with account-bound keys.
- Keys cannot be lost — they are counters on the account, not items. No dropping them on
death, no losing them in lava, no duplication exploits, no scams.
- Public odds — a preview screen shows the exact percentage of every reward, taken from the
same table the roll uses. There is no setting to hide it.
- Rarity tiers — colour and optional server-wide announcements per tier ("Steve just won an
Elytra!"). Five tiers included; add your own.
- Opening animation — a short spinning reel. The outcome is decided before it starts, so a
player who closes the window still gets the prize, and a disconnect mid-spin refunds the key.
- Free-key timers — per crate, e.g. one free key every 24 hours or once a week.
- Physical crates — bind any block with
/crate setblock <crate>; right-click opens,
left-click previews. A floating label appears above it, the block is protected from breaking,
and no orphan entities are ever left behind.
- Rank-only crates — give a crate any permission node you like.
- Keys can be granted to offline players, so a webstore command like
crate givekey {player} vote 1 just works.
?️ Vote rewards
Reward server-list votes — with a Votifier server built into the plugin.
- No NuVotifier needed. RewardCore runs its own Votifier v1/RSA listener, generates its key
pair on first start, and hands you the public key with
/vote key.
- Already run NuVotifier? Keep it: RewardCore can reward the votes that plugin receives
instead, using the same configuration.
- Vote streaks — a rolling window (48 h by default) that survives an off-by-a-few-hours vote,
with a bonus every N consecutive votes.
- Offline voters are not punished — crate keys and command rewards apply immediately; items
and XP are kept and delivered on their next login.
- Vote party — every vote counts toward a shared goal that rewards everyone online, with
progress announcements ("12 votes to go!").
- Clickable vote links in
/vote, plus each player's totals and streak.
/vote test runs the exact code path a real vote takes, so you can verify rewards before
touching a firewall.
One reward format for everything
Daily rewards, crate prizes, vote payouts, and vote parties all use the same block. Learn it once:
give:
items:
- type: DIAMOND
min: 1
max: 3
xp: 100
levels: 0
keys:
vote: 1
commands:
- 'eco give {player} 500'
messages:
- '&aThanks for voting, {player}!'
Console commands are the deliberate escape hatch. Instead of depending on one economy or
permissions plugin, any reward can run a command — so RewardCore works with EssentialsX, CMI,
LuckPerms, or whatever you already run:
commands:
- 'eco give {player} 2500' # any economy
- 'lp user {player} parent addtemp vip 7d' # a week of VIP as a crate prize
Items support amount ranges, custom names, lore, enchantments, and a fake glow. Overflow drops at
the player's feet instead of vanishing.
Commands
| Command |
Aliases |
Description |
/daily |
dailyreward, dailyrewards |
Open the reward calendar |
/daily claim | streak |
|
Claim today's reward · show your streak |
/crate |
crates, key, keys |
Open the crate menu |
/crate keys | preview <crate> | open <crate> | claim |
|
Keys · odds · open · free key |
/vote |
votes, voting |
Vote links, your stats, party progress |
/rewardcore status | reload |
rc, rewards |
Module status · reload everything |
Admin: /crate givekey|takekey|setblock|removeblock|reload, /daily reset|reload,
/vote test|key|reload. Everything is tab-completed.
Permissions
| Node |
Default |
Controls |
rewardcore.daily.use |
everyone |
/daily and claiming |
rewardcore.crate.use |
everyone |
/crate, opening, previews |
rewardcore.vote.use |
everyone |
/vote |
rewardcore.admin |
op |
/rewardcore |
rewardcore.daily.admin · rewardcore.crate.admin · rewardcore.vote.admin |
op |
Admin subcommands |
rewardcore.lang.<code> |
off |
Force a language for a group |
Crate access uses whatever node you write in crates.yml, so it never clashes with your setup.
Modular by design
Each feature is a module you can switch off in config.yml:
modules:
crates:
enabled: true
daily:
enabled: true
vote:
enabled: false # this server does not use vote lists
A disabled module registers no commands, no listeners, and no tasks — and its data is kept, so
switching it back on restores every streak, key, and vote count. Modules only reference each other
optionally: if you turn crates off, key rewards elsewhere are skipped with a console warning
instead of breaking.
Bilingual out of the box
All player-facing text lives in lang/messages_en.yml and lang/messages_nl.yml — menu titles,
item names, lore, chat, even the d/h/m/s countdown suffixes. Nothing is hardcoded.
A player's language is chosen by a rewardcore.lang.<code> permission, then their own client
locale, then your default. Adding a third language is copying one file and translating the values.
Installation
- Drop the jar in
plugins/.
- Start the server.
- Edit
daily-rewards.yml, crates.yml, and the vote: section of config.yml.
/rewardcore reload.
For votes, open TCP port 8192, run /vote key, and paste the key into your vote sites.
Compatibility
|
|
| Server |
Paper 1.21+ (and forks: Purpur, Pufferfish). Spigot is not supported. |
| Java |
21 or newer |
| Side |
Server only — players need no mod |
| Folia |
Not supported |
| Dependencies |
None |
| Storage |
Flat YAML you can open and read |
Data files
daily-data.yml (streaks) · crate-data.yml (keys and timers) · vote-data.yml (votes, party
counter, pending offline rewards) · crate-blocks.yml (physical crates). Back them up with your
world; the plugin never overwrites your configuration on update.
FAQ
Do I need an economy plugin? No. Reward money with a console command and any economy works.
Are crate keys items players can trade? No — they are account-bound, which is what makes them
impossible to duplicate or lose.
Do I need NuVotifier? No, the listener is built in. If you already run it, RewardCore can use
its votes instead.
What if a player votes while offline? Keys and commands apply straight away; items and XP wait
for their next login and are delivered automatically.
Can I hide the crate odds? No. Showing them is a deliberate design decision — players trust a
crate they can inspect, and several jurisdictions expect disclosure.
Does it work on Spigot? No. Paper or a Paper fork.
评论 0
登录后参与评分
还没有评论,来抢沙发吧