Animation Frame Packer and Unpacking.

[DatMoshu]

Animation Packing & Unpacking System

Overview

This PR introduces a robust system for exporting (packing) and importing (unpacking) animations in UOFiddler. It allows users to easily transfer animation data between UOFiddler and external tools by converting complex UO frame structures into standard PNG sprite sheets with accompanying JSON metadata.

Key Features

1. Pack Frames (Export)

• Functionality: Converts the selected animation (or all actions for a mob) into a single PNG sprite sheet and a JSON descriptor file.
• Customization: Users can configure the export via a new PackOptionsForm:
  • Directions: Choose which facing directions to export.
  • Layout: Define maximum sprite sheet width or force "One Row Per Direction" for easier manual editing.
  • Spacing: Adjust padding between frames.
• Output: Generates anim_{body}_{action}.png (sprite sheet) and anim_{body}_{action}.json (metadata).
• Metadata: The JSON file preserves critical data for every frame, including:
  • Direction & Index (Frame order)
  • Frame bounds (X, Y, Width, Height on the sheet)
  • Center point (The "pivot" or "anchor" of the frame, essential for correct alignment in-game)

2. Unpack Frames (Import)

• Functionality: Reconstructs animations from the exported JSON and PNG files.
• Process:
  • Reads the JSON to locate frames on the sprite sheet.
  • Extracts pixel data and rebuilds the UO-specific palette (16-bit A1R5G5B5).
  • Restores the exact Center points for every frame.
• Conflict Resolution: Prompts the user to either Overwrite existing frames or Append to them.

3. Bulk Unpack (Batch Import)

• Functionality: Automates the importing process for an entire directory of animations.
• Workflow:
  • Scans a selected folder for *.json files.
  • Parses filenames (expected format: anim_{body}_{action}.json) to automatically map data to the correct Body and Action IDs.
  • Global Overwrite: Asks the user once for their overwrite preference (Yes/No/Cancel) and applies it to the entire batch, preventing popup spam.
  • Error Handling: Skips invalid files or mismatches gracefully, providing a summary report (Imported count vs. Error count) at the end.

Technical Implementation

• AnimationListControl.cs:
  • Added OnPackFramesClick: Handles the export logic, sprite sheet generation using GDI+, and JSON serialization.
  • Added OnUnpackFramesClick: Handles single-file import.
  • Added OnBulkUnpackFramesClick: Implements the directory scanning and batch processing loop.
  • Refactored UnpackAnimation: A core helper method that performs the actual file reading, bitmap extraction, and memory insertion for both single and bulk modes.
• Data Structures:
  • Introduced PackedOutput, PackedMeta, and PackedFrameEntry classes to strictly type the JSON data.
• Palette Management:
  • Implemented BuildPaletteFromFrames to dynamically generate an optimal 16-bit palette from the 32-bit source PNGs during import, ensuring visual fidelity is maintained when converting back to UO's format.

How to Test

1. Pack: Right-click an animation in the list -> "Pack Frames". Select options and save. Verify the PNG and JSON are created.
2. Unpack: Right-click an animation -> "Unpack Frames". Select a generated JSON file. Verify the animation loads correctly in the viewer.
3. Bulk: Place multiple exported animation files in a folder. Right-click -> "Bulk Unpack Frames". Select the folder and confirm the batch processes correctly.

[AsYlum-]

Overall looks good. Minor changes needed.

[AsYlum-]

This can probably be reverted. Formatting changes in unrelated file.

[AsYlum-]

Could we move this to Forms directory?

[AsYlum-]

Is this needed?