Release 1.1.0

• Added support for multiple sizing algorithms
• Added new sizing algorithm "gen9"
• Updated pokesizer command

Sizing Algorithms

Added support for multiple sizing algorithms to allow for future development of new algorithms.

• Renamed the old sizing to "basic" sizing algorithm
• Added a new sizing algorithm "gen9"
• Added a new configuration field sizingAlgorithm. At the moment, this accepts either "basic" or "gen9" as valid values
• The default sizer used is "basic"

Basic sizing

This sizer will simply take a random value between the minimum and maximum size modifiers and sets that value to the scale of the Cobblemon.

This definition is found in sizes/basic.json

Gen9 sizing

This sizer attempts to replicate the sizing that's used in the 9th generation of Pokemon games.

The sizer will randomly choose a value between 0 and 255 and run it through the following formula to get the size for the Cobblemon:

minSizeModifier + (randomValue/255) * (maxSizeModifier - minSizeModifier) = chosenSizeValue

Thanks to WxAaRoNxW for this suggestion!

The definition is found in sizes/gen9.json

---

Both definitions have default values that can be modified.

Note: In the gen9 definition, the values defined must remain between 0 and 255.

New command functionality

Updated the pokesizer command with additional functionality.

Command definition:

/pokesizer <player|self> [pokemon|slot] [size]

Command permutations

• /pokesizer <player|self>

  • Randomly resizes the entire team for the specified player or yourself if "self" is used

• /pokesizer <player|self> [pokemon|slot]

  • Resizes the specified pokemon or slot to a random size for the specified player or yourself if "self" is used

• /pokesizer <player|self> [pokemon|slot] [size]

  • Resizes the specified pokemon or slot to the specified size for the specified player or yourself if "self" is used

There are no permission changes in this version. You will still need the correct permissions to use these commands.

Extra notes

• The initial size definitions in the main configuration will not be automatically removed. This is so that if any changes were made to the file, they can be copied over to the new files. The old size definitions can be safely deleted at any time.