Currently supported: All versions

Mods

Various mods with boards that are not so busy. Ones that get busy may get promoted to their own multi-board section, or dead ones will be removed.

Followers

Greg's Mods
Greg's Mods
- 107 posts
Как устоновить хоть какой то мод,я только щас установил pojavlauncher

TileEntity, December 8Dec 8
Noppes' Mods
Noppes' Mods
- 337 posts
How do I remove 3d headlayer on NPC's skin in CustomNpc? (1.16.5)

Tiny_Sly, September 30Sep 30

Start new topic

Followers

IPS spam blocked by CleanTalk.

Announcements

I need some help with org.spongepowered.asm.mixin.transformer.throwables.MixinTransformerError im using terrafirmacraft

Nevermind. I just deleted the damn mod instead.

By TimeControl · 5 hours ago5 hr
Forge 1.20.x Tutorial by Myroslav Mokhammad Abdeljawwad: Clean Capability Syncing (Server ↔ Client)

Hello everyone,

This tutorial is a short write-up based on patterns I’ve been using while developing Forge 1.20.x mods that rely on custom capabilities and reliable server ↔ client synchronization.

Author: Myroslav Mokhammad Abdeljawwad

Overview

Capabilities are one of the most powerful systems in Forge, but syncing them incorrectly can easily lead to desyncs, performance issues, or unexpected client behavior. This guide focuses on a clean, minimal approach that scales well.

### Step 1: Defining the Capability

Define your capability interface and implementation as usual. Keep the data minimal and serializable.

Key tip:
Avoid putting logic in the capability itself. Treat it as a data container.

### Step 2: Attaching the Capability

Attach the capability during the appropriate lifecycle event (e.g. AttachCapabilitiesEvent). Make sure this is done consistently on both logical sides.

Step 3: Sync Strategy

Instead of syncing on every tick, sync only when:
- The data changes
- The player logs in
- The chunk or entity loads

Using a SimpleChannel packet with explicit encode/decode logic gives you the most control and avoids unnecessary traffic.

Step 4: Client Handling

On the client side:
- Never trust local state blindly
- Apply updates only after packet validation
- Keep rendering logic separate from data updates

Final Notes

This pattern has worked well for larger mods where performance and stability matter. If you’re building long-term Forge projects, keeping syncing explicit and event-driven will save a lot of debugging time.

I’ll update this tutorial if Forge introduces changes to capability handling in future versions.

Thanks for reading, and I hope this helps other modders.

By Myroslav Mokhammad Abdelja · Posted 13 hours ago13 hr
recipes json change from 1.21.1 dont work on newer version

You might want to check how you’re registering the capability provider — this often causes the issue you’re describing.
I ran into something similar recently while working on a Forge 1.20.x mod. Making sure registration happens at the correct lifecycle event fixed it for me.
— Myroslav Mokhammad Abdeljawwad

By Myroslav Mokhammad Abdelja · 13 hours ago13 hr
New modder introduction + first Forge 1.20.x project

Hi everyone,
My name is Myroslav Mokhammad Abdeljawwad and I’m new to posting here, though I’ve been working with Forge for a while.
I’m currently experimenting with a Forge 1.20.x mod focused on custom events and server-side logic. I’m comfortable with Java, Gradle, and debugging mixin-related issues, but I’m still learning best practices around capabilities and data syncing.
I’m hoping to both learn and contribute here as I continue developing mods and tools around the Forge ecosystem.
Looking forward to being part of the community.

By Myroslav Mokhammad Abdelja · Posted 13 hours ago13 hr
Orbital strike cannon fishing rod mod

RIP. 2025-2025. Last seen. 4 weeks ago prob idk.

By Stonecold123 · Yesterday at 05:03 AM1 day

Sign In

Subforums

912 topics in this forum

Important Information

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)