Links
Tags
Creators
Details
4.6.2-neoforge.1
Compatibility
Changes
First public preview release of ViaNeoForgePlus.
ViaNeoForgePlus is derived from ViaVersion/ViaFabricPlus and adapts the project for NeoForge.
Requirements
- Minecraft 26.2
- NeoForge 26.2.0.11-beta or a newer compatible 26.2 build
- Java 25
- Client-side installation only
Highlights
- Ports the ViaFabricPlus client integration from Fabric to NeoForge.
- Bundles the ViaVersion, ViaBackwards, ViaAprilFools, ViaLegacy, and ViaBedrock protocol stack.
- Preserves upstream API packages, translation keys, resource namespaces, and persistent identifiers for compatibility.
- Includes NeoForge metadata, access transformers, configuration paths, commands, and mod-list integration.
Installation
Download ViaNeoForgePlus-4.6.2-neoforge.1.jar and place it in the NeoForge instance's mods directory.
Verification
- Main JAR SHA-256:
2250D8BBCABA27B7CBBB5EAD655816AC781F0E71AB11B982F8A9C6EAF8E3AE75
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:P1xkizgf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PMtL44Ny:P1xkizgf"
}

