Version 1.2.0

The goal of this update is to provide more customizability to players and a few more QoL things that were requested in the last few months.

• Added datapack support for custom pokemon sizes
• Added config option biasSizeTowardAverage
• Added check size option to pokesizer command
• Allow pokesizer command to be run by server

Datapack Support

Added support for defining pokemon or groups of pokemon with custom sizes. These sizes will be applied for the pokemon regardless of the sizer being used.

The files should be put under the following structure in your datapack:

data/cobblemonsizevariation/custom_sizes/

The custom size file is structured as follows:

example.json

{
  "species": [
    "bulbasaur",
    "weedle"
  ],
  "minSize": 0.1,
  "maxSize": 10.0
}

• The species list can be as little as one pokemon or as many as you like.
• The min and max size can be lower and higher than the values defined in the other sizers. For example, the max size above is 10.0 instead of 2.0
• Currently the custom sizes won't work with the pokesizer command. A fix for this will come in the future.

BiasSizeTowardAverage config option

• Defaults to false
• If the config is set to false nothing will change
• If true, the sizes that are generated for each pokemon will always be closer to the average of the min and max values. This makes regular sized pokemon more common and tiny and huge pokemon more rare.

Check size with pokesizer command

Added a new parameter to the pokesizer command that returns the actual size of the pokemon being queried.

eg: /pokesizer <player>|self Bulbasaur check

This will send a message in chat with the size of the pokemon you selected:

The size of your Bulbasaur is 1.00

Allow server to run pokesizer command

A small change that allows the server to run the pokesizer command.

This will not work with the self parameter. You can only use it from the server when targeting another player on the server.