1.19.2 - Custom Reworked Progression, 45+ Balanced Bosses, hundreds of unique areas/mobs to discover, multiple endings, multiplayer, and so much more!
Available on CurseForge at https://legacy.curseforge.com/minecraft/modpacks/mc-chocolate-edition
we use the todo list to track our progress and act as a sort of changelog.
you can choose an existing issue and assign it to yourself, or create a new one by selecting "add item" at the bottom of a list and give it a title.
select "convert to issue" and choose the chocolate-edition repo.
provide as many details as possible regarding the bug and how to reproduce it, or about the intended feature to be added and why.
assign the issue to yourself and move it to the appropriate column.
"todo" for thing you intend to complete before the next release "in progress" for issues actively being worked on. if you give up on a fix, move it back to "todo" or "goals for next update" "needs testing" for issues that have a open PR awaiting approval. you can add a comment to the issue and link it to the respective PR with a # once a PR has been merged to develop, the issue can be closed with a comment linking the closing PR, and moved to "Done"
main represents the current latest release. It should only be merged to prior to a new version release.
develop branch is the main development branch that represents the next release as it is developed.
Create a new branch derived from develop
git checkout develop
git pull
git checkout -b feature/your-branch-nameDo the changes required by editing the files in your local git repository (not the minecraft instance files directly) copy the changes to your minecraft instance with
bash copyToInstance.shor if you have RunItOn! installed and enabled (ctrl + shift+ p > RunItOn: enable), simple save (ctrl + s) any file within /overrides.
note: if you delete any files that are not in either
/defaultconfigsor/scripts, you will also need to manually delete them from your minecraft instance
after copying over the files, you can run /reload in game to reload crafttweaker scripts.
commit changes when it is in a working state
git add .
git commit -m 'your commit message'When your changes are committed, complete and stable, push your branch to github
git push -u origin head or if the branch has been pushed before:
git pushcreate a Pull Request and assign reviewers Strix (Jonah-Hansen), Toxin (GildedToxin)
main to developfiles changed. make sure nothing is included that is not related to the intended changes.Once your Pull Request is reviewed and approved, merge your branch into develop and then delete your derived branch.
once complete, you can switch back to develop, pull your changes and get started on the next feature!
git checkout develop
git pull
git checkout -b feature/new-featureif you are adding or removing mods, there is a process you must follow in order to synchronize your git repo.
these instructions assume you are using curseforge to manage your instances
make sure you are on a new branch specific to these changes.
close your game if it is open, and add or remove the mod from curseforge by selecting you instance > add more content (puzzle piece icon) > search for the mod and install
launch your game and check that the mod has been added or removed successfully.
export a profile of your instance by selecting your instance in curseforge > 3dots > export profile
ensure configs, defaultconfigs, mods, resourcepacks, scripts, shaderepacks, and overrides.txt are selected, then click export.
extract the contents of the generated .zip
in your local repo, delete your /overrides folder, and copy over the contents from the extracted .zip, overwritting modlist.html and manifest.json
verify that the mod has been added or removed from the modlist, and that the respective config files/folders appear. you may need to manually delete configs for removed mods.
commit and push the changes, open a PR and wait for review.
download and install
the default option are generally okay. dont be scared to ask for help if you need!
instructions assume you are on windows
create a folder somewhere on your computer and call it something like "minecraft chocolate edition project files"
open the folder and right click in the empty space > git bash here
(if this option is not available you may not have installed git correctly)
in your git bash terminal, type, or right click and paste
git clone https://github.com/chocolate-edition/Chocolate-Edition.gityou will see the files being downloaded to a "chocolate-edition" folder.
if you have never used git before, you will need to link your local git to your github account. once the clone is complete, run
git config --global user.name "your github useername"
git config --global user.email johndoe@example.comonce the repo has been cloned, and your git is set up, you can open VScode and choose "open folder"
find the chocolate-edition folder that was created earlier and open. in the explorer view on the left hand side, you can see all the files for this project.
I recommend you change you color scheme to "Dark (visual studio)" from file > preferences > theme > color scheme as some color schemes do not show git changes nicely.
also, open a terminal by selecting teerminal > new terminal at the top of the screen.
in the terminal, select the drop down next to the + icon and "select default profile", then choose "git bash"
runItOn! allows the script that copies files from here to your minecraft instance to run automatically when any file inside /overrides is saved. it can be enabled and disabled by opening the command palette with ctrl + shift + p and search for runItOn: enable or disable
instancePath.txt.example and paste in the file path to your minecraft instance on the first line in the file. (replace the example path). save this file and rename it to instancePath.txt. you should see it become greyed out in the explorer view as this file is unique to you and not tracked by git.the path you give it is the target for where the copy script will send files.
note: you can manually run the copy script at any time by running
bash copyToInstance.sh
you are almost ready to get started! in your terminal, run
git pull
git checkout develop
git pull
bash copyToInstance.shnow your minecraft instance is synchronized with the develop branch from github!
Git is a CLI (command line interface) tool used for version control, which is different than, but works in conjunction with, GitHub. Git is used for managing the local repositories and allows you to push it to the remote repository (GitHub) through command line.
Version control is useful in team settings - or in general - as it allows you to work on many aspects of your code/project, while being able to manage and have an overview of all changes being made, when, where, and by who.
In the Git Terminal, running commands is how you pull, commit, push, and so much more
$ git branch - Prints list of all local branches
$ git branch -d "branch name" - Deletes the chosen local branch - you cannot be on the branch when you delete it
$ git branch -D "branch name" - Deletes the chosen local branch with unmerged changes. you will lose any unmerged c
$ git checkout "name-of-branch" - Switches the files in your local repository to the chosen branch
$ git checkout -b "name-of-branch" - Creates a new local branch derived from the current branch
$ git add . - stages all changed files to the next commit
$ git add overrides/scripts/filename.zs - stages files at the relative path to the next commit
$ git commit -m "commit message" - Commits all staged files to the current local branch
$ git log - Prints a log of all recent commits on the current branch
$ git push - Pushes your changed to the remote repository
$ git push -u origin head - Pushes the current local branch when it does not yet exist on github (you will only have to do it once per new branch)
$ git pull - Pulls the changes for the current branch from github to your local branch
$ git branch -D "branch name" - Useful if you name a branch wrong
$ git checkout -b "name-of-branch" - You should always $ git pull before doing this, so you have the most recent files