Survival Essentials is a Minecraft mod that makes survival maps/servers a bit more easy for the player by giving a way to upgrade tools from wood to netherite, giving more ways to get leather and paper so the player can make books and bookshelves a bit faster and by giving a set of wood armor just so players can have a decent set of armor at the start of their adventure. More features to be implemented soon, including a set of redstone tools and armor.

Note: Items names, textures and recipes are WIP(Work in Progress)

Recipes

Mod Guide

1 Book + 1 Redstone = 1 Mod Guide

This book contains all recipes of the mod, it'll be regularly updated as more recipes are added

Contributing

Copied from MarcDiethelm's Contributing guide

If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on Github, new technologies and and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request.

How to make a clean pull request

• Create a personal fork of the project on Github.
• Clone the fork on your local machine. Your remote repo on Github is called origin.
• Add the original repository as a remote called upstream.
• If you created your fork a while ago be sure to pull upstream changes into your local repository.
• Create a new branch to work on! Branch from development if it exists, else from main.
• Implement/fix your feature, comment your code.
• Follow the code style of the project, including indentation.
• If the project has tests run them!
• Write or adapt tests as needed.
• Add or change the documentation as needed.
• Squash your commits into a single commit with git's interactive rebase. Create a new branch if necessary.
• Push your branch to your fork on Github, the remote origin.
• From your fork open a pull request in the correct branch. Target the project's development branch if there is one, else go for main!
• ...
• Once the pull request is approved and merged you can pull the changes from upstream to your local repo and delete your extra branch(es).

And last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code.

License

GNU General Public License v3.0