-
Notifications
You must be signed in to change notification settings - Fork 0
Process
You’d probably want to add your server and instances to GitHub and create snapshots each time you’ve integrated new mods.
You should create branches for different situations. For example, you might have some quality-of-life mods you always want to use with any mod pack. With different branches, you can create as many mixin-mod packs as you want, and then you can merge them into your main mod pack after sufficient testing.
Your client instance should have no mods. The server should have only server-side mods. If your client is able to connect, all is good. If a newly added mod doesn't let your clean instance connect it is either client-side only or a client-server mod. For now move it to the mods of the Client-Side Instance.
Your server should have no mods installed. Your client with your client-side mods should be able to connect successfully to the server. If you're not able to connect to the server the newly added mod is not a client-side only mod. If you've done test 1 with this mod remove it from this instance and copy it to the server-client mod instance and server. If you haven't tested it in test 1, move it to the server-side server.
This test is just an extra step ensuring that there are no problems connecting a client with many client-side mods to a server with many server-side mods.
Mods that need to live on both instance and server are tested here.
Copy all client-server and client-side mods to the instance. Copy all client-server and server-side mods to the server. Test that all the mods are happy together.
Leave the "libraries", "mods", and the "forge" and "Minecraft" jars in the root. Startup from fresh, which will create a fresh world and this might trigger some problems that weren't caught earlier.
Get some friends to test your Integrated mod pack before creating a distribution.
If your mod pack is slow, you need to profile it. TBC.
Upload your mod to CurseForge.