<!-- 1. START HERE: (Before filling all this out, please quickly go to the list of all issues: (https://gitlab.com/cable-mc/cobblemon/-/issues/?sort=created_date&state=all) and do a quick search to see if your issue has already been reported. If it has, please add a comment to the existing issue instead of creating a new one.)--> <!-- 2. If the issue was not already reported, please fill out the following template. --> <!-- 3. If you do not know something, don't worry! Just fill out as much as you can to make sure the issue can get fixed asap. --> ## Summary In Cobblemon 1.6.0 snapshots, when `Pokemon.clone()` is called, the method no longer generates a new UUID by default. This behavior differs from version 1.5.2, where a new UUID was automatically generated upon cloning. This seems like either a breaking change or a bug. ## Steps to reproduce 1. Call the Pokemon.clone() method on an existing Pokémon object. 2. Compare the UUID of the existing Pokémon with the UUID of the cloned Pokémon object. ## What is the current bug behavior? The cloned Pokémon object retains the same UUID as the original Pokémon. ## What is the expected correct behavior? The cloned Pokémon object should have a new, unique UUID automatically generated by default, as was the case in version 1.5.2. ## Cobblemon Version and Mod Loader Cobblemon: 1.6.0-SNAPSHOT (Git Commit: 7188978) Minecraft Version: 1.21.1 Fabric Loader: 0.16.9 ## Mods used besides Cobblemon None ## Additional Information The issue might have been introduced during a refactor of the `Pokemon.clone()` method.