2.3.0
Compatibility
Changes
2.3 is came!I add two new items in the game for new game version!And I made the OP more OP in the sever with Gost.
Look at the vedio to check the news in 👉2.3.0👈
点击看中文
1.新增道具「冲刺矛」&「漂浮药水」
「冲刺矛」:物品ID为金矛(GOLDEN_SPEAR),左键使用可进行一次原版矛的冲刺效果,使用后即刻消失。 (该道具仅在服务器版本 ≥ 1.21.4 时可用,插件启动时自动检测服务器版本并给出反馈。)
「漂浮药水」:物品ID为滞留药水(LINGERING_POTION),右键使用获得漂浮效果 4.5 秒。
2.新增管理员单人测试模式(/gostadmin testmode)
管理员可单人强制开局,对局不会因人数不足而结束,道具正常发放,方便管理员/服主单人测试本插件(可以在对局中使用道具检验你设计的地图是否合理)。
3.新增管理员指令 /gostadmin giveitem <道具名>
现在管理员可以使用 /gostadmin giveitem <道具名> 直接获得道具,支持模糊匹配(比如 肾上腺素、凝冰球、冲刺矛 等所有游戏道具)(目前发现“冲刺矛”这一道具在局外可能存在无法获得对应道具的问题”)。
4.新增管理员强制开局指令 /gost start
管理员可跳过最小玩家数限制强制开始游戏。虽然我们此前就有/gostadmin start,但是这个可以正常随机地图。
5.Config_version从26升级到 27,插件版本升级到 2.3.0。
6.新添加了对局结束之后展出积分排行榜
1.Added new items:
“Spear Rush” uses GOLDEN_SPEAR as the item ID, left-click to perform a spear rush-like dash effect, consumed immediately after use. (Only available on server version ≥ 1.21.4, with automatic version detection on startup.)
“Levitation Potion”: Uses LINGERING_POTION, right-click to gain Levitation effect for 4.5 seconds.
2.Added admin test mode (/gostadmin testmode):
Admins can start a solo game session that won’t end due to insufficient players, with normal item distribution for testing purposes.
3.Added admin command /gostadmin giveitem <item name>:
Admins can directly obtain any item (supports fuzzy matching)
(Now I found that sometimes “Spear Rush” may not be out of the game,Is it a bug I need to fix?).
4.Added admin force start command /gost start:
Admins can bypass the minimum player limit to force start a game.
5. Configuration version upgraded to 27, plugin version upgraded to 2.3.0.
6. Added a leaderboard display after the match ends.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Gost-2.3.0.jar | Unknown | 194.6 KiB |
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:SKYebqyY:x1mqXqaM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SKYebqyY:x1mqXqaM"
}

