SkiesGenerator

Fixed

• Generators no longer stop working after a restart. A generator whose location failed to resolve on load (its world was unloaded, renamed, or deleted) was registered as a "phantom" generator. The generator task then hit a NullPointerException on location.clone(), which aborted the entire tick loop every tick — silently stopping all generators, not just the bad one.
• The generator task now processes each generator in isolation: a single invalid or misbehaving generator is logged and skipped instead of halting every other generator.
• Invalid entries in generators.yml (null location, or a location whose world can't be resolved) are now skipped during load with a clear warning that names the entry. Entries are left in the file in case the world returns later, so no data is lost.
• A null/unresolved-world location can no longer be registered as a generator from any code path (GeneratorManager.createGenerator now rejects them).

Changed

• Load-time warnings for bad generators now include the offending entry name and the underlying error message, making it easier to find the culprit in generators.yml.

Removed

• Removed a redundant, discarded Generator construction during load that also caused the stored generator UUID to be ignored in favor of a random one.