1.0.0-BETA1
Compatibility
Required content
Changes
新增
团队对抗框架 + 完整开局流程(选队→倒计时→发装备→队色甲→无敌) 双计分模式(击杀人数 / 击杀积分,含爆头/连杀等标签) 复活系统:不重生/有限次/无限次 + 立即重生开关(默认手动点重生)+ 无机会自动旁观 HUD 计时/比分/击杀提示;结算四榜切换(人数/分数/团队击杀/团队积分) OP 面板:自适应不出屏、滚轮+滚动条、底部常驻大「开始游戏」、分组卡片、出生点/复活/总时长设置、作者 B 站按钮 配置落盘持久化(出生点重启不丢)
修复
面板尺寸溢出(顶部/底部被挤出屏幕、开始游戏消失的根因) 滚动方向与盲区 重生后假死/不加载区块(延后重生+区块预载+关死亡界面) 指令失效、单人无权限 击杀提示淡出、控件叠加等 使用方式:客户端+服务端同装 Fabric 1.20.1 + Fabric API;右 Shift 或 /minigame panel 开面板,/minigame start 开局。
New Features
Team-based combat framework with a complete game start process: team selection → countdown → gear distribution → team-colored armor → invincibility.
Dual scoring modes: kill count / kill points, including tags for headshots, streaks, etc.
Respawn system: no respawn / limited / unlimited, plus an instant respawn toggle (default manual click) and auto‑spectate when no chances left.
HUD displaying timer, score, and kill feed; post‑game four leaderboard tabs (players, points, team kills, team points).
OP panel: adaptive sizing that stays on screen, scroll wheel + scrollbar, a large Start Game button permanently at the bottom, group cards, settings for spawn point, respawn, and total duration, and an author's Bilibili button.
Configuration is persisted to disk (spawn point survives server restarts).
Fixes
Fixed panel size overflow (root cause of top/bottom being pushed off screen and the Start Game button disappearing).
Fixed scroll direction and dead zones.
Fixed fake death and chunks not loading after respawn (by delayed respawn + chunk preloading + closing the death screen).
Fixed commands not working and singleplayer permission issues.
Fixed kill feed fade‑out, UI control overlap, and other minor issues.
Usage
Install on both client and server with Fabric 1.20.1 and Fabric API.
Press Right Shift or use /minigame panel to open the panel.
Use /minigame start to start the game.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:68OqXNL4:ovMxxwrH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:68OqXNL4:ovMxxwrH"
}

