Scripts

Powershell

Default values

ServerPackCreator always supplies a couple of default key-value-pairs during script creation. These are stored in a separate file called variables.txt.

The following placeholders will be replaced by ServerPackCreator during the creation of the scripts and variables.txt.

Jabba is a piece of software which makes the installation and usage of a JDK according to the system you are on very easy. It is used by the install_java.xxx-scripts to supply the correct Java version for your modded server should the criteria mentioned in the SPC_SKIP_JAVA_CHECK_SPC and SPC_JDK_VENDOR_SPC be satisfied.

Placeholders and values (3.14.x and up)

As of 3.14.x you can add and edit placeholders. Make sure to map your desired value to the appropriate placeholder key. The GUI provides a table where you can configure these, or any other values, to your liking.

The way this system works is that ServerPackCreator scans the given template for any occurance of a given placeholder, say SPC_JAVA_SPC, and replaces that occurrence in the template with the assigned value, java by default unless you changed it. (Also java for the ZIP-archive, if any is created.) After every configured placeholder has been replaced with the configured value, the resulting text is written to the start scripts, based on the file-endings of your provided templates. BAM! Template engine with customizable content!

Java Install Templates

Starting from version 6.0.0, ServerPackCreator will install the required Java version for the modded Minecraft server using a set of install-scripts. These are based on templates, just like the start scripts.

In the server_files-directory, you will find a couple of files which follow the naming convention of default_java_template.xxx where xxx represents the type of the script, e.g. bat, ps1 or sh.

Changing these templates follows the same procedure as the start scripts. The properties are as follows:

You may also use the GUI, Settings -> Global -> Java Script Templates -> Reset to default values, to reset the entirety of the template setting to factory defaults.

Changing the default templates

Starting from versions 3.13.x and up, the default templates are always overwritten during startup of ServerPackCreator, to ensure any user always has the latest version of the default templates available to them and to ensure any changes made to them, by me, end up in the users hands. This has the benefit of making any migration for future versions not your problem.

The downside: If you want to customize these templates, you will have to create separate templates and set the property for the templates accordingly.

In other words:

1. Copy the desired template to a name of your liking, e.g. custom-template.sh

2. Make your changes to these custom templates

3. Set de.griefed.serverpackcreator.serverpack.script.template.sh to /path/to/custom/templates/custom-template.sh

4. ...

5. Profit

Repeat the same for ps1 or bat if you so desire. Keep in mind to change the properties accordingly. The last section of the property-key determines the type of the script, see the following for an example:

Each of these represents the path to a template, for bat, ps1 and sh respectively. If you wish to add a template for another type, simply add a property which ends with your desired type, like so

de.griefed.serverpackcreator.serverpack.script.template.zsh=...

Removing templates

If you wish to return back to the default template for any of the types supported by default (bat, ps1, sh), simply remove the property from the serverpackcreator.properties and restart ServerPackCreator.

You may also use the GUI, Settings -> Global -> Script Templates -> Reset to default values, to reset the entirety of the template setting to factory defaults.