Mhm I think you're missing the point. You seem to think this is a tool created to read data from released games created by others. It really isn't. We're using it during playtests to record players playing OUR game. Other developers (hobbyist, indie - I would expect big studios to have their own tools for this sort of thing) could benefit from this.

The tool can (and does in the case of UDK) run on a server...or just client if it is not an online game at all (it is not bound to multiplayer games) We've tried this and it worked fine (one PC acted as server, client and did the logging with several clients connected)

You also seem to think I will try to sell or license such a tool? That is not the intention, if the tool is ever released at all, it would be open for the (UDK) community to use.

Finally, I had another look at the post I made on our site, and I cannot for the life of me see how I pretended to have something revolutionary, just something I wanted to share (part of my graduation) and see if other (indie) developers had any interest in for their own games.

p.s. I will look into the text on our site about triple-A, thanks for the feedback.

ButchDean, on 25 April 2012 - 04:07 PM, said:

I have not yet tried it with another game or genre. The benefit of using it for different genres would be obvious. The main obstacle is engine support to export the entire level as a mesh. UDK supports such a feature and can export to .fbx which can be imported inside the tool at runtime.
Any game/engine should be able to output text data to a log, so I see no problems there. An example of what this could look like:

[0016.82]:[PlayerStatus]:Name=Preatorius:Pos=-96.00,-1152.00,46.61
timestamp:eventtype:name:position

I will continue working on it and improve the abstraction to hopefully make it useful for non-UDK games. (I am not sure how common it is for editors to be able to export their level to .fbx (without textures, just plain geometry))

ButchDean, on 25 April 2012 - 03:55 PM, said:

We are creating a game, this tool was created to analyse our playtests. The tool however is not designed to only work with our game and could be used for any genre to review all gameplay events that occured during a session (or merge all sessions and create a heatmap)