Seasons now can cycle!

Seasons changes

All seasons are now stored in a Tree structure consisting of a TreeBranch. Each branch can have many branches but only one parent, can store only one SeasonObject, but one season can be stored in several branches at once and have many parents. Seasons that have no parents (located at the root of the tree) are called highest (first) order seasons. The longer the “path” to a season - the lower its order.

Seasons tree example

A season can store a list of seasons after which it will occur with a specified chance (if there are other seasons that occur after the same season). If at the end of a season it turns out that no season comes after it, a random season is set (given its chance of being set; a chance of 0 means that the season cannot be set automatically).

Configs changes

The config system was completely rewritten and optimized. Now all config files are described in ConfigFileObject and their contents are stored in ConfigContentObject. All values in configs are now automatically typed depending on the default value. Added methods to create a selection from some list. All values are now stored in ConfigValueObject (or ConfigSelectionObject if it is a list).

Methods

addHeader - add header.
addValue - add parameter.
addDynamicSelectionButton - add a selection from a list (as a button in the interface) obtained from the supplier.
addStaticSelectionButton - add a selection from the list (as a button in the interface) passed in the method call.
addDynamicSelectionDropdown - add a selection from the list (as a dropdown list in the interface) received from the suppler.
addStaticSelectionDropdown - add a selection from the list (as a dropdown list in the interface) passed in the method call.
addDynamicSelectionSuggestion - add a selection from the list (as a prompt when entering text in the interface), received from the suppler.
addStaticSelectionSuggestion - add a selection from the list (in the form of prompts when entering text in the interface), passed when calling the method.

Parameters

key - key, used to get the value.
value - default value, further typing of the changed value depends on the type of this value.
header - header (mostly decoration), specify “” if you want to inherit it from the previous added value or header.
description - description of the parameter.
consumer - lambda expression executed when the value is changed, receiving the old and new value as input.
list - list containing possible values for the parameter.
supplier - lambda expression that returns the list.