You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ColorzCore A FE8 -input Main.event -output HACK.gba -startOffset 0xB2A610
(this, of course, assumes that support for the -input <file> syntax (as opposed to -input:<file>) is implemented).
The -startOffset <offset> option would set the initial value of CURRENTOFFSET/whatever to <offset>, instead of the default 0.
This would have a mostly two advantageous effect (that come to my mind):
Allows tools that call EA externally for installing small chunks of events (such as FEBuilder) to not have to use workarounds through generating an "installer" file.
Waay in the future, when we'll consider outputting objects/asm in addition to raw binary, since ORG FreeSpace shouldn't be a thing anymore, it will allow us to properly differentiate hooks (sections that need to go at specific fixed offsets; maybe we could encode those with special names and/or just throw errors since those shouldn't really exists in standard relocatable objects anyway) and regular relocatable data (.text/.rodata-like sections).
🤔 All things considered that's actually not that potentially useful, but given that the amount of effort that would go into implementing such feature is probably fairly small I think it won't hurt to have it anyway at some point.
The text was updated successfully, but these errors were encountered:
Example:
(this, of course, assumes that support for the
-input <file>
syntax (as opposed to-input:<file>
) is implemented).The
-startOffset <offset>
option would set the initial value ofCURRENTOFFSET
/whatever to<offset>
, instead of the default 0.This would have a mostly two advantageous effect (that come to my mind):
ORG FreeSpace
shouldn't be a thing anymore, it will allow us to properly differentiate hooks (sections that need to go at specific fixed offsets; maybe we could encode those with special namesand/or just throw errors since those shouldn't really exists in standard relocatable objects anyway) and regular relocatable data (.text
/.rodata
-like sections).🤔 All things considered that's actually not that potentially useful, but given that the amount of effort that would go into implementing such feature is probably fairly small I think it won't hurt to have it anyway at some point.
The text was updated successfully, but these errors were encountered: