--- [Request] Add Macro Action Recorder

[TrevorAvrett]

Record the steps the users took to make the map cache edits. Save the macro recorded actions instead of a .map patch. If user copies a float, int, double, etc, the macro records where from, (rather than the exact value, so the action can be reused across all builds/maps) then wherever the user pasted that information. If the user types a value, or toggles a flag, then that is recorded. etc etc.

[photo is an Adobe Illustrator Rendering of what I mean]

Results:______

---

Across Maps:___

-Saves user from repeated, tedious/time consuming processes for more forward research progression for any map of a Halo game across any build

-Faster changes for casual realtime-lobby poking fun

As .Map Save/patch substitutes:______

-A Workaround for .map patching or .maps no longer working with newer updates of MCC (save the macro recorded -abridged version of history of changes made to the map rather than the map itself so the process can be reapplied to the updated map file) that may be necessary unless 343's update change patterns can be predicted and accounted for, (additional, injected Tags must have a source folder to pull the other reference from)

-Future-proofs Assembly from having to keep up with updates or changes between retail console and PC, (and/or other),

-Abridged macro saves could serve as an effective workaround for modders to port their mods from retail directly to PC or vise versa