Jump to content

Recommended Posts

Posted

Okay first of all i know many many many people will disagree with me and will probably stop reading right about now, but hear me out.

 

In my opinion i believe keeping forge on 1 version of Minecraft and updating it for that version only would make it very easy and less stressful for modders, forge devs, consumers and for everyone who uses the wonderful Minecraft Forge. Now i know what your thinking "WHY?!!! WHAT ABOUT *Insert totally awesome new feature from latest version of minecraft*?!!!!!" mods can add *Insert feature here* and even do a better job at it.

 

If we allow Minecraft forge to be non-parallel to Minecraft versions it will be easier for Modders to develop mods and the Mods don't need to be updated thus taking the dependency away from the developers to keep up with Minecraft's frankly insane updating pattern. since the Minecraft code stays the same the forge devs will have an easier time developing new hooks and new awesome features without the fear of their work being nulled as soon as Minecraft updates.

 

If this comes into effect mods will no longer become in-compatible and we would be able to use them for ever unless forge changes something vital to the mod

 

Just remember this is my opinion i am not forcing you to accept it, that's why its in the suggestions forum

 

Posted

I believe Lex doesn't want to go through the horde of "ZOMG WHYYYY I WANT MODS WITH NEWER MINECRAFTS!!!!"

'nuff said.

Read the EAQ before posting! OR ELSE!

 

This isn't building better software, its trying to grab a place in the commit list of a highly visible github project.

 

www.forgeessentials.com

 

Don't PM me, I don't check this account unless I have to.

Posted

Short answer, Never gunna happen.

Long answer:

1) It is by far harder to update Forge then it is most mods {I say most as there are some exceptions}. So If I can update Forge {Including all the back end stuff you guys dont see} Then a modder can update to a new MC version. Most things when it comes to updates for the end modder, is the same thing repeated a million times. Int he case of 1.7 it's removing all referneces to Block.blockID/Item.itemID. When a modder understands what they need to do, it becomes more tedious then hard.

 

2) Minecraft Updates as of late are large yes, but they are no insane, there update cycle of 4-6 months is NOT crazy. I'ts prety good actually.

1.2: March 1st 2012

1.3: Auguest 1st 2012 (5 Months)

1.4: October 25th (4 Months)

1.5: March 13th 2013 (5 Months)

1.6: July 1st 2013 (4 Months)

1.7: October 25th 2013 (3 Months, This was bumped up due to Minecon)

The last few updates have actually been done {partially} because of our interactions with the Minecraft team, We are slowly moving forward into a world where Minecraft modding WILL be stable, there is no reason for us to stagnate and hinder that progression.

 

3) I WILL NOT back port any Minecraft features to older versions. And If I stop updating to newer versions the entire fucking community will hound me to back port things. Ya.. this isn't gunna happen.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Posted

Int he case of 1.7 it's removing all referneces to Block.blockID/Item.itemID. When a modder understands what they need to do, it becomes more tedious then hard.

 

For the 1.7 release, will there be some sort of reference explaining what methods and such we should use instead of the depreciated ones, or will we have to root around for the answer?

Posted

No, for deprecated names, they have been deprecated for over a minecraft version, modders have had adiquate time to adjust to Forge's changes.

Beyond that it's Vanilla code that has changed. It may be a little bit of work but it's not hard.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Hey! I noticed you're trying to register your alexandrite item and possibly set its resource location manually with setId(...). I wanted to help clarify a few things that might simplify your code and avoid errors. ✅ The issue: You're using setId(...) inside the item registration like this:   public static final RegistryObject<Item> ALEXANDRITE = ITEMS.register("alexandrite", () -> new Item(new Item.Properties().useItemDescriptionPrefix() .setId(ResourceKey.create(Registries.ITEM, ResourceLocation.fromNamespaceAndPath(TutorialMod.MOD_ID, "alexandrite"))))); But: Item.Properties does not have a setId(...) method — this line will either fail or do nothing meaningful. useItemDescriptionPrefix() is mostly used for translation keys (like "item.modid.name") but isn't needed unless you have a very specific reason. 🛠 The fix: You only need to register your item like this:   public static final RegistryObject<Item> ALEXANDRITE = ITEMS.register("alexandrite", () -> new Item(new Item.Properties())); Forge automatically handles the ResourceLocation (modid:alexandrite) based on the name passed into .register(...), so there’s no need to manually assign it. 📝 For the texture: Make sure you have this file in your resources: src/main/resources/assets/tutorialmod/models/item/alexandrite.json { "parent": "item/generated", "textures": { "layer0": "tutorialmod:item/alexandrite" } } And your texture PNG goes here: src/main/resources/assets/tutorialmod/textures/item/alexandrite.png 🌍 For the name in-game: Add this to your en_us.json under: src/main/resources/assets/tutorialmod/lang/en_us.json { "item.tutorialmod.alexandrite": "Alexandrite" }   Note: if im wrong about the issues you are encountering, i apologize.
    • 🛠️ Fix for Transparent or Clipping Item Render Issues When Held in First Person (Forge 1.20+) Hey everyone! I recently ran into a frustrating bug while making a custom item (a rocket) for my Forge mod, and I’m sharing the fix because it’s a bit obscure — and it worked wonders. 💥 The Problem: My item rendered semi-transparent and see-through — but only in first person. It also clipped through nearby blocks when held, unlike default items like swords or leads. The texture file was confirmed to be fully opaque (alpha 255), so the issue wasn’t the PNG itself. Interestingly, when no texture was present and the default purple-black checkerboard appeared, the clipping issue disappeared. ✅ The Fix: I ended up resolving it by randomly trying something I found on a Forge forum post about block rendering. I added this property to my item's model JSON — even though it's typically only used for blocks: { "parent": "item/generated", "textures": { "layer0": "farbeyond:item/rocket_item" }, "render_type": "minecraft:cutout" } Boom. That single line forced the item to render using a proper opaque (cutout) layer, removing all the unwanted transparency and clipping behavior in first person. 🙌 Credit: I originally found the "render_type" trick mentioned here, in a block rendering context: 👉 https://forums.minecraftforge.net/topic/149644-1201-help-with-transparent-blocks/ Even though it was meant for blocks, I thought, why not try it on an item? And it worked! Big thanks to the poster — this fix wouldn’t have happened without that tip. Hopefully this helps anyone else stuck on a weird rendering bug like I was. This isn’t a common item solution, so feel free to share it further. I’d love to know if it works for you too.
    • Use Java 21 instead of Java 24   Also make a test without modernfix
    • Ive been on this world for 2 days now, my computer blue screens pretty often so maybe that has something to do with it. maybe just incompatible mods like a lot of people so im hoping someone more knowledgeable can help me find what i need to get rid of. thank you! paste bin
    • Should probably say that i am running minecraft 1.21.1 and with quite a lot of mods (many of which im unsure should even be on the server side)
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.