All versions
3.2
Release
Config and localization tweaks2 weeks ago 90
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Added:
- New config 'Durability damage' - determines the damage the item in your hand takes when using Black Flash
- New config 'Damage modifier' - Now, during a black flash, the damage you deal is multiplied by a modifier instead of dealing fixed damage. For instance, if a normal attack deals 9 damage, a black flash with a modifier of 2 would deal 18.
- New config 'Player whitelist' - Basically, if enabled, only players on the special whitelist will be able to use Black Flash
- New command
/blackflash whitelist add/remove *target*- Adds a player to the Black Flash whitelist. If the 'Players whitelist' config option is enabled, only whitelisted players will be able to unleash Black Flash
- New command
- Added tag
black_flash:black_flash_entity_blacklistfor modpack creators- Entities included in this tag will not be able to trigger a Black Flash. To add an entity to the tag, use a data pack or cubejs
- Config menu codes - You can now generate code from your config to transfer it to the other world or use it to config black flash for modpacks
- To get the configuration code, click the small white button at the bottom of the config menu. This will generate the code of your mod settings in the input field
- The command
/blackflash config code *code*uses your config code
- Client-side configs now have special icon
- Config descriptions are now translatable
Changed:
- 'Damage' config is now 'Damage modifier'
- Slimes and magma cubes have been added to the
black_flash:black_flash_entity_blacklisttag; Black Flash now checks if an entity is in the tag, rather than checking if it is a slime or a magma cube. - Tweaked config a little bit
- Cleaned up localization files
- Russian localization has been temporarily removed until I re-translate the mod
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:YIxVXqog:3YJZYMMH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YIxVXqog:3YJZYMMH"
}

