Dragonlings

[2.1.1] - 2026-04-08

Added

• /dragonlings give <player> <type> — Spawns a tamed dragonling in front of the target player, applies Tamework tame/owner, and links it to the Dragon Whistle when Tamework is present (permission dragonlings.give). Accepts short names (green, blue, red, purple), aliases, full role ids (e.g. Dragonling_Green), or other registered NPC role names.
• Per-variant tame limits — Configurable maximum tamed dragonlings per color per player (defaults: 4 each for green, blue, red, purple, and template pilot). Natural taming and /dragonlings give both enforce the cap; a translated message is shown when the cap is reached.
• Persisted tame accounting — Counts are stored in tame_counts.json under the plugin data folder: incremented when a tame completes (Tamework Custom effect after tame, or after a successful give), and decremented when a tamed dragonling dies (DeathComponent), so limits stay correct regardless of chunk load.
• Tamework hooks — TwInteractionConfig Tame entries use custom requirement dragonlings_tame_cap (pre-tame check against stored counts) and custom effect dragonlings_tame_cap_record (post-tame increment), registered via reflection so the mod still loads without Tamework on the classpath.

Changed

• Tame cap configuration — config.json in the plugin data directory exposes MaxGreen, MaxBlue, MaxRed, MaxPurple, and MaxTemplatePilot (integers, default 4). If config.json is missing, defaults are applied and the file is written on first start so it can be edited directly.
• Purple dragonling void projectile damage — PurpleVoidProjectilePhysicalDamage in config.json sets absolute physical hit damage for the purple variant’s void orb (default 20.0, minimum 0). When this differs from the default, a patched copy is written under generated/Server/ProjectileConfigs/ in the plugin data folder and registered as a separate projectile asset. Restart the server after changing this value so it can be preloaded.