Links
Tags
Creators
Details
5.0.1
Compatibility
Changes
User-Relevant Changes
-
New user interface
- All screens have been rewritten. The version list now groups versions into the tabs
Modern,Legacy,Beta,Alpha,ClassicandApril Fools, opening on the tab of the currently selected version. - Every entry shows an icon, its update name, and its release date.
- Version lists, settings, and server lists now have a search bar, with version search also matching versions within a range.
- All screens have been rewritten. The version list now groups versions into the tabs

-
Bedrock Edition support
Support for Minecraft: Bedrock Edition, including Bedrock Realms, has been removed from the core mod. This release is required to use the ViaNeoForgePlus Bedrock Edition addon, which restores support through a separate NeoForge addon mod.
-
Settings
- The
authenticationgroup has been merged intogeneral,debughas been renamed toadvanced, andbedrockhas been removed from the core mod. - Visual changes beyond basic gameplay emulation have been dropped. For in-depth visual changes, use a dedicated visual mod instead.
- Removed settings include
Verify session for online mode servers,Automatically select CPE when using the ClassiCube server list,Set session name to ClassiCube name,Show classic loading progress in connect screen,Experimental block connections,Emulate inventory actions in alpha versions,Save scroll position in slot screens,Execute inputs synchronously,Legacy tab completions,Emulate armor HUD,Always tick client player,Serverside block/item place sounds,Hide modern command block screen features,Hide modern Jigsaw screen featuresand most purely cosmetic visual toggles.
- The
-
Other
- Fixed ClassiCube authentication not being completed before joining a server.
- Preserve legacy world clocks in versions 1.21.11 and earlier.
- Fixed ViaVersion's
hide-scoreboard-numbersconfig option to only work for sidebar scoreboards. - Fixed errors caused by invalid stats in versions 1.11 and earlier.
- Updated various translations.
- Fixed the BetaCraft server list refresh button not working.
- Fixed the ViaNeoForgePlus button being cut off on the multiplayer and direct connection screens.
Technical Changes
-
Redesigned API
-
The API instance is now accessed via
ViaFabricPlus#api, which returns aViaFabricPlusAPIinterface. It is split into the sub-APIsprotocolTranslation,conversions,limitations,screensandsettingsinstead of one large interface full of static helpers. -
ViaFabricPlus#getImplandViaFabricPlusBaseare deprecated for removal. Every method forwards to its replacement, so migrating is simply a matter of renaming. -
LoadingCycleCallbackandChangeProtocolVersionCallbackhave been replaced by theViaFabricPlusEntrypointinterface andaddChangeProtocolVersionListener. -
Settings have moved to
api.settings.baseand are registered through their group.ModeSettinghas been replaced byEnumSetting. -
Refer to the updated development documentation for more information.
An example of how to include the API while still being able to run the mod, after running
./gradlew publishToMavenLocalin the ViaNeoForgePlus repository:repositories { mavenLocal() } dependencies { compileOnly("com.viaversion:vianeoforgeplus:5.0.1") { transitive = false } runtimeOnly("com.viaversion:vianeoforgeplus:5.0.1") { transitive = false } } -
-
Removed submodule
The visuals module has been merged back into the core mod. Most of its visual changes that went beyond “basic gameplay functionality” have been removed.
GitHub Repository Changes
-
Organized patches by version
Feature mixins are now categorized by the version range they apply to (
features/v1_8,features/v1_10, ...) instead of by feature name, making it obvious which versions a workaround belongs to. Refer to the updated maintenance documentation for further details.
Translation contributors
A list of all translators can be found here:
https://crowdin.com/project/viafabricplus/activity-stream
Please also read the 4.6.3 changelog.
You can support the original ViaFabricPlus project by donating at:
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:PMtL44Ny:cUzO80NR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PMtL44Ny:cUzO80NR"
}

