Jump to content

For the modders out there: how do you prefer to set up a Forge 1.7 workspace?


Texenox

Recommended Posts

Call me really curious, I am indeed. :P

I want to know how you guys would prefer the layout of your Forge 1.7.2 modding workspace. What I have is a regular workspace set up for IntelliJ IDEA, but with any credits, license and readme files in an extra folder called "reference", and I deleted the gradlew file that does not correspond to my Operating System.

 

What about you guys?

Link to comment
Share on other sites

I'd say move the licenses and stuff into /src/main/resouces so that it is picked up by the builder, or potentially link it in using the build.gradle.

And I would also say keep the gradlew file for those who use your repo who arnt using your OS.

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

Link to comment
Share on other sites

I'd say move the licenses and stuff into /src/main/resouces so that it is picked up by the builder, or potentially link it in using the build.gradle.

And I would also say keep the gradlew file for those who use your repo who arnt using your OS.

I don't even keep my code in a maven repo. My mods are not open source.

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.



×
×
  • Create New...

Important Information

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