NeoBackports

⭐ — (9 endorsements) 📥 356 downloads 📌 v1.2.5 📅 6/24/2026
🟡 Updated this year

By Nikdo53 · forge

⬇ Download Mod Source: Modrinth ↗ 📅 Updated: 7/31/2026 📅 Created: 6/24/2026
⚠️ Install Order · 2 steps
1🛠️ Forge — Minecraft Forge (mod loader) Download ↗
2🛠️ Fabric — Fabric Loader Download ↗

Install in this order, then this mod last — most mods fail to load without their framework and dependencies in place.

🔍 Analysis

  • 🏆 #88 of 371 forge mods in this game by downloads

📋 About This Mod

A library for using neoforge 1.21.1 features and methods on forge 1.20.1 This mod is intended to be used as a library included with other mods. Currently, the only standalone features are blurred 1.21-style gui backgrounds. Manually installing a newer version than is packaged is only useful for fixing bugs ### Current features include: - Datamaps - Data components - Data attachments - Stream codecs - Blurred gui backgrounds (enabled with a built-in resourepack) - DeferredHolders (and their subtypes) - 1.21.1-style networking - Recipe serializers with codecs - useItemOn and useWithoutItem methods for blocks ... and a lot of convenience interface extensions ### Q&A - **Why backport to 1.20.1? wouldn't it make more sense to help devs port up instead of down?** - Making a lib for foward porting is fundamentally pointless, as it carries technical debt and would require porting the lib up every new version. Devs would never get used to new features, even when they are objectively better, and would make laggier and buggier mods. Doing it this way means we can satisfy the 1.20 crowd while still pushing them towards newer version - **This sounds like a synitra connector type mod, could it work that way?** - Theoretically, if I put a lot of work into it, it *could* make very tiny 1.21.1 mods run on 1.20.1, but the support would be **extremely** limited so it's not work the time. TLDR: **NO** ### Installation instructions Since this lib uses interface injections, switching from ForgeGradle to **ModDevGradle Legacy** gradle plugin is required. Documentation (https://github.com/neoforged/ModDevGradle/blob/main/LEGACY.md) and a working MDK (https://github.com/NeoForgeMDKs/MDK-Forge-1.20.1-ModDevGradle) In build.gradle: ``` repositories { // Some other repositories you might have... maven { url = 'https://nikdo53.github.io/NeoBackports' } } dependencies { // Some other dependencies you might have... jarJar(modImplementation("net.nikdo53:NeoBackports:${neobackports_version}")) interfaceInjectionData("net.nikdo53:NeoBackports:${neobackports_version}") } ``` In gradle.properties: ``` # Set this to whatever is latest neobackports_version=1.2.2 ``` ## Technical differences Features aren't backported 1 to 1 (due to backend differences between versions) but should be similar enough for most mods to just work without major differences ### Class names In order to make the difference between original forge/vanilla classes and backported ones, backported classes get the "neo" suffix, for example: - SmithingRecipe -> SmithingRecipeNeo - PacketDistributor -> PacketDistributorNeo - DeferredRegister -> DeferredRegister**Typed** (this ones different cuz i forgot) ### Data components/attachments Unlike 1.21.1, these are just clever wrappers for existing features (item nbt and capabilities respectively), meaning that other mods not using this API should be able to access them like normal. ### Datamaps These have been (with permission) ported directly from neoforges code with minimal differences. Note that the login packet which handshaked known datamaps has been removed and non-mandatory are generally not supported. I might return to this in the future, but since this mod is required on both client and server, it's probably not very useful (and 1.20.1 login packets are weird) ### Stream codecs The ByteBuf generic has been removed, since everything uses FriendlyByteBuf: StreamCodec<RegistryFriendlyByteBuf, SomeClass> -> StreamCodec<SomeClass> <details> <summary></summary> The icon is a tibetan fox, it looks pissed cuz its been forced to use forge </details>

A library for using neoforge 1. 21. 1 features and methods on forge 1. 20. 1

This mod is intended to be used as a library included with other mods. Currently, the only standalone features are blurred 1. 21-style gui backgrounds. Manually installing a newer version than is packaged is only useful for fixing bugs

