Package-level declarations
Core-package of ServerPackCreator.
Server packs are created using de.griefed.serverpackcreator.api.ConfigurationModel, which can be checked for errors using de.griefed.serverpackcreator.api.ConfigurationHandler.checkConfiguration and any of the available variants. Afterwards, when the checks of the given configuration model return no errors, it is fed into de.griefed.serverpackcreator.api.ServerPackHandler.run, which creates finally creates your server pack.
In other words, the intended workflow is as follows:
Create a de.griefed.serverpackcreator.api.ConfigurationModel.
Check it using de.griefed.serverpackcreator.api.ConfigurationHandler.checkConfiguration or variants.
Create the server pack using de.griefed.serverpackcreator.api.ServerPackHandler.run.
Should you wish to customize your instance of ServerPackCreator, see de.griefed.serverpackcreator.api.ApplicationProperties. If you wish to enhance your instance of ServerPackCreator with plugins, see de.griefed.serverpackcreator.api.Applicationplugins and
de.griefed.serverpackcreator.api.plugins.configurationhandler.ConfigCheckExtension
de.griefed.serverpackcreator.api.plugins.serverpackhandler.PreGenExtension
de.griefed.serverpackcreator.api.plugins.serverpackhandler.PreZipExtension
de.griefed.serverpackcreator.api.plugins.serverpackhandler.PostGenExtension
de.griefed.serverpackcreator.api.plugins.swinggui.ConfigPanelExtension and de.griefed.serverpackcreator.plugins.swinggui.ExtensionConfigPanel
de.griefed.serverpackcreator.api.plugins.swinggui.TabExtension and de.griefed.serverpackcreator.plugins.swinggui.ExtensionTab
Core-package of ServerPackCreator.
Server packs are created using de.griefed.serverpackcreator.api.ConfigurationModel, which can be checked for errors using de.griefed.serverpackcreator.api.ConfigurationHandler.checkConfiguration and any of the available variants. Afterwards, when the checks of the given configuration model return no errors, it is fed into de.griefed.serverpackcreator.api.ServerPackHandler.run, which creates finally creates your server pack.
In other words, the intended workflow is as follows:
Create a de.griefed.serverpackcreator.api.ConfigurationModel.
Check it using de.griefed.serverpackcreator.api.ConfigurationHandler.checkConfiguration or variants.
Create the server pack using de.griefed.serverpackcreator.api.ServerPackHandler.run.
Should you wish to customize your instance of ServerPackCreator, see de.griefed.serverpackcreator.api.ApplicationProperties. If you wish to enhance your instance of ServerPackCreator with plugins, see de.griefed.serverpackcreator.api.Applicationplugins and
de.griefed.serverpackcreator.api.plugins.configurationhandler.ConfigCheckExtension
de.griefed.serverpackcreator.api.plugins.serverpackhandler.PreGenExtension
de.griefed.serverpackcreator.api.plugins.serverpackhandler.PreZipExtension
de.griefed.serverpackcreator.api.plugins.serverpackhandler.PostGenExtension
de.griefed.serverpackcreator.api.plugins.swinggui.ConfigPanelExtension and de.griefed.serverpackcreator.plugins.swinggui.ExtensionConfigPanel
de.griefed.serverpackcreator.api.plugins.swinggui.TabExtension and de.griefed.serverpackcreator.plugins.swinggui.ExtensionTab
Types
Manager for ServerPackCreator plugins. In itself it doesn't do much. It gathers lists of all available extensions for TabExtension,PreGenExtension,PreZipExtension and PostGenExtension so they can then be run during server pack generation and during initialization of the GUI.
Manager for ServerPackCreator plugins. In itself it doesn't do much. It gathers lists of all available extensions for TabExtension,PreGenExtension,PreZipExtension and PostGenExtension so they can then be run during server pack generation and during initialization of the GUI.
Base settings of ServerPackCreator, such as working directories, default list of clientside-only mods, default list of directories to include in a server pack, script templates, java paths and much more.
Base settings of ServerPackCreator, such as working directories, default list of clientside-only mods, default list of directories to include in a server pack, script templates, java paths and much more.
API wrapper, allowing you to conveniently initialize, setup and use the different aspects of ServerPackCreator.
API wrapper, allowing you to conveniently initialize, setup and use the different aspects of ServerPackCreator.
Conveniently access all different check-types, whether they passed and which errors, if any, were encountered.
Base for the de.griefed.serverpackcreator.api.ConfigurationHandler to ensure we have the basics for config-checks and config-handling.
Check any given PackConfig for errors and, if so desired, add them to a passed list of errors, so you may display them in a GUI, CLI or website. The most important method is checkConfiguration and all of its variants which will check your passed configuration model for errors, indicating whether it is safe to use for further operations. Running your model through the checks also ensures that the default script settings are present and set according to your pack's environment.
Check any given PackConfig for errors and, if so desired, add them to a passed list of errors, so you may display them in a GUI, CLI or website. The most important method is checkConfiguration and all of its variants which will check your passed configuration model for errors, indicating whether it is safe to use for further operations. Running your model through the checks also ensures that the default script settings are present and set according to your pack's environment.
Method by which to exclude mods during the generation of a server pack.
A FileInclusionSpecification is at minimum a source-declaration from which files and directories will be included in the server pack to be generated.
A FileInclusionSpecification is at minimum a source-declaration from which files and directories will be included in the server pack to be generated.
Custom logging configuration setup to prevent incorrect log-directories when executing ServerPackCreator from CLI from a completely other directory. Or possibly when using symlinks, too. This class prevents the logs being written to the logs
-directory inside the directory from which SPC is being run from.
A PackConfig contains the settings required to create a server pack. A configuration model usually consists of:
A PackConfig contains the settings required to create a server pack. A configuration model usually consists of:
Base-class for the de.griefed.serverpackcreator.api.ServerPackHandler to ensure we have the most important methods for generating a server pack from a given configuration.
A ServerPackFile represents a source-destination-combination of two files/directories. The source is the file/directory, usually in the modpack, whilst the destination is the file to which the source is supposed to be copied to in the server pack.
A ServerPackFile represents a source-destination-combination of two files/directories. The source is the file/directory, usually in the modpack, whilst the destination is the file to which the source is supposed to be copied to in the server pack.
Everything revolving around creating a server pack. The intended workflow is to create a PackConfig and run it through any of the available ConfigurationHandler.checkConfiguration-variants, and then call run with the previously checked configuration model. You may run with an unchecked configuration model, but no guarantees or promises, yes not even support, is given for running a model without checking it first.
Everything revolving around creating a server pack. The intended workflow is to create a PackConfig and run it through any of the available ConfigurationHandler.checkConfiguration-variants, and then call run with the previously checked configuration model. You may run with an unchecked configuration model, but no guarantees or promises, yes not even support, is given for running a model without checking it first.