Coding From 1.6.4 To 1.8

[Betterjakers]

Hello! I currently know how to code mods in 1.6.4, but I want to start coding in 1.8. Is it the same? If so, how do I set it up?

[Draco18s]

Well, mcp is basically gone, but getting stayed is still somewhat the same.

1) download Forge and unzip into a folder

2) install; either use the command line or create a batch file.  Run

gradlew setupDecompWorkspace eclipse 

3) point Eclipse at the created eclipse folder

 

A base mod file will look 90% the same, except for the annotations and event names.

[jabelar]

Actually quite a bit has changed. But if you're decent in Java it is generally pretty easy to figure out how to update things.

 

The question is whether you want to port some of your old mods from 1.6.4 or whether you just want to start new mod in 1.8.

 

If you want to port your old mods, I suggest you look at tutorials for both converting 1.6.4 to 1.7.10 and also converting 1.7.10 to 1.8.

 

I have a partial list of changes that I've run into here: http://jabelarminecraft.blogspot.com/p/minecraft-forge-converting-your-mod.html

 

Honestly a lot has changed. Blocks in particular use a very different system for managing state and models. Entity ID registration has changed. Lots of new events available, and some no longer available (i.e. sound events). There are also lots of little changes that can trip you up if you were counting on your previous understanding, like some methods have simply changed names or been deprecated/removed.

 

But it is all Java so if you use your IDE (like Eclipse) you can explore the vanilla code and learn how things are done and adapt that to your liking.

[Draco18s]

A lot has changed, yes, what I was getting at was that starting a mod hasn't changed a whole lot.  You're going to have to relearn a lot of systems, but as long as you know what you're doing you can figure out where your knowledge breaks down and how to find the new answer.

[jabelar]

A lot has changed, yes, what I was getting at was that starting a mod hasn't changed a whole lot.  You're going to have to relearn a lot of systems, but as long as you know what you're doing you can figure out where your knowledge breaks down and how to find the new answer.

 

I agree. In fact, he might be better off if he's forgotten the 1.6.4 stuff since then he can just start in re-learning 1.8. In many ways 1.8 is easier or at least improved.

 

But I suspect he may have some 1.6.4 mods that he wants to convert, although that wasn't clear from his post. That could be a chore if he had a lot of custom blocks or items to convert.

[Betterjakers]

All sounds good, except what do you mean "point Eclipse at the created eclipse folder"? I put "Run gradlew setupDecompWorkspace eclipse" in a .bat file in the forge src. It opened command prompt for a second, then closed.

[jabelar]

All sounds good, except what do you mean "point Eclipse at the created eclipse folder"? I put "Run gradlew setupDecompWorkspace eclipse" in a .bat file in the forge src. It opened command prompt for a second, then closed.

No don't do it from a .bat. Just run it from a command window that contains the downloaded forge stuff. It will then go through a fairly long series of steps to download various things, make deobfuscations, etc.

 

Also, if you're just trying to get started in 1.8 again, I have a bunch of tutorials that can help. Here is the tutorial for setting things up: http://jabelarminecraft.blogspot.com/p/quick-tips-eclipse.html