Alright, some words to tell you than I didn't forget about this tool.
Working for a small local society have its advantages... except when the said society have a big project to achieve and everybody, boss included, turn into code monkeys. In short, I didn't really had free time the last few months, and the few I had, I didn't really felt like writing lines of code since it already was what I did every single second of the day.
But, yes I don't forget this tool. I'm still working on it, even if lately it was more in my mind than everything else. I'll go on holidays next week, and when I return I should have enough time to effectively work on it.
I don't know how many time it will need, since I'll have to redo the whole viewer's interface, but I've probably found a workaround which will let you do something near to "copy this to the console". I'll also add more customization (font, color and size), to the viewer and to the configuration interface ; and think of a way to make this also available via a configuration file for those who want to keep the configuration from a game to another. Then I'll start to works on the "save on file" feature.
In the same time, I'll add the attributes stored in __slots__ and not just in __dict__. To my knowledge, there's not a single game which use it, but still it's not a reason to not use check it.
I'm also searching a way to deal with object which aren't stored directly in an attribute/variable but in a list or a dict. At first I found it useless since, for 95% of the games, the object is firstly stored in a variable, then added to the list/dict. But then I crossed a game which don't do like this and felt frustrated because of this, so...
This said, it's really not an easy thing, I can't just pass through the list/dict, I also need to keep a copy of the object to address it more easily, and also split the values displayed to make them clickable independently of the rest of the list/dict. And all this will increase the interactive elements displayed on the screen, making it more slower than it can already be when a lot of data are displayed.
So, I also probably have to find a way to alternate between interactive/not interactive, to work around this problem... I've an headache just writing it and don't guaranty that it will be effectively implement one day.
Well, it was more than just "some words"... Sorry for the month without update and good holidays to those who've this chance.