Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 3 years ago
Updated 2 months ago
All versions
21.15.1-mc1.21.1-neoforge
Release
21.15.1-mc1.21.1-neoforge6 months ago 1,067
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added
- Emote System added
- Holding emote wheel key (default 'Y') will open Emote screen, where you can select a emote to play
- Emote system is data-driven. Meaning that users can add custom emotes
- Similar to other datapack systems, it requires each client to load emote animation provided as resource pack
- Persistent Mapped Buffer (by @dfdyz)
- Boosts frame rate by removing the uploading process of buffers to shader
- Requires OpenGL version over 4.6
- Added "swing_sound", "hit_sound", and "hit_particle" that is configurable in ItemCapability
- This is not supported by data pack editor, as we're going to refactor the data pack screen
Changed
- Configuration screen reboot
- The design of configuration screen is clean and modernized
- Splitted configurations with more specific categories, Ui, Graphics, Model, Controls, and Camera
- Some configurations' names have been changed to more standard and in common use terminologies
- Added a side bar to switch Settings, Data Pack Editor, Cosemtics screen
Fixed
- Fixed the player can't play the same attack animation, until it fully ends in the server side
Tested against:
- Minecraft: 1.21.1
- NeoForge: 21.1.217
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| epic-fight-21.15.1-mc1.21.1-neoforge-sources.jar | Unknown | 1.38 MiB |
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:vu3NZ5Ma:L6lE458l"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vu3NZ5Ma:L6lE458l"
}

