MCPE -Scripts

MCPE Server Scripts provides a lightweight management setup for starting and maintaining an MCPE (Minecraft Bedrock) server. The repository includes an installer script (installer.sh) to configure the environment and the server, followed by a start script (start.sh) to run the server with its built-in features. Use the installer to set up dependencies, create a ready-to-run server directory, and customize basic settings. Once installation is complete, invoke the start script to launch the server with the advanced tooling provided by these scripts, such as automated restarts, backups, or runtime configurations implemented by the project.

Prerequisites: a Linux-based system (or WSL on Windows) with shell access, curl or wget, git, and appropriate permissions.

1. Clone the repository and navigate to it:

• git clone https://github.com/FaigerSYS/MCPE-Server-Scripts.git
• cd MCPE-Server-Scripts

2. Ensure scripts are executable:

• chmod +x installer.sh start.sh

3. Run the installer to set up dependencies and initial configuration:

• ./installer.sh

4. After installation completes, start the MCPE server using the provided start script:

• ./start.sh

Notes:

• The installer.sh handles prerequisites and environment setup specific to this project. If you encounter permission or dependency errors, re-run the installer with elevated privileges (sudo) where appropriate.
• Ensure your system has the required ports open (default MCPE server ports) and adequate resources allocated for the server to run smoothly.

Tips and common issues:

• Make sure to grant execute permissions to the scripts (chmod +x) before running them.
• If your server won’t start, check the start.sh logs for hints about missing dependencies or misconfigurations.
• The scripts are designed to be simple and script-based; they may not cover all edge cases. Review installer.sh and start.sh if you need to customize paths or options.
• Environment variable MCPE_SCRIPTS_HOME (optional) can be used to point to the repository root if the scripts rely on relative paths.
• Regularly update the repository and re-run the installer if you pull changes that affect dependencies or server setup.