Declarative approach

[SmalkiGroove]

Hey,

I was thinking of a better way to work on rom hacking, hear me out :

• every class that handles editing of some part of the ROM would have a task serializer and deserializer
• making a change to the ROM through the editor writes it into a local file as a YAML or other data format
• add a section to run a playbook from YAML file or text (or other) and it would perform the binary editing accordingly

If you are familiar with tools such as Ansible that is kinda what i'm thinking of, because when you lose or corrupt a ROM that you have spent days and days working on you don't want to restart everything manually on some editors you know.

Example of task :

tasks:
- kind: Ability
  id: 53
  data:
    mpCost: 50
    rangeAoeType: "weapon"
    effect-2:
      targets: "self"
      effect: "recover-hp"
...

or alternativerly use enum ineger values instead of strings but with a comment next to it to describe :

...
    rangeAoeType: 2 # line
...

Also that would be useful to share patches to other people. Thoughts ?

[Rurusachi]

I like the idea and I might implement something like this in the future. I initially considered something similar that would store the internal filesystem unpacked and only build the ROM as a separate action. But for now I'm slowing down development while I focus on another project I've put on hold for a while.