Jump to content

Starting Forge Development...


Airwolf89

Recommended Posts

Well, not exactly a thread where I cry for help to a specific problem, but I have started Minecraft modding yesterday (I develop Java since a few years) and I have to say my respect for all minecraft modders has grown a mighty bit =)

 

I have done a few tutorials, after I finally found a forge source version which hasn't run into any error messages right from the start, and I realised the code isn't that hard.

What really bugs me is the fact the even the simplest bits of code seem to change in every tiny minor release and I have to do the same things different (because things don't work the way like I see them in the tutorials) and that the referenced Minecraft code is all obfuscated. If you look for something on google you have to hope that your problem is adressed in the right version on any forums.

 

How do you manage to keep track of all those changes and find out what you have to use in this jungle of ever changing, obfuscated code? In those two days in which I started learning this, the idea of making my own MC mods and even keep them up to date for the varying releases has become rather unpleasent. It seems to me that I would have to re-develop my mods for every single release there is. I knew there are some problems in the code which keep the modders from releasing their mods for the current versions, but I didn't expect something like this. =)

 

Maybe you have a few tips for me on how to start and face those problems, if not, I think the MC mod development is something I'd rather not try for myself =)

 

Thanks in advance =)

Link to comment
Share on other sites

It sounds like you are doing something wrong. I have only been modding for a little while (since 1.7.2) but i have found it really easy even with my very limited java knowledge (i am learning java at the same time i am learning to mod) Most of the minecraft src files should be de-obfuscated for you if you have setup your workspace properly. When you say you have to re-develop for every release do you mean every release of minecraft? or forge? If you just started yesterday i dont see how there could have been a lot of updates to ether... 

I am the author of Draconic Evolution

Link to comment
Share on other sites

The most disturbing thing in this thread is:

"after I finally found a forge source version which hasn't run into any error messages right from the start"

 

I really hope, that by this you mean you found this link www.minecraftforge.net/forum/index.php?action=files and downloaded source.

Follow this tutorial (if you haven't found it yet) http://www.minecraftforge.net/forum/index.php?topic=14048.0

 

If you setup your workspace properly then:

"even the simplest bits of code seem to change in every tiny minor release"

Sadly yes. I've been with MC since alpha, modding from Beta 1.6+ and it's kinda pain in the ass.

When created, Minecraft had not just few, but a lot of badly written classes and it's being replaced by better ones since (mostly), well, the "big update" (1.7). After 1.7 most of updating to new version isn't really that hard. Sometimes there might be some bigger changes (like now with 1.8 ) but from my exp i know that rewriting/fixing what's alredy done can't take more than 5% of your total work over mod (well, this depends).

 

"referenced Minecraft code is all obfuscated"

Again - if you setup your workspace properly there should be file in Referenced Libraries (eclipse): forgeSrc-version.jar

Most of important (usable) code IS deobf, and what is not is probably stuff that is just not used in modding (internal methods and game engines).

 

"If you look for something on google you have to hope that your problem is adressed in the right version on any forums"

Forge Forums (here) is probably your best shot :) Always up to date with very nice ppl.

 

"How do you manage... (...)"

Now I really think you set your workspace not quite well. If not, then I really can't refere to your situation, everything is clear and easy for me. MC/Forge updates don't change THAT much.

 

Hope it helped. If you have any questions (best tutorials, etc.) please ask. :)

 

 

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

Link to comment
Share on other sites

Hey there,

 

thanks for the feedback.

 

Well, yes, I downloaded the source files from the page you linked here. I have followed the basic tutorial in the wiki of this page.

I started with the recommended build of 1.7.2. When executing gradle I had the problem that he couldn't fetch some data from Maven and completely failed. I tried some things I found in some forums and finally I tried an older release of 1.7.2 and it worked. I followed the tutorial linked in the wiki here and realised that it is for 1.6.2 and that most things will not work in 1.7.2. After that I tried to install an older version of the forge source, but that also failed due to some failed hash checks (but I saw that this seems to be a known bug due to some changes on mojangs side or so)

So, I got back to 1.7.2 and tried the other series from the guy which was about 1.7. But even in that tutorial I saw that things are different and things didn't work, so I assume they have changed...

 

Regarding the deobfuscated code. I had hoped that I have done something wrong. But the release I used (forge-1.7.2-10.12.0.987), I executed gradle and everything was fine. Everything was build, I got no error messages, I can start MC from Eclipse and so on. I wouldn't know what to do different. Maybe this version doesn't work properly... =)

 

My Java environment should not be the problem, everything is fresh installed from the ground up, path and java home variables set, so there should be no problem here.

 

Tomorrow I will start again with a new environment of forge with the recommended 1.7.2 source (or another version you recommend) and post the problems I encounter.

I really hope that it is not that bad as I learned it until now.

 

Thanks =)

Link to comment
Share on other sites

