PUPPET MASTER 0.4.4 BY REDZERGLING — BETA PLAYTEST

Install the same 0.4.4 ZIP and dependencies on every player's machine. Keep config
values identical; the new global player/summon damage multiplier defaults to 0.2.
The multiplier applies to the survivor and all summons EXCEPT Horizon Rail, which
retains its original full damage. Support healing calculations are preserved.
Existing configuration values otherwise remain intact.
Primary proc coefficients are 0.2 per hit; damaging summons use 0.5, except
Horizon Rail which retains 1.0. Healing is not an offensive proc attack.

NEXT HANDS-ON CHECKS
1. Start a normal run. Test movement, sprint, jump, firing up/down and summoning.
   The support hand should hold underneath the rifle and release for commands.
2. Check the five loadout slots and their alternatives; every skill has its own
   icon. Bind Extra Skill 1 to the desired side mouse button if needed.
3. Play several stages, including a boss. Judge whether 20% of the previous damage
   makes the army too weak or still too strong, with the rail turret restored to
   full strength. Record difficulty, items and skills.
4. In co-op, test both host and client as Puppet Master. Each player's puppets
   should inherit only their owner's items, obey their commands and respect caps.
5. Test stage transitions, player death and reconnects. Look for lingering puppets,
   duplicate summons, disappearing models, animation issues or excessive slowdown.
6. Ping a farther enemy while a nearer one is available. Your attacking summons
   should focus your ping; your friend's summons should follow their own order.
   Test both host and client. Summon more units while an order is active.
7. Re-ping the same enemy to cancel, then try another enemy, a ground ping and an
   allied ping. Only enemy pings should focus attacks. Dead targets release focus.
   A visual ping fading does not cancel the order. Check cover and range limits;
   mobile units pursue, turrets wait for a clear/in-range target, healers heal.

The automated test notes in VALIDATION.txt document local-server checks. Remote
multiplayer and sustained normal-run balance/performance require the above tests.

REPORTING A PROBLEM
Save the profile's BepInEx/LogOutput.log and note the mod version, skill choices,
items, stage/difficulty, and whether you were host or client. Describe how to repeat
the issue. Keep a copy of the previous release ZIP for rollback.
