Resource Pack Handbook

This handbook is an overview of how to contribute to the resource packs in Gamer Dorks servers. Please read all the way through if you are currently an Artist who intends to contribute to the Minecraft server resource packs.

Locating the Resource Packs

The Resource Packs are stored publicly on GitHub and can be found here:

Cloning the Repository

The following is a step-by-step guide for cloning the Resource Pack repository onto your device so that you can contribute to it directly.

  1. Ensure Git is installed on your device. You can find instructions for your device here.
  2. Create a folder to clone the repository into.
  3. Open git bash (Windows) or your terminal (Linux) and navigate to the folder you created.
    • Use cd <directory> to navigate between different directories (folders).
    • Use cd .. to go back to the previous directory if necessary.
  4. Go to the resource pack GitHub page and click on the green Code button.
  5. Copy the HTTPS URL to your clipboard.
  6. Run the git clone <url> command in your terminal or git bash. Replace the URL with the one you copied in step 5.

Authenticating your GitHub Account

Before making changes to the repository for the first time, make sure you are logged in to GitHub, so that you have the necessary permissions to push changes.

  1. Install the GitHub CLI.
  2. Run the gh auth login command in your terminal and follow the provided instructions.
  3. Return to your terminal. You should now be able to push to the repository.

Creating your Branch

Make your changes in a separate branch of the repository, so that they can be reviewed and pulled at Leadership’s discretion. It is not possible to push to the Master branch unless you are an Administrator or Sr. Dev.

  1. Create a branch by running git branch <name>. Select a name which identifies this branch as belonging to you.
  2. Switch to the newly created branch by running git checkout <name>.
  3. Push the branch to GitHub by running git push --set-upstream origin <name>.

(Ensure the selected <name> is consistent between these three commands.)

Now, all future changes you make will be sent to your own branch and can be merged into the main branch at the administrator’s discretion.

Making Contributions

Whenever you are ready to push the contributions you made to your branch, follow these steps. These will be repeated every time you contribute to the resource pack.

  1. Open git bash (Windows) or your terminal (Linux) and navigate to the folder you cloned the repository into.
  2. Run git fetch and git pull. This will ensure that your local repository is up to date.
  3. After ensuring your local repository is up to date, make your contributions to the resource pack.
  4. Add the changes you made to your commit by running git add <path>, where <path> is the relative file path to files you wish to contribute.
    • Use git add . to add the entire directory to your commit. This is generally easier.
  5. Commit your changes by running git commit. A text editor will open in which you can write and save commit notes, as a brief description of the changes made.
  6. When you are ready to push your changes to the remote branch, use git push. This will update the page on GitHub.

Resource Pack Conventions

All resource packs follow the same directory structure.

All textures should be in the .png format. Texture resolution depends on a few factors:

  • All armor/elytra model textures should be 64×32.
  • Enhanced SMP item textures should generally be 16×16, except for Legendary Crate items and Remnants of the Past items, which are 24×24.
  • Unboxed item textures are 24×24, except for material items, which are 16×16.
  • Unless otherwise specified, textures should be 16×16.

The style of items in-game should follow that of Minecraft’s default textures whenever possible.

Recommended Software

Aseprite is recommended for creating pixel art. If you do not own Aseprite, LibreSprite is a usable free alternative. However, it is likely that you already use an app that works for you, and it is fine to continue to use that.

Notepad++ or Visual Studio Code are recommended for editing .json files.