Skip to content

Commit

Permalink
typos, improve wording
Browse files Browse the repository at this point in the history
  • Loading branch information
Technici4n committed Nov 13, 2023
1 parent b95cda2 commit 646523b
Showing 1 changed file with 7 additions and 8 deletions.
15 changes: 7 additions & 8 deletions content/news/20.2registry-rework.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,24 +4,23 @@ date: 2023-11-13T19:50:00+01:00 # TODO: update date
categories:
- News
author: technici4n # TODO: probably add maty and schurli, or replace by team
# TODO: add neoforge version below to both entries
summary: |
In this post we go over the changes we made to the registries subsystem of NeoForge,
delivered a few weeks after the initial 20.2 NeoForge release.
Summary of the NeoForge 20.2.X registry system changes.
description: |
In this post we go over the changes we made to the registries subsystem of NeoForge,
delivered a few weeks after the initial 20.2 NeoForge release.
Summary of the NeoForge 20.2.X registry system changes.
---

## Introduction
A big update to the registry system as just released in NeoForge version XXX. <!-- TODO add neoforge registry release version-->
A big update to the registry system was just released in NeoForge version 20.2.X. <!-- TODO add neoforge registry release version-->
Our primary goal is to simplify the code as much as possible,
and align it with the registry system in vanilla Minecraft.

This blog post will go through the most important changes that were made,
to act as a migration guide for modders.

This rework is the first of the three big reworks that will land
in NeoForge 20.2 after [our initial release](../20.2release).
This rework is the first of the three big reworks to land
after [our initial 20.2 release](../20.2release).
The other two systems that will receive an overhaul in the coming weeks
are **capabilities** and **networking**.
Once these also land we will be aiming for a 20.2 stable release.
Expand All @@ -31,7 +30,7 @@ Previously, the NeoForge registry system was completely separate from vanilla's.
Now, we use the existing registry system in vanilla, with a few additions that are relevant to mod support.

This means that `IForgeRegistry` is replaced by the vanilla `Registry`.
NeoForge adds a few method to the vanilla `Registry` type via `IRegistryExtension`.
NeoForge adds a few methods to the vanilla `Registry` type via `IRegistryExtension`.
Here is an overview of the changed methods:
| `IForgeRegistry` | `Registry` |
|--------------------------------|--------------------------------------------|
Expand Down

1 comment on commit 646523b

@neoforged-pages-deployments
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deploying with Cloudflare Pages

Name Result
Last commit: 646523b3f35554e9ed93fcffd4e06839c180537d
Status: ✅ Deploy successful!
Preview URL: https://6ab2631b.neoforged-website-previews.pages.dev
PR Preview URL: https://pr-14.neoforged-website-previews.pages.dev

Please sign in to comment.