What really bugs me is the fact the even the simplest bits of code seem to change in every tiny minor release and I have to do the same things different (because things don't work the way like I see them in the tutorials) and that the referenced Minecraft code is all obfuscated. If you look for something on google you have to hope that your problem is adressed in the right version on any forums.

 

How do you manage to keep track of all those changes and find out what you have to use in this jungle of ever changing, obfuscated code? In those two days in which I started learning this, the idea of making my own MC mods and even keep them up to date for the varying releases has become rather unpleasent. It seems to me that I would have to re-develop my mods for every single release there is. I knew there are some problems in the code which keep the modders from releasing their mods for the current versions, but I didn't expect something like this. =)

Unfortunately I think you've got a pretty accurate idea of what it's like.

At every major release, and many minor releases, a whole lot of changes occur which often break large parts of your code which then needs significant rewrites.  It's not a trivial exercise to update them, and it takes a long time (~ 4 months) before the deobfuscation is reasonably complete and a new version of Forge is available).  Then you've got a few weeks of fun to get your mod to recompile, change your methods (and sometimes entire algorithms), test, and re-release.  The landscape is littered with good mods whose authors just got burned out by the grind.

 

You can insulate yourself a reasonable amount by relying on the Forge methods as much as you can (Events for example) because these tend to be more stable. 

Personally, I try to encapsulate my code as much as possible and reduce its interaction with vanilla (and Forge) objects as much as possible.  This has a few benefits-

1) Changes to Vanilla or Forge tend to break only small parts of the code and it's much easier to code an adapter if necessary

2) It's much easier to write test code to perform automated testing of your classes, i.e. to discover what has been broken by the update and to test your fixes.

 

The lack of documentation (and the large amounts of misleading or outdated information) are initially a problem but after a few months you'll get used to it and won't really need it much anymore.

 

You should start with 1.7.10 I think.

 

-TGG

 

 

Link to comment
Share on other sites

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.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • I've been trying to give a little transparency to a block and a custom model, but I'm running into the same issue with the transparency of the block Some guides say I use ItemBlockRenderTypes.setRenderLayer in a ClientEvent class but its deprecated, I already tried to set a Properties in Properties.copy(Blocks.FLOWERPOT) But the render in game still doesn't has transparency, only as an Item  
    • My friends and I are modding to survive But recently I want to use cmd to open the server instead of making the single player game public But when I used two methods to start the server, I encountered two problems first A I used forge to install the server files Created using the original server jar The server was installed successfully and the mod was also loaded successfully. But after I replaced the world file with my survival map, I found that the mod items inside disappeared but could be taken from creation again. So I tried to install the server using forge first B I have studied forge for a long time but successfully installed it. But when I put in mods it crashed But mods can be installed on the server   我和我的朋友們正在mod為了生存 但是最近我想用cmd打開伺服器而不是把單人遊戲公開 但是當我使用兩種方法啟動伺服器時,我遇到了兩個問題 首先AI使用forge安裝伺服器檔案使用原始伺服器jar 建立伺服器已成功安裝,mod 也已成功載入。但是當我用我的生存地圖替換世界文件後,我發現裡面的mod物品消失了,但可以再次從創建中取出。所以我嘗試先使用forge安裝伺服器,BI研究了forge很久但成功安裝了它。但是當我安裝 mods 時它崩潰了但是 mods 可以安裝在伺服器上 我和我的朋友正在mod生存 但最近我想使用cmd開啟伺服器而不是單人遊戲公開   但是當我使用了兩種方法開啟伺服器時遇到了兩種問題   第1個A 我使用了forge安裝伺服器文件 在使用原版伺服器jar建立    伺服器安裝成功 mod也順利加載  但是我將我的生存地圖替換世界文件後發現裡面的mod物品消失了但可以再次從創造拿取  所以我嘗試使用forge安裝伺服器   第2個B forge我研究了很久但也成功安裝了 但是當我放入 mods 之後發生了崩潰 但是mods在1A伺服器上是可以安裝的 Ps 我用谷歌翻譯 so    
    • That’s probably not it because as I stated I’ve done it before. I did it like deadass 10 - 20 times when trying to learn to make this mod pack because I kept wanting to reset my profiles and such. So it definitely works, it looks like maybe the creephosting files were the things that couldn’t be reached I tried reading the crash log
    • I don't know if this is the right place or not, but I have put together a custom modpack and I am in need of others to help me. It's a questing modpack with a lore book i'm currently writing out through Patchouli, and i am in need of somebody who will assist me in making the quests for the pack. It's a Zombie apocalypse modpack inspired by Deceasedcraft  with a tinge of magic and RPG mechanics via Mine and slash. Is there anybody willing to assist me as i'm one person building a modpack I could also use help with optimizations since that's not really my strong suite. 
    • File a report to SPYRECOVERY36 @ gmail com he can legitimately assist in proper review and recovery of all your assets that was stolen. Endeavor to submit your request for a refund to his mail . He also spy and hack any device remotely without any trace. Contact via spyrecovery36 @ gm ail com  
  • Topics

×
×
  • Create New...

Important Information

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