btw if u make a plugin for 1.21.8 its ok too

The problem

My custom block registered correctly, appeared in the creative tab, but rendered as a missing texture cube.

No errors at runtime, just a purple-black block.

What I checked first

• Registry name was correct

• Blockstate JSON existed

• Model JSON paths looked fine

• Textures were in the right folder

Everything looked correct.

The actual issue

The problem was a mismatch between the blockstate JSON and model file names.

Example mistake:

blockstates/my_block.json
models/block/myblock.json

Forge does not warn you when these names don’t match exactly.

The fix

Make sure naming is consistent everywhere:

• blockstates

• models/block

• models/item

• registry name

Also ensure that:

• JSON files are lowercase

• no extra underscores or hyphens exist

• resource reload cache is cleared

Restarting the client after fixing resource paths helped immediately.

Takeaway

If your block exists but renders wrong, the issue is almost always:

• naming mismatch

• resource path typo

• cached resource reload

Hopefully this saves someone else an hour.

From a player and developer perspective, here’s what consistently separates good mods from great ones.

Performance awareness

High-quality mods avoid ticking when unnecessary, cache results, and respect server performance.

Consistent behavior

Items behave predictably, configs work as expected, and nothing breaks silently.

Clean UI/UX

Menus don’t lag, text is readable, tooltips explain behavior without external documentation.

Compatibility mindset

Good mods avoid hard conflicts, use proper tags, and integrate with existing systems instead of overriding them.

Documentation

Even minimal README files or in-game descriptions dramatically improve user experience.

None of these are flashy, but together they’re what make a mod feel professional.

Interested to hear what others prioritize.

https://geysermc.org/download/

I installed it in the mods folder, but after starting, it didn't create a Geyser folder as instructed in the documentation.

Did I download the wrong version (the Spigot version)? I downloaded NeoForge (chatGPT told me it's compatible with Forge)

Please teach me...

Thanks 

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.

Is the old method still valid, or should everything be handled with ModConfigEvents now?

Any guidance from experienced modders would be great.

— Myroslav M. Abdeljawwad aka Myroslav Mokhammad Abdeljawwad

A few simple tips:

• Always validate your JSON using an online validator

• Make sure your paths match exactly (Forge is case-sensitive)

• Check that all textures are referenced from the correct namespace

• If your model is invisible, 90% of the time it’s a missing comma or wrong folder name

Hopefully this helps someone avoid an hour of debugging like it did for me.

Best regards,
Myroslav Mokhammad Abdeljawwad

I DID IT!! Finally!

I did it in perhaps the most jank way possible, but it does work.

I went into my compiled .class files under build/classes/java..etc etc and found the one class I needed to replace. Then I took a compiled version of the mod, opened it up with xarchiver, and just deleted the existing file and replaced it with mine. Then I did the same to the images, and now it just works! Amazing!

Hello to all,

I was going to make a post under modder support, but after some consideration, this seemed like a better call. Apologies if this post does not belong here though.

To start, I am fully willing to admit I am way in over my head here, so if someone wants to just point me in the right direction in order to actually start doing things properly rather than trying to fix this mess I created, I understand and appreciate it.

If you have any suggestions, I would grateful to hear them! Thank you for your time!

Basically, I am working on a modpack for some friends of mine and myself which I plan to make very difficult, but hopefully not too tedious. One of the ways that I intend to do that is by adding backpacks that are small. I found the mod "Useful Backpacks" by U Team and it seemed great, but the backpacks were just too big. So I downloaded and modified the source code to make them smaller, and it worked out great! The backpacks were way smaller and I could test them out fine by running the forge version client (it is a multiloader setup). However, when I went to publish the mod, I could not for the life of me get it to publish. Whenever I tried to, it throws the error "Publishing artifacts is only allowed when property createBuild is supplied." Digging around in the gradle files lead me to find that the setup was seemingly never mean to output a local file, but rather to publish directly to mod sites and Github (I think). Despite my attempts to tinker with the gradle files to add local publishing and strip out as much (hopefully) unneeded code (for forge) as possible, I still have not been able to get it to publish (still runs the client though).

This was a bit of a surprise as I had tinkered with some other mods and had no issues publishing them before.

Attempt number two saw me trying to rebuild the project in a separate directory after outputting an archive of the desired branch. By merging the files from "common" into the forge directory along with the core mod files I saw some progress, but also plenty of errors. Needless to say, that did not go far, but I did try a few times.

Which leads me to attempt number three. I decided that rather than trying to modify existing code directly, that it might be best to try and make an addon mod that changes a very small amount of code in Useful Backpacks. I was able to import the mod as a dependency, so I can call on files from the original mod. Sadly the one java file I need to modify is a public enum so no directly overriding that (I think). Instead I figured I would just override everything that calls it instead and point the new files to my own public enum. Would this even work? Does this make any sense? No idea! Regardless, it shows some promise I believe, but it still is giving me a bit of a rough time.

I still have some other ideas: do attempt two again but import the core files instead of directly adding them, mess around with the gradle files from the original project some more, etc etc.

Honestly, at this point I wonder if I should just make my own backpack mod from scratch.

That is basically it. Hopefully whoever is reading this is not cradling his or her head in pain right now. I have learned quite a bit from the constant failures so I think I will figure this out at some point.

Thank you once more for your time!

Info:

MC: 1.20.1

Forge: 47.2.20 or 47.4.0

(depends on whether I am using the latest version or the one used in the Useful backpacks' source code)

Useful Backpacks: 2.0.1

Mapping Channel: parchment

Mapping Version: 2023.09.03-1.20.1

OS: Arch Linux x86

IDE: VSCodium

Logs:

Attempt one: https://pastebin.com/i23fbxTW

The one java file I need to modify (modified): https://pastebin.com/71uYJhP2

(I also need to modify three image files, but I figure that should be no issue)

I remember back when I was in high school and had way more time to develop mods, there were tons of active posts, and while the documentation wasn’t always super extensive, you could always find someone to help you out with your questions or see someone else’s threads that were really informative.

But lately, I’ve noticed that the forum seems pretty empty compared to how it used to be. I’m wondering, is there a specific reason for this? Is it just that the community has moved to other platforms, like Discord? It feels like a lot of the knowledge base and conversations have shifted over there.

I’m just curious to hear others’ thoughts on this, and if anyone knows why the forum has become quieter, I’d love to know!

Thanks!

My vision for this mod is to have auto generated structures from wich factions like the covenant, banished and flood will spawn from. Each faction is hostile to one another and will attack each other and other mobs on sight. Each faction will grow increasingly stronger as you kill them or by naturally leveling up as they spread. Theirs an arsenal of weapons you can pick up from said faction to give them a taste of their own medicine. My priority is on adding the covenant first as each faction will be added step by step.

Here's what I've done so far :

I need a mod to help build something similar litematica

in forge 1.20.1

I mainly use MCreator for development, as it’s my preferred tool, but I’m open to integrating custom code, models, and assets from collaborators.

Main Question:
Would anyone be interested in joining the development of this mod?
I’m looking for people who could help with:

• 3D Models (weapons, mobs, bosses, environmental assets)
• Sound Design (boss themes, dungeon ambience, ability sounds)
• Texture & Artwork (UI elements, icons, environment textures)
• Additional Coding (if needed for complex systems beyond MCreator’s scope)

Concept:

• Players can enter portals leading to themed dungeons.
• Each dungeon ends with a unique boss battle.
• Defeating bosses grants special XP to improve stats (strength, mana, speed, defense).
• Rare loot, upgradeable gear, and unlockable powers.

Extra Features Planned:

• Multiple dimensions with unique environments.
• NPCs giving quests.
• Random portal events appearing in the Overworld.

Technical Approach:

Development will primarily use MCreator for rapid prototyping.

• Custom models and textures can be integrated.
• NeoForge API features may be added for advanced functionality.

If this project interests you, feel free to reply here or send me a message so we can discuss ideas, asset requirements, and a possible development roadmap.

Post text:
Hey everyone!

I’ve been digging into Minecraft modding for a while and have one big question that I can’t figure out on my own. Maybe someone with more experience could help or give me some advice.

Here’s the issue:
When I take a “normal” Minecraft mod — for example, one that just adds some blocks or new items — I can easily change its structure, package names, or even rebrand it entirely. It’s straightforward.

But as soon as I try this with cheat-type mods like XrayMod or AntiXray, everything falls apart.
Even if I just rename the classes, refactor the packages, or hide its identity somehow, the mod either breaks or stops working properly. XrayMod in particular is proving to be a nightmare to modify without losing its core function.

So my question is — why is this so much harder with cheat mods like Xray?
Is there something fundamentally different about how they’re coded, loaded, or protected that prevents simple renaming or restructuring? And if so, how can I actually learn to understand someone else’s cheat mod enough to safely refactor it without breaking the core features?

I’ve already been spending over two months trying to figure this out and haven’t gotten anywhere. It feels like there must be some trick or knowledge I’m missing.

Would really appreciate any thoughts, tips, or references — maybe there are guides or techniques for understanding cheat-mod internals?
Or if you’ve successfully “disguised” a cheat mod like Xray before, I’d love to hear how you did it.

Thanks in advance for any help or discussion. ✌️