Jump to content

Recommended Posts

Posted

So basically I have this fairly large mod that I was working on.  Spent countless hours on it, countless hours learning the ins and outs how to make mobs how to do render custom blocks etc the whole works.  This is a large mod.  Every time an update happens its hours to go through and fix everything. I kept the mod up to date until 1.7 but the upgrade to 1.8 seemed really to knock the wind out of my sails. I have tons of custom rendered blocks on top of everything else like mobs and world gen etc. 

 

I wonder if it is worth it to even begin to try and update the mod all the  way to 1.9.  If I did I imagine by the time I get there the next version will be out and the mojang programmers will probably rewrite and make stuff even more difficult.  Ive noticed the amount of mods are shrinking as Im sure plenty of people are tired of constantly having to completely recode their mods in some cases.  (Also please do not take this the wrong way, my complaints have nothing to do with Forge and the people who spend even more time then I can ever imagine updating Forge to deal with these completely rewritten parts of Minecraft.  You guys are champions. )

 

I just don't want to let the mod go unfinished and unreleased tho, I spent many many many hours and I believe people would really love it. 

 

How long does it take to get familiar with the new json system of rendering blocks?  Once familiar with it, is it easier than the previous rendering system? 

 

Does anyone else feel kind of exhausted and defeated?  Guess Im kinda just hoping for a pep talk lol.  Sorry for the ramble.

 

Posted

I personally would recommend updating to 1.9 and then to 1.9.2.

Changes between those two will not be THAT large and most certailny worthier (is it a word?) than doing 1.8.9 and then 1.9+.

 

Between 1.7.10 and 1.8.x there is a hellish path through updating all rendering code.

 

Then between 1.8.9 and 1.9 there is yet again - next model update which basically removes quite some things that Forge added for modders in 1.8.x, but vanilla added it later in 1.9 (basically just when you are done with updating to 1.8.9 Forge IBakedModel formats, you have to rewrite most of IModelBaked to new 1.9 vanilla format which "replicate" what forge did in 1.8.x).

 

So yeah - if any, I'd go straight to 1.9.

 

Perks:

* 1.7.10 can be called ancient at this moment, sure it still has users, but there were a LOT of nice things added in 1.8+.

* Model system is nice, very clean if you ask me. Keeps everything somewhat "flatter" (clearer) than old ways of rendering.

* Code is kinda much more readable, you have generics, docs, "better" names.

* New hooks for many things (most of old hacky ways can be now replaced with nice short code).

* Forge Capabilities - hell, this is godly powerful. If you use ItemStack-dependend data handling - you will be pleased. E.g: You can have "IEEP-like" (IExtendedEntityProperties) on ItemStacks (load/save NBT only once and normally, e.g per tick, you can operate on anything you want).

* Plenty more, really worth it.

* Additional: 1.7.10 is not only ancient in terms of Forge. E.g: Bukkit is "dead" and now most ppl start going with Sponge - which is API based on Forge 1.8+. Future is bright for compatibility, clear non-hacky modding and server side mods.

1.7.10 is no longer supported by forge, you are on your own.

Posted

thank you for your response, very helpful.  I'm wondering if I would be better off almost rewriting the entire mod from scratch in 1.9 instead of trying to patch up the old code.  What would you suggest?

Posted

You say the mod has its history, it might be good to freshen some code.

 

I'd just make new project and copy-update file after file. Starting from Main, Blocks and Items, through Entities, Tiles, Events, finishing at Rendering (making some helper methods and abstraction on the way).

1.7.10 is no longer supported by forge, you are on your own.

Posted

I honestly think it's worth it. Although, I have seen with several poplular mods is that people want to play with all thier favorite mods together. A lot of popular mods are not to 1.9, and most are still on 1.7.10-1.8. It's honestly up to you. Although, it may take some time to sort out the .json files.

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

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

  • Who's Online (See full list)

    • There are no registered users currently online
×
×
  • Create New...

Important Information

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