Tags
Creators
Details
All versions
1.9
Release
GreatCombat 1.99 months ago 210
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Folia
Paper
Purpur
Changes
RU
- Добавлены внешние плейсхолдеры
%greatcombat_time% - Оставшееся время в секундах
%greatcombat_time_formatted% - Форматированное время
%greatcombat_in% - Статус боя (true/false)
%greatcombat_in_formatted% - Форматированный статус боя (Да/Нет из конфига)
%greatcombat_opponents% - Список всех оппонентов
%greatcombat_opponents_contains_{имя}% - Проверка наличия оппонента (true/false)
%greatcombat_opponents_contains_{имя}_formatted% - Форматированная проверка (Да/Нет из конфига)
Также можно получать информацию о других игроках через %greatcombat_player_ИмяИгрока_...%
- Добавлено начало боя от кристалла энда
- Исправлена очистка кулдаунов при остановке режима боя
- Добавлены действия при взятие предмета в руку
- Добавлены действия при истечении кулдауна на предмете
EN
- Add placeholder expansion
%greatcombat_time% - Raw remaining combat time in seconds
%greatcombat_time_formatted% - Formatted combat time
%greatcombat_in% - Boolean combat status (true/false)
%greatcombat_in_formatted% - Formatted combat status (Yes/No from config)
%greatcombat_opponents% - Formatted string with all opponents
%greatcombat_opponents_contains_{name}% - Boolean contains opponent
%greatcombat_opponents_contains_{name}_formatted% - Formatted contains status (Yes/No from config)
You can also parse placeholder for other players using %greatcombat_player_NickName_...%
- Add combat starting with end crystal
- FIX cooldowns cache invalidation on combat stop
- Add actions on item held
- Add actions on cooldown expiration
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:MHvv5HlS:lqsjPr5E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MHvv5HlS:lqsjPr5E"
}

