Jump to content

Does anyone know how to add mods to your development environment (not dependencies, but mods for testing). (1.20.1, 47.1.3)


Linksapprentice

Recommended Posts

Hi! I'm relatively new to mod development, but not at all new to modpack development. I've decided to take things up a notch in quality and start making some core content for a modpack that I've been developing for about half a year. It is 1.20.1 (47.1.3). I've started to write code for my core mod, but I was wondering if anyone knew of a way to get my development environment to run my modpack instead of a fresh client with forge and the core mod. I know how to define dependencies, but the vast majority of mods in the pack do not need to be dependencies for the pack. Preferably I'd also like to have it register my config settings and other modpack things, like crafttweaker scripts, directly from the 'runClient' and 'runServer' commands. Btw I'm using IntelliJ Community Edition as my IDE if that effects anything. Thank you for reading! 

Link to comment
Share on other sites

  • 3 weeks later...

There should be a run folder inside your project root (beside src, gradlew.bat etc) inside of which is a "normal minecraft installation" with config, logs, mods, resourcepacks, saves, etc.

You should be able to drop whatever you want in there to have it load with the game, separate from being in your dev environment

Developing the Spiral Power Mod .

こんにちは!お元気ですか?

Link to comment
Share on other sites

On 12/13/2023 at 1:46 PM, Rohzek said:

There should be a run folder inside your project root (beside src, gradlew.bat etc) inside of which is a "normal minecraft installation" with config, logs, mods, resourcepacks, saves, etc.

You should be able to drop whatever you want in there to have it load with the game, separate from being in your dev environment

yeah but dont works you put some mod.jar there an the console trow a lot of error of mixing and dont run  

Link to comment
Share on other sites

  • 4 weeks later...
On 11/22/2023 at 3:42 PM, Linksapprentice said:

Hi! I'm relatively new to mod development, but not at all new to modpack development. I've decided to take things up a notch in quality and start making some core content for a modpack that I've been developing for about half a year. It is 1.20.1 (47.1.3). I've started to write code for my core mod, but I was wondering if anyone knew of a way to get my development environment to run my modpack instead of a fresh client with forge and the core mod. I know how to define dependencies, but the vast majority of mods in the pack do not need to be dependencies for the pack. Preferably I'd also like to have it register my config settings and other modpack things, like crafttweaker scripts, directly from the 'runClient' and 'runServer' commands. Btw I'm using IntelliJ Community Edition as my IDE if that effects anything. Thank you for reading! 

Wow, nice job

Link to comment
Share on other sites

i need help with my mod its alliance of valiant arms the minecraft mod i dont know where to put the file i put it in the normal area and another question do i put it in my forge folder and if theres multiple then which folder please help and thanks to everyone who replys

i forgot to say im not the dev for this i just want to run it on my minecraft 1.20.4 game

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.