[Dwedit]

This is a feature request or idea for a feature, and I might try adding it in. Feedback on this idea would be appreciated.

This would be an enhancement for FCEUX's code-data-logger, and would help with disassembling a game.

This feature would be for "Tags" on code to indicate what the code does.  It could either apply to all encountered code, newly discovered code, or code with/without existing tags.

Examples of possible usage:
You play Super Mario Bros.  You run Code-Data-Logger.
You want to log newly discovered code encountered while Jumping, so you'd set the tag to "jump", then jump, and all newly discovered code would have the "jump" tag.
Or you want to walk into a wall, and newly discovered code would have the "walk into wall" tag.

Then the Code/Data Logger tags and such could possibly be integrated into the debugger.

[FAST6191]

There is already something like this, though the reverse approach is taken and you do everything but what you want and then what you want and thus eliminate (or seriously reduce) all the always on routines.

Though it is more routine finding than something to make some kind of more human readable logs.