S
secondadvent
Guest
Quick request (which I have probably asked before...): Could you implement an Enemy AI dump option? I know that you can currently just C/P to a text file and have it there, but the most important thing, and most annoying thing to add is the offsets, which is not included in the copied information.
I know that the copied info would be enough for most people's needs, but for me, I always like to have the offsets present so that i can know from a glance where the jumps are actually going, and also because I will be dumping every redone enemy script that I do, so that I can actually comment on stuff (hard to know why I did certain things if I go away for a bit and come back to a specific enemy and want to remove/compress stuff that I knew before couldn't be touched, costing me lots of lost time
), and create my own "pseudocode" for the AI, which helps even more (It is as if I disassembled it in PrC, but without it yelling at me for my coding style
).
You could even think of it as an extended copy button, that includes the offsets as well (doesn't have to output anything, just copy to the clipboard), and includes the final end opcode, though I am not sure how PrC would handle accidentally trying to import the offsets, I mean you could take the easy way and just tell people NOT to include the offsets, or tell your program to ignore anything starting with 0x###, though I am not sure how much it already ignores, how much work all of this would be, and how willing you would be to do it, but I would be VERY grateful for such a feature
.
I know that the copied info would be enough for most people's needs, but for me, I always like to have the offsets present so that i can know from a glance where the jumps are actually going, and also because I will be dumping every redone enemy script that I do, so that I can actually comment on stuff (hard to know why I did certain things if I go away for a bit and come back to a specific enemy and want to remove/compress stuff that I knew before couldn't be touched, costing me lots of lost time
You could even think of it as an extended copy button, that includes the offsets as well (doesn't have to output anything, just copy to the clipboard), and includes the final end opcode, though I am not sure how PrC would handle accidentally trying to import the offsets, I mean you could take the easy way and just tell people NOT to include the offsets, or tell your program to ignore anything starting with 0x###, though I am not sure how much it already ignores, how much work all of this would be, and how willing you would be to do it, but I would be VERY grateful for such a feature