http://feuniverse.us/t/fe8-the-grand-eventing-wiki-chapter-construction-guide-wip/1594
This wiki
if we had better buildfile tools than event assembler then it would be easier
i think we can generalize these two approaches to the ābuildfileā (āsource codeā?) approach and the āin placeā approach. Klok mentions the problem of āconvertingā to EA, but thatās the wrong way to think about it ā you donāt really āconvertā an existing project to using an EA buildfile (you may s well just start from scratch). A buildfile is just āsome computer-readable description of āthis is how i get my final project from the base ROMāā. To āconvertā a FEditor modified project to an EA buildfile would probably be a lot of work, since weād have to come up with ways to serialize the internal FEditor data structures into EA-friendly data (work for this exists, but FEditor doesnāt keep track of diffs so weād need to figure out how to figure out whatās in vanilla and what isnāt).
Itās also worth noting that these two approaches are not mutually exclusive ā you can write a buildfile on top of an existing working ROM perfectly well; this is how the most recent builds of EN were developed (with a buildfile that treated āthe last EN revisionā as āthe base ROMā). It is much more difficult to do the reverse, because the whole point of a buildfile is that there is no working ROM, thereās just āthe base ROMā and āthe buildfileā.
Having a nice GUI is of course preferable to not having one, and having a tool generate EA buildfiles or something would be fantastic. What people are missing, though, is that having a machine generate these for you (even based off of some graphical representation of a project) by necessity requires making some assumptions about the projectās internals, which is inherently less flexible. How is some prebuilt GUI tool supposed to understand how, say, Misakaās portrait mod works? Sure, someone could write that in now, but what if I (or circles, or colorz, or whoever) comes up with some radical new thing that changes how some other underlying data is represented? EM, or whatever would be completely in the dark as to how to serialize these new data structures (Lexou has talked about how itās possible to deserialize these by examining the in-ROM routines, but I donāt think itāll be so easy to write a system to do the reverse for arbitrary data). Yeah, you can work around that somewhat by making your GUI tool expose some easy hooks for people to write their own modules, but we were already talking about how thereās a shortage of tool developers?
To add to this topic there are also a few other tools for this.
One, thereās UPS2EA if you just want to take your current Hack and make it truly base everything off of a base ROM.
Two, for just text edits, I do have a Text Ripper, which you then can edit text entries in a text editor and re-insert with EA. It is, however, not very polished nor does it output in one big file as circlesās textprocessor would prefer.
I know colorz said FE8 is preferable, but, i will ask this anyway: Will EM work with FE7?
Lexou has put a lot of work into supporting all of GBAFE.
EM works with FE7, if youāre interested in modding old tech.
thanks.