KettleMC PaperSpigot 1.7 Fork

⚠️ Log4Shell is fixed on the server side! It is however still possible to attack old and vulnerable clients which have not yet been patched. Please make sure to apply client side patches as well.

This is the primary repository for the KettleMC PaperSpigot 1.7.10 software. PaperSpigot is a high performance Spigot fork that aims to fix gameplay and mechanics inconsistencies. PaperSpigot 1.7.10 is no longer a supported software by their development team; please do not bug them to fix any issues for you. You are free to submit issues via the Issue tracker on GitHub, we will aim to fix or add any issues you come across.

This is a fork of IPVP-MC/Paper-1.7, which added some new patches to paper.

Installation Instructions

Install our customized version of PaperSpigot via two easy steps:

1. Clone this repository to your computer via git clone or GitHub's download feature
2. Run ./build.sh and copy the paper-1.7.10.jar from your main folder.

If you are more experienced with Paper you can also do the steps manually.

1. Clone this repository to your computer via git clone or GitHub's download feature
2. Initialize git submodules: git submodule update --init
3. Apply code patches to update submodules: ./applyPatches.sh
4. Compile the code via Maven 3: mvn clean install
5. The PaperSpigot server file will appear in the PaperSpigot-Server/target/ directory as paperspigot-1.7.10-R0.1-SNAPSHOT.jar

New to this?
Installation requires Git and Maven 3, if you do not have these please view the following links:

• Maven 3 Download and Installation Instructions
• For Windows: Git Download

Developers

Creation of a patch is simple and easy:

1. Follow the Installation Instructions and install our current patches.
2. Navigate to PaperSpigot-Server or PaperSpigot-API and modify the code you need.
3. Commit your changes to the PaperSpigot-Server or PaperSpigot-API subdirectories using git commit -m "Patch name".
4. Return to the parent directory and execute the ./rebuildPatches.sh script.
   • This will automatically generate your new patch files for your code.
5. Commit your patch files to git in the main repository directory.