Tags
Creators
Details
3.8.1
Compatibility
Changes
Some details for this release
Do not go on servers with this release, it will not work. unless the server is running neoforge.

Information
THIS IS AN UNOFFICIAL PORT TO NEOFORGE!!!! ALL CREDITS TO Enjarai This version doesn't have any dependencies.
Overview
Do a Barrel Roll is a lightweight, fully clientside mod that changes elytra flight to be more fun and semi-realistic. It achieves this by redesigning movement with a completely unlocked camera orientation in mind, allowing for full pitch, yaw and roll control in flight.
Some subtle and less subtle modifiers are also applied to the camera, including but not limited to smoothing and banking.
Controls
The default controls are as follows, but can be modified:
- Mouse x axis to roll
- Mouse y axis to pitch
- strafe keys (normally A and D) to yaw
Configuration
The mod can be configured in-game using YACL. Once you install both of these, you can access the config screen by finding the mod in the mods list and pressing the config button.
A wide range of options are available, including custom mouse behavior, elytra activation restrictions and changing values of modifiers like banking, sensitivity and more.
Disclaimers
This mod does not actually modify the flight physics themselves, so in most cases it shouldn't trigger anticheat. However, doing things like loop de loops looks to the server like rapid camera movement and may get you flagged. Use at your own risk.
Versions prior to 2.8.3 may not be suitable for use on multiplayer servers due to lax server-side restrictions
Credits
Based on the Cool Elytra Roll mod by Jorbon, specifically it's "realistic mode".
Originally ported to Forge by MehVahdJukaar. Modern Forge port based on Sinytra's multiloader template.
Original Mod by Enjarai
Mod icon by Mizeno.
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:FmdorWvl:UU8Q5VX4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FmdorWvl:UU8Q5VX4"
}![Do a Barrel Roll [NEOFORGE]](https://cdn.modrinth.com/data/FmdorWvl/4e8f6c0171528d6077587724443f8fb05b81c060_96.webp)

