Please provide detailed Information about the Feature you would like to
see.
The Data Editor seems to be similiar to a Hex editor, but doesn't work the same
way. Currently when you target a file, it already has a value populated that
you just need to change to a provided value. I'd assume this is a string value,
not a memory location...but more on this later.
What if (at least for higher missions), you needed to aquire knowledge on a
filetype before you can edit them? You don't just open a file and throw in
random data at a random location IRL (and you'll rarely be provided this
information), you need to know what each byte does and means or you'll corrupt
the file.
You could do something like copy an RFC off a research server that explains the
filetype and fields. Then you could accept missions that require that file type
to be edited.
Then instead of just opening the editor and the old value is prepopulated, what
if based on the mission needs and knowledge of the filetype, you have to seek
to a specific address, then insert the desired value, BUT you have full control
over where in the file you seek and the new value. If you seek to the wrong
address and enter the right value, or the right address and enter the wrong
value, it corrupts the file (in the case of wrong address) or is changed to the
wrong value (in the case of right address, wrong value/data) and you fail the
mission.
Please rate the importance of your Feature Request *for others*
[Low|Med|High]:
[Low]
Original issue reported on code.google.com by frazerda...@gmail.com on 25 Oct 2013 at 5:49
Original issue reported on code.google.com by
frazerda...@gmail.comon 25 Oct 2013 at 5:49