MSH TAG v1.2 -- independent tester handoff
=========================================

Local automated checks do not close the original Windows setup report or establish
four physical controller support. Please return observations from the final v1.2
download, including failures. Do not patch a previously patched ZIP.

Choose one path
---------------
Two humans on Fightcade: use clean Euro 951024 msh.zip. Extract the two-player
patch package and drag the ZIP onto msh-tag-v1.2-preview.cmd. It writes
msh_tag_v1.2.zip beside the original, plus a receipt. Back up Fightcade's existing
msh.zip, then copy the output to Fightcade\emulator\fbneo\ROMs as msh.zip.
Both players must use the same v1.2 patch and agree on whether to include the sky.

Four humans on RetroArch: extract the MSH TAG RetroArch package. Put clean Euro
951024 msh.zip beside PLAY MSH TAG 4P.cmd, then run that launcher. It makes
msh4p.zip and launches the custom Arcade (FinalBurn Neo - MSH TAG) core. Keep
the filename msh4p.zip. Set four different Device Index values for ports 1-4:
P1/P3 are one team, P2/P4 the other. The stock FinalBurn Neo core is not this path.

For either path, optionally put your clean mvsc.zip beside msh.zip before patching
to add the double-team sky. Without it, the stage stays. Record this choice.

Installation observations
------------------------
- Record Windows version, emulator/core version, chosen package and patch receipt.
- Time the setup from extraction to the first fight. Record every unexpected prompt,
  unclear step or failed action, including cmd.exe and drag-and-drop behavior.
- Confirm the clean parent remains unchanged and the output filename is correct.
- Test a second launch, and upgrading with an older msh4p.zip plus a clean parent.
- For Fightcade, verify an actual online match with the same patch on both sides.
- For RetroArch, confirm the title includes MSH TAG and each of the four controllers
  has its own port. Return a result from the UI, not just a core-only script.

Gameplay observations
---------------------
- Automatic HP+HK tag attack: stand-block, crouch-block and neutral on both sides;
  repeat from an air tag. Neutral should be hit; Hulk can deal native block chip.
- Perform an ordinary jumping HK before and after tagging. Its native overhead rule
  should remain. In 4P, hold the incoming teammate's own attack during entry too.
- Hulk crouching HP: test close and tip range against standing/crouching Spider-Man,
  Psylocke, Iron Man and a large opponent, both sides. A connected first strike should
  lead into the launcher; a first-hit whiff should keep the original second-hit reach.
- Play repeated CPU opponents, KO while tagging out, draw/rematch and continue.
  Check that a dead bench fighter stays out and the original opponent stays beaten.
- Tag repeatedly with Blackheart projectiles and Captain America's shield active;
  check object ownership, colors, Daily Bugle reflections and HUD stability.
- New partners should have empty gem slots. Activate Soul Gem while hurt, tag to
  a hurt partner, and check that healing continues. Check KO versus DOUBLE K.O.
- Try LP+MP+HP in blockstun (pushblock) and QCF+MP+MK with one level (snapback).

Four physical controllers
-------------------------
P1/P2 join with HP+HK and select both team picks. Check independent P1/P3 and P2/P4
ownership through tag-out/tag-back, simultaneous double-team input, KO handoff,
rematch and continue. Record all four device models and their mapped ports.
Start/Coin lines are absent in the 4P wiring, so Start-based taunt and gem cycling
are unavailable. This is separate from running-gem carry, which v1.1 repaired.

Flicker report
--------------
The user reported Fightcade; RetroArch is unknown. The linked September 28 footage
predates v1.1. If flicker occurs now, record an exact clip timestamp, v1.2 receipt,
stage, both teams, what flickers (fighter/HUD/background), renderer, Vsync, shaders,
fullscreen/window mode and display refresh rate. A brief old clip alone does not
identify a cause or prove that the current patch still has the issue.

Please return: setup time, pass/fail for each tested item, exact reproduction inputs,
and clip/receipt details for failures. Leave items you did not test marked untested.