Minecraft version 1.12.2
https://www.curseforge.com/minecraft/modpacks/rivers-of-iron/
https://optifine.net/adloadx?f=OptiFine_1.12.2_HD_U_F5.jar
See https://github.com/HenryFBP/rivers-of-iron-mc/releases.
You want to download the ZIP files called 'rivers-of-iron-release-*.zip'.
packwiz cf export
Or...
python3 Makefile.py
Look it up on Twitch (Mods > MC > Browse Modpacks > Search > [Rivers of Iron]
)
Or...
Mods > MC > My Modpacks > Create Custom Profile > or (import) a ...
and supply it the .ZIP file.
Import the .ZIP file in MultiMC.
By default, port 25565
is used.
Try ZeroTier or just port forward.
- Import the pack into MultiMC/Twitch.
- Download https://adfoc.us/serve/sitelinks/?id=271228&url=https://files.minecraftforge.net/maven/net/minecraftforge/forge/1.12.2-14.23.5.2854/forge-1.12.2-14.23.5.2854-installer.jar (from https://files.minecraftforge.net/maven/net/minecraftforge/forge/index_1.12.2.html)
- Run the installer.
- Change the path for the Forge installer to the installed modpack (e.g.
C:\tools\MultiMC\instances\rivers-of-iron-latest-v1.0.4-0714798\minecraft
) - Make sure 'Install Server' is checked.
- Run the
.bat
or.sh
file in the installed modpack folder.
Go ahead! No license.
Read https://authors.curseforge.com/knowledge-base/game-specific-support/120-how-to-create-a-modpack for more info.
See https://github.com/HenryFBP/gooeyiron.
- For massive game-breaking changes that warrant a new world.
- For missing block IDs, broken factories.
- For new mods that do NOT remove blocks or break factories.
- For new quests.
- For tweaks that do not remove items.
- For small bugfixes.
-
Switch branch to
release
-- i.e.git checkout release
. -
Update the
release
branch to a state you want to release from.Example:
git merge master
to updaterelease
with all the commits frommaster
. -
Run
git [diff|log] MOST_RECENT_VERSION
to see what's changed since last release -
Update the
RELEASE-NOTES.md
file. This is a log of all release notes. -
Update the
version
attribute in./pack.toml
. -
Optionally, run
python3 Makefile.py
and test the modpack. Fix and repeat 1-5 until it works. -
Make a commit for the
RELEASE-NOTES.md
file, and all other files you wish to be released.Note: the word
alpha
andbeta
will cause the releases to be tagged as such in CurseForge. -
Run
git tag -a vXXX -m "Releasing version XXX"
,XXX
being the new release version. -
git push origin release --tags
. Travis should make a .zip and upload it to Github. -
Run
git checkout master
and thengit merge release
and thengit push
to copy the tags and updates to the release notes over tomaster
branch.
This step requires a Git release to take place first.
On https://www.curseforge.com/project/421665/files/upload,
- Copy the release .ZIP file and upload it.
- Copy the DESCRIPTION.md if it has changed.
- Copy the relevant parts of the RELEASE-NOTES.md.
- Wait for a mod to wake up and approve.
From https://stackoverflow.com/questions/3211809/how-to-compare-two-tags-with-git.
git diff v0.0.1 v0.0.3
: Comparing file changes between tags:git diff v1.0.2
: Comparing file changes between a tag and the HEADgit log v0.0.1..v0.0.3
: Comparing commits between tags
Mostly deprecated. Use packwiz
.
https://github.com/comp500/packwiz
- Put the ZIP file in
input/
- Execute the file
./scripts/import-zip-and-clobber-files.\[ps1/sh\]
. NOTE that this can delete files in./
.
packwiz cf install