
斗蛐蛐 (Cricket Fight)
把你喜欢的生物请上擂台!看红队与蓝队在封闭战场里正面交锋;挑选原版或模组生物,分配队伍、施加药水强化,然后等着胜负揭晓! Bring your favorite mobs into the arena! Watch red and blue teams clash in a sealed battlefield; choose vanilla or modded creatures, assign teams, apply potion buffs, and see who wins.
1.0.0
Compatibility
Changes
斗蛐蛐 1.0.0
擂台已经搭好,红蓝双方也已就位。欢迎来到《斗蛐蛐》的首个公开版本!
本次内容
- 一键生成 31×11×31 的全封闭红蓝八角擂台。
- 图形化管理生物、队伍和比赛,全程无需使用命令。
- 支持原版生物以及当前服务端安装的模组生物。
- 支持搜索、动态模型预览和大型生物自适应显示。
- 可一次多选多只生物,批量加入红队或蓝队。
- 比赛开始前生物保持和平,开赛后只攻击对方队伍。
- 支持为参赛生物添加持续到死亡的药水效果。
- 自动判断胜负,并让获胜方幸存者恢复至满状态。
- 提供清场令牌与落物清扫器。
- 擂台结构受到保护,避免方块破坏、爆炸、活塞和流体影响比赛。
- 自动生成的擂台名称支持中英文国际化。
- 优化界面字体、生命值、实体朝向及多种显示细节。
Cricket Fight 1.0.0
The arena is ready, and both teams are waiting. Welcome to the first public release of Cricket Fight!
Highlights
- Instantly builds a sealed 31×11×31 red-and-blue octagonal arena.
- Manage mobs, teams, effects, and matches entirely through the GUI.
- Supports vanilla mobs and compatible mobs from installed mods.
- Includes searchable catalogs, animated previews, and automatic large-mob scaling.
- Multi-select mobs and assign entire groups to either team.
- Mobs remain passive before the match and only attack opponents after it begins.
- Apply potion effects that remain active until the affected mob dies.
- Automatically determines the winner and fully restores surviving champions.
- Includes dedicated tools for removing arena mobs and dropped items.
- Protects registered arenas from breaking, explosions, pistons, and fluids.
- Automatically generated arena names follow the player’s selected language.
- Improves interface text, health displays, entity orientation, and overall readability.
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:YEn2DV27:f9rTDNwJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YEn2DV27:f9rTDNwJ"
}