### Current features include: - Datamaps - Data components - Data attachments - Stream codecs - Blurred gui backgrounds (enabled with a built-in resourepack) - DeferredHolders (and their subtypes) - 1. 21. 1-style networking - Recipe serializers with codecs - useItemOn and useWithoutItem methods for blocks

... and a lot of convenience interface extensions

### Q&A - Why backport to 1. 20. 1? wouldn't it make more sense to help devs port up instead of down? - Making a lib for foward porting is fundamentally pointless, as it carries technical debt and would require porting the lib up every new version. Devs would never get used to new features, even when they are objectively better, and would make laggier and buggier mods. Doing it this way means we can satisfy the 1. 20 crowd while still pushing them towards newer version - This sounds like a synitra connector type mod, could it work that way? - Theoretically, if I put a lot of work into it, it could make very tiny 1. 21. 1 mods run on 1. 20. 1, but the support would be extremely limited so it's not work the time. TLDR: NO

### Installation instructions Since this lib uses interface injections, switching from ForgeGradle to ModDevGradle Legacy gradle plugin is required. Documentation (https://github.com/neoforged/ModDevGradle/blob/main/LEGACY.md) and a working MDK (https://github.com/NeoForgeMDKs/MDK-Forge-1. 20. 1-ModDevGradle)

In build.gradle: ``` repositories { // Some other repositories you might have... maven { url = 'https://nikdo53.github.io/NeoBackports' } }

dependencies { // Some other dependencies you might have...

jarJar(modImplementation("net.nikdo53:NeoBackports:${neobackports_version}")) interfaceInjectionData("net.nikdo53:NeoBackports:${neobackports_version}") } ```

In gradle.properties: ``` # Set this to whatever is latest neobackports_version=1. 2. 2 ```

## Technical differences Features aren't backported 1 to 1 (due to backend differences between versions) but should be similar enough for most mods to just work without major differences

### Class names In order to make the difference between original forge/vanilla classes and backported ones, backported classes get the "neo" suffix, for example: - SmithingRecipe -> SmithingRecipeNeo - PacketDistributor -> PacketDistributorNeo - DeferredRegister -> DeferredRegisterTyped (this ones different cuz i forgot)

### Data components/attachments Unlike 1. 21. 1, these are just clever wrappers for existing features (item nbt and capabilities respectively), meaning that other mods not using this API should be able to access them like normal.

### Datamaps These have been (with permission) ported directly from neoforges code with minimal differences. Note that the login packet which handshaked known datamaps has been removed and non-mandatory are generally not supported. I might return to this in the future, but since this mod is required on both client and server, it's probably not very useful (and 1. 20. 1 login packets are weird)

### Stream codecs The ByteBuf generic has been removed, since everything uses FriendlyByteBuf:

StreamCodec -> StreamCodec

The icon is a tibetan fox, it looks pissed cuz its been forced to use forge

🤖 AI-enhanced — based on mod data

📊 Mod Details

Game
Minecraft Mods
Author
Nikdo53
Version
1.2.5
Downloads
356
Endorsements
9
Category
forge
Created
6/24/2026
Updated
7/31/2026
Game Versions
1.20.1
Tags
library

🔧 How to Install Minecraft Mods Mods

Download from Modrinth. Use Prism Launcher or drop into your mods folder.

📖 Full step-by-step install guide for Minecraft Mods →

Visit the official mod page for specific installation instructions for this mod.

🎮 Need cheat codes or console commands? Check ur gaming wiki for Minecraft Mods commands, item IDs, and more.

❓ Frequently Asked Questions

Which Minecraft Mods versions does NeoBackports support?

The author lists 1.20.1. Other versions may work but are untested by the author.

What is the latest version of NeoBackports?

Version 1.2.5, published 2026-07-31 with 356 downloads recorded at the source.

Keep browsing — more Minecraft Mods mods await

📋 All Minecraft Mods Mods 🏆 Top 25 📂 More forge 👤 More by Nikdo53 🔎 Similar Mods 🌐 Best forge (All Games) 🔀 Check Compatibility ⚖️ Compare Mods 🆕 New Mods