Pregen Unlock instructions

o/ Everyone,

Since I am getting a lot of "wrong" UUIDs recently, since not everyone reads the unlock message, I am going to provide instructions how to unlock chunkpregens content.

So steps to unlock the content:
- Step 1:  Send me your Minecraft UUID.
  - Step 1.1: Don't use a "Website" to obtain it. Because that doesn't deal with name duplication.
- Step 1.2: Use the "usercache.json" in your minecraft instance. And look for your username there.
- Step 2: Wait for me to update the supporter list, which i will do asap.
- Step 2.1: Please send it through patreon because otherwise i can't really validate your support
- Step 3: Set the "update-supporters" config to true in the "config/PregenExpansionConfig.toml" or the "config/pregen/expansion.cfg" if you are using 1.2.0 patch on your client/server
- Step 4: Start the client/server, if everything worked the "config" should be set to false automatically, that's your indicator that it worked.

Once the config has been synced in 1 minecraft instance, all instances are automatically synced with it.
And a Internet connection isn't required either after it validated it.

If you don't find the Expansion Config, then you most likely haven't installed the expansion.
Basically all the features got moved into another mod, due to curseforge requesting it.
You can find the expansion mod here, or combined jars.
(These are the pregen posts and you find the latest releases there just scroll through the post until you find release attachments)

Also since it keeps getting asked:
1.19.3 is for 1.19.3 alone, while 1.19 is for 1.19.0/1.19.1/1.19.2

1.18.x-1.19.0 Specific Requirement:
- 1.18.x: Needs at the very least forge version 40.1.64 or newer
- 1.19.0: Needs at the very least forge version 41.0.110 or newer
Otherwise the mod will not be able to detect if you are a supporter or not...

Custom Servers:
If you are using custom Servers, you might not be able to use the expanded ranges or the other commands. This is due to how the 1.0 version was coded. It is not a bug, but a "Undefined Behavior" I have been using. The UI ("i" key) still allows you to use expanded ranges though.
This will be also addressed in the next patch.

Anyways, I thank anyone who reads this for the support :)

Have a nice time.