Package-level declarations

Types

Link copied to clipboard

Conveniently access all different check-types, whether they passed and which errors, if any, were encountered.

Link copied to clipboard
class ConfigurationHandler(versionMeta: VersionMeta, apiProperties: ApiProperties, utilities: Utilities, apiPlugins: ApiPlugins)

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.

Link copied to clipboard

Method by which to exclude mods during the generation of a server pack.

Link copied to clipboard
class InclusionSpecification(var source: String, var destination: String? = null, var inclusionFilter: String? = null, var exclusionFilter: String? = null)

A FileInclusionSpecification is at minimum a source-declaration from which files and directories will be included in the server pack to be generated.

Link copied to clipboard

Source-indicator for where the modpack came from. Entries are self-explanatory.

Link copied to clipboard
open class PackConfig

A PackConfig contains the settings required to create a server pack. A configuration model usually consists of: