? PokePinks — Race for Pinks
为 Cobblemon 打造的“赢家通吃”宝可梦对战。 两位训练家,各派一只宝可梦,一场对决。赢家带走两只宝可梦,输家只带着一段故事离开。
想当年,街头赛车手押上自己的粉红纸片(车钥匙)——赢了比赛,把车开走。PokePinks 也是如此,只不过这里的“车”是一只烈咬陆鲨,而且它确实戴着讲究头带,没错,连头带一起带走。
100% 服务端运行。 原版客户端、模组客户端都没关系——没人需要安装任何东西。把它放到服务器上,晚餐时间你的玩家就开始拿他们最好的朋友打赌了。
✨ 功能列表
- 赢家通吃的 1v1 赌注对战 —— 每位训练家押上一只宝可梦;赢家保留两只,包括携带道具
- 等级匹配的赌注(默认完全匹配,容差可配置),防止老手欺负新手
- 双重确认揭示 —— 在锁定之前,双方完整展示彼此的押注宝可梦;从结构上杜绝欺诈
- 禁止换人、禁止道具 —— 这是设计使然,而非规则限制:你的战斗队伍中恰好只有一只宝可梦
- 防崩溃托管机制 —— 原子化结算配合幂等交付队列;绝不会出现重复或消失的宝可梦
- 断线惩罚系统 —— 退还双方押注,记录一次违规,通知玩家和工作人员;由服主决定处罚,而非模组自动执行
- 永久审计日志 —— 每场战斗都记录完整的宝可梦数据;可通过工作人员 GUI 或控制台文本浏览
- 基于排名的冷却时间 —— 通过权限节点实现(兼容 LuckPerms)
- JSON 或 MariaDB 存储 —— 单服务器零设置,或在整个网络中共享违规/禁令/日志
- 一键分类屏蔽 —— 可针对传说、神话和幻之宝可梦进行一键屏蔽,外加手动物种黑名单
- GUI 可选 —— 提供完整的箱子 GUI 流程,或纯聊天/命令模式以满足特定需求
- 100% 服务端运行 —— 支持原版客户端;玩家无需安装任何内容
⚔️ 对战流程
- 发起挑战。
/pokepinks challenge <player> —— 对方会在聊天栏看到可点击的 [ACCEPT] [DENY] 按钮。公开的挑战让退缩本身就是一种损失。
- 选择押注。 一个简洁的队伍菜单。点击你愿意失去的那只。等级必须与对手的选定相匹配——不允许等级 100 欺负等级 30。
- 双重揭示。 在锁定之前,双方都能看到两只宝可梦的全部信息:物种、等级、闪光状态、携带道具。你清楚自己冒了什么险,也清楚自己能赢得什么。只有当两位训练家都点击确认后才会开始。绝不偷梁换柱。永远不。
- 战斗开始。 纯粹的 1v1。无法换人——你的战斗队伍里 literally(字面上)只有一只宝可梦,所以根本没有东西可以换 到。没有背包,没有第二次机会。只有你、你的宝可梦和你的选择。
- 赢家通吃。 奖品直接加入胜者的队伍(如果队伍已满则放入电脑),包含携带道具。败者会收到一条广播,向全服宣布其战败。这就是 PokePinks,宝贝。
平局?两只宝可梦都回家。爆炸镜像对战是一场表演,而不是抢劫。
? 你的宝可梦不会因 Bug 丢失——只会输给更优秀的训练家
这是服务器所有者真正关心的部分。一旦双方确认,两只宝可梦都会进入托管状态——在第一招发出之前,它们会从队伍中移除并写入存储。此后:
- 战斗中服务器崩溃? 重启后两只宝可梦会自动返回。
- 数据库在最糟糕的时刻出错? 结算是原子事务配合幂等交付队列——重复和丢失在结构上是不可能的,而不仅仅是概率低。每次移交都会在被视为完成前与实际磁盘数据进行验证。
- 欠债时离线? 下次登录时交付,并附带解释说明。
- 战斗无法开始? 托管立即解除。没有人会因为技术细节而损失任何东西。
默认情况下,奖品以战前的满血状态到达。翻转一个配置开关 (battleOnClones: false),它会以战斗结束时的状态到达——濒死、伤痕累累、谦卑。你的服务器,你的规则。
? 愤怒退出的玩家得到的是记录,而不是豁免权
拔掉网线并不能拯救你的宝可梦——但一次连接断开也不会让你失去它。
- 任何中途断线 = 双方押注退还。真实的网络问题确实存在。
- 每次断线也会记录一次违规:断线者会收到通知,对手会收到通知,在线的工作人员会被提醒。
- 无自动封禁。 违规是收据,不是判决。工作人员可以看到模式并做出决定——对习惯性拔线的玩家使用
/pokepinks ban,对 ISP 确实很烂的训练家使用 /pokepinks pardon。
? 工作人员一览无余
每场已解决的战斗都会永久记录:双方玩家、两只宝可梦(摘要和完整序列化数据)、结果、胜者、时间戳、服务器。有人大喊“诈骗”?输入 /pokepinks log <player>,点击条目,三十秒结案。可在分页 GUI 中浏览(带有实际的宝可梦图标),或通过控制台查看纯文本。
⚙️ 适用于从单人多人游戏 (SMP) 到大型网络的任何场景
- 零设置 JSON 存储 用于单服务器——原子写入,开箱即用的防崩溃保护。
- MariaDB 模式 用于网络——禁令、违规、冷却时间和统一的审计日志在所有后端共享。在一台服务器上愤怒退出,你的记录会跟随你到下一台服务器。
- 基于排名的冷却时间 通过权限节点实现(兼容 LuckPerms)——让你的冠军每 5 分钟可以重赛,而其他人在一小时内冷却。
- 一切皆可配置: 等级匹配容差、物种黑名单、传说/神话/幻之宝可梦的一键屏蔽、队伍同步设置的加入交付延迟、GUI 或纯聊天模式、广播开关、权限命名空间。
- 优雅降级: 如果启动时数据库不可用,PokePinks 会禁用自身并告知你——你的服务器继续运行。
⌨️ 命令
用于训练师
| 指令 |
功能 |
/pokepinks challenge <player> |
发起挑战 — 竞速争夺粉钻 |
/pokepinks accept / deny |
接受或拒绝挑战 |
/pokepinks stake <1-6> |
通过队伍槽位选择赌注(无 GUI 模式) |
/pokepinks confirm |
确认并锁定你的赌注(无 GUI 模式) |
/pokepinks cancel |
在战斗开始前随时取消 |
用于工作人员 (pokepinks.staff)
| 指令 |
功能 |
/pokepinks log [player] [page] |
浏览审计日志 — 游戏内图标 GUI,控制台输出文本 |
/pokepinks strikes <player> |
查看玩家的断线违规记录 |
/pokepinks pardon <player> |
清除某人的违规记录(申诉时适用) |
/pokepinks ban <player> / unban <player> |
禁止玩家参与 PokePinks(仅针对该模组的封禁,非服务器封禁) |
/pokepinks reload |
重新加载配置文件 — 同时尝试重连失败的数据库连接 |
? 安装方法
下载 jar 文件,将其放入服务器的 mods/ 文件夹中,然后重启。就这么简单 — 首次运行时会自动生成配置文件 config/pokepinks.json,JSON 存储开箱即用,无需额外设置。客户端无需安装任何内容。
依赖: Fabric 1.21.1 · Cobblemon 1.7+ · Fabric API · Fabric Language Kotlin。仅限服务端。
放手一搏,愿它足以制胜。 ?
? PokePinks — Race for Pinks
Winner-takes-all Pokemon battles for Cobblemon. Two trainers. One Pokemon each. One battle. The winner walks away with both Pokemon. The loser walks away with a story.
Back in the day, street racers bet their pink slips — win the race, take the car. PokePinks is that, except the car is a Garchomp, and yes, it's holding a Choice Scarf, and yes, the scarf comes with it.
100% server-side. Vanilla clients, modded clients, doesn't matter — nobody installs anything. Drop it on the server and your players are betting their best friends by dinner.
✨ Feature set
- Winner-takes-all 1v1 stake battles — each trainer wagers one Pokemon; the winner keeps both, held items included
- Level-matched stakes (exact match by default, tolerance configurable) so nobody bullies a rookie
- Double-reveal confirmation — both stakes shown in full to both players before anything locks; scams are structurally impossible
- No switching, no items — enforced by design, not by rules: your battle party contains exactly one Pokemon
- Crash-proof escrow — atomic settlement with an idempotent delivery queue; no dupes, no vanishing mons, ever
- Disconnect strike system — refund both, record the strike, notify player + staff; owners decide punishments, never the mod
- Permanent audit log — every battle recorded with full Pokemon data; browsable staff GUI or console text
- Rank-based cooldowns via permission nodes (LuckPerms-friendly)
- JSON or MariaDB storage — zero-setup single server, or shared strikes/bans/logs across a whole network
- One-toggle category blocks for legendaries, mythicals, and ultra beasts, plus a manual species blacklist
- GUI-optional — full chest-GUI flow, or pure chat/command mode for setups that need it
- 100% server-side — vanilla clients work; nothing to install for players
⚔️ How it goes down
- The callout.
/pokepinks challenge <player> — they get a clickable [ACCEPT] [DENY] right in chat. Public enough that backing out is its own kind of loss.
- Pick your stake. A clean menu of your party. Click the one you're willing to lose. Levels must match your opponent's pick — no level 100 bullying a level 30.
- The double-reveal. Before anything is locked, both players see BOTH Pokemon in full: species, level, shiny status, held item. You know exactly what you're risking and exactly what you're winning. Nothing starts until both trainers hit confirm. No bait-and-switch. Ever.
- The battle. A pure 1v1. No switching — your battle party literally contains one Pokemon, so there's nothing to switch to. No bag, no second chances. Just you, your mon, and your choices.
- Winner takes all. The prize goes straight to the winner's party (or PC if it's full), held item included. The loser gets a broadcast announcing their defeat to the whole server. That's pinks, baby.
Draws? Both Pokemon go home. Explosion mirror matches are a spectacle, not a robbery.
? Your Pokemon can't be lost to a bug — only to a better trainer
This is the part server owners actually care about. The moment both players confirm, both Pokemon enter escrow — pulled from the parties and written to storage before the first move is made. From there:
- Server crashes mid-battle? Both Pokemon come home automatically on restart.
- Database hiccups at the worst possible millisecond? Settlement is one atomic transaction with an idempotent delivery queue — duplication and loss are structurally impossible, not just unlikely. Every hand-off is verified against what's actually on disk before it's considered done.
- Offline when you're owed a mon? It's delivered next login, with a note explaining why.
- Battle can't start? Escrow unwinds instantly. Nobody loses anything to a technicality.
By default the prize arrives at full pre-battle health. Flip one config toggle (battleOnClones: false) and it arrives exactly how the fight left it — fainted, scratched, humbled. Your server, your rules.
? Rage-quitters get a file, not a free pass
Pulling the plug doesn't save your Pokemon — but one dropped connection doesn't cost you one, either.
- Any mid-battle disconnect = both stakes refunded. Real internet problems happen.
- Every disconnect also records a strike: the disconnector is told, the opponent is told, and online staff get pinged.
- No auto-bans. Strikes are receipts, not sentences. Staff see the pattern and decide —
/pokepinks ban for the serial cord-puller, /pokepinks pardon for the trainer whose ISP actually is that bad.
? Staff see everything
Every resolved battle is permanently logged: both players, both Pokemon (summary AND full serialized data), outcome, winner, timestamp, server. Someone cries "scam"? /pokepinks log <player>, click the entry, case closed in thirty seconds. Browsable in a paginated GUI with actual Pokemon icons, or plain text from console.
⚙️ Built for anything from an SMP to a network
- Zero-setup JSON storage for single servers — atomic writes, crash-safe out of the box.
- MariaDB mode for networks — bans, strikes, cooldowns, and one unified audit log shared across every backend. Rage-quit on one server, your record follows you to the next.
- Rank-based cooldowns via permission nodes (LuckPerms-friendly) — let your champions run it back every 5 minutes while everyone else cools off for an hour.
- Configurable everything: level-match tolerance, species blacklist, one-toggle blocks for legendaries/mythicals/ultra beasts, join-delivery delay for party-sync setups, GUI or pure-chat mode, broadcast toggles, permission namespace.
- Degrades gracefully: if the database is down at boot, PokePinks disables itself and says so — your server keeps running.
⌨️ Commands
For trainers
| Command |
What it does |
/pokepinks challenge <player> |
Call someone out — race for pinks |
/pokepinks accept / deny |
Answer a challenge |
/pokepinks stake <1-6> |
Pick your stake by party slot (GUI-less mode) |
/pokepinks confirm |
Lock in your stake (GUI-less mode) |
/pokepinks cancel |
Back out any time before the battle starts |
For staff (pokepinks.staff)
| Command |
What it does |
/pokepinks log [player] [page] |
Browse the audit log — icon GUI in-game, text from console |
/pokepinks strikes <player> |
Check a player's disconnect strikes |
/pokepinks pardon <player> |
Wipe someone's strikes (appeals happen) |
/pokepinks ban <player> / unban <player> |
Bar a player from PokePinks (the mod's ban, not a server ban) |
/pokepinks reload |
Reload the config — also retries a downed database connection |
? Installation
Download the jar, drop it in your server's mods/ folder, restart. That's it — the config generates itself on first run at config/pokepinks.json, and JSON storage works out of the box with zero setup. Clients need nothing installed.
Requires: Fabric 1.21.1 · Cobblemon 1.7+ · Fabric API · Fabric Language Kotlin. Server-side only.
Run what you brung, and hope it's enough. ?
评论 0
登录后参与评分
还没有评论,来抢沙发吧