Genuine Geniuses Gather Around

[Mikerman50]

Hello to everyone who's reading this.

 

Let me introduce myself, i'm Mikerman50 an ex-porter (vanilla mods - Bukkit mcportcentral.co.za) with VERY little actual modding experience who was recruited by the owner of mcpc to help with a mod, the very basic tasks of assisting in adding certain blocks, which was mainly a case of copy pasting, shortly after that I told the lead coder that I can make models, and since then that has been my primary job.

 

Until recently where the constant chasing of updates have been a hindrance and made it near impossible to add the extra new content we had lined up. which in turn made him feel the need to resign, leading me in charge of updating to 1.7.2+ while he pursues other paths.

So what I'm really looking for is some assistance or pointers of how to update from 1.6.4 - 1.7.2 quickly.

 

Now a couple of things id like to make clear is that I am currently attempting to learn Java and any help given please explain it clearly, imagine if you will a Goldfish crossed with a sloth. And since the Lead Developer has finished he has agreed to let the mod be open source. If you feel you can help this humongous task please message me on here and I shall give you more information.

 

<NB> If anyone does have a FULL list of changes from 1.6.4 - 1.7.2 that might help somewhat

 

Many Thanks

 

Miker

[Jwosty]

Copy your source into a new forge gradle evironment. Look at the hundreds of compilation errors (ok, probably less than that ) and fix them.

[Mikerman50]

nope lol, tried that had over 20,000 errors

 

[Zzyxz]

<NB> If anyone does have a FULL list of changes from 1.6.4 - 1.7.2 that might help somewhat

 

Yeah would be cool if there would be a changelog or something like that for forge...

[Jwosty]

Since those first errors that I can see are mainly due to renames, you could write a little script that uses regexes to search through your source and replace the old names with the new ones. That's really the most you can do.

[LexManos]

... It wont magically just work.

There are TONS of changes in 1.7, it's a MAJOR update.

You're going to have to fix A LOT of errors.

If you don't know java, don't volunteer to take over a project that is written in java -.-

[Mikerman50]

... It wont magically just work.

There are TONS of changes in 1.7, it's a MAJOR update.

You're going to have to fix A LOT of errors.

If you don't know java, don't volunteer to take over a project that is written in java -.-

 

While I do appreciate the reply, I did state that I am trying to learn java. And I didn't exactly volunteer myself, I just refuse to let the mod die. 

 

I see modding as another code base that uses JAVA language.  Because knowing a language doesn't make you able to make the best mod it's down to creativity and maybe eccentricity. All im asking for is a little help.  Like the code is 70% correct.  It just needs pointers in what to update. 

 

As yes change logs say that.  In a vague way.

[GotoLink]

Well, the biggest changes are:

-blockID, itemID ("removed")

-Sounds (to json based)

-Network (to netty based)

-Forge Event (moved to FML package)

-FML interfaces (changed into FML events)

 

Anyway, you'll still have to fix your 20.000+ errors yourself.

You can ask for any specific issue on those forums, but not all of them at the same time.

[Mikerman50]

Thank you.  Next would be to hunt them all down.

[jabelar]

Like everyone here has said, from painful personal experience that migrating a mod from 1.6.4 to 1.7.2 is a very tedious undertaking.  Basically we are now modding a new code base.  There are functions that are entirely different, registrations that are entirely different, asset organization that are entirely different.

 

I'm not aware of any way except to use the IDE (like Eclipse) to help flag your problems and then crawl through and learn to fix each one.  The fixes aren't always easy either -- for example if you relied on block and item IDs those are now referenced differently, if you registered sounds those are now registered differently.

 

Again, the best way to explain it is that all of the Minecraft code as well as the Forge code has been modified extensively and it will ripple through your entire mod code. We're actually modding a different game now (no exaggeration)!

 

Anyway, just look at everything flagged in Eclipse and fix it one by one.  Note that just because you see 21,000 errors it doesn't mean you will have to fix that many -- for many fixes it will clean up whole swaths of reported errors.  Unless you had one million lines of code I don't expect you have to actually fix 21,000 lines of code.  Search and replace (carefully! make sure you use the case sensitive and whole word option when search and replacing, else you can really screw up your code irreparably) should get you pretty far.

[Mikerman50]

well sure as heck feels like that many errors, if anyone feels like looking at it feel free to add any comments or anything that may help.

 

https://bitbucket.org/SimCraft/simcraft

 

P.s I know the code may seem messy, but c'est la vie.

[darty11]

Find and replace Block. with Blocks.

 

You need to do it by case, only replace Block with Blocks if it is referencing a block for example Block.Stone but it will fix a lot of problems.

 

Replace .blockId and .ItemId with nothing, will fix many more.

 

Several other changes like changing setunlocolised name to set block name (only in blocks) and such will really knock out those errors.