Well, we're only a month into widespread availability of Civ4, and one of the DG's long-standing problems is being solved. We have always given our Designated Players a somewhat onerous task of recording everything they do. We get varying degrees of information depending on how much time the DP has, whether he/she agrees with the "record everything" philosophy, how much the chat is bugging them, etc. Most of the time the chat log is presented as a play log, which just doesn't give the people who want details what they want.
Others also see the same need for logging during Succession Games, the difficulty in Civ4 in alt-tabbing to another program, and the Python based design, and you get the perfect opportunity to actually automate this stuff.
Enter the autoevent logger mod. Take these files and put them in your customAssets folder in the mygames tree, and out pops a log of the things you do playing the game.
Rather than inundate eotinb with individual requests, let's decide here if we want to require DP's to use this logging feature, and what things we want to see in a DemoGame log. Then we can either collarborate with eotinb on adding the features we want into the mod, or build a special version ourselves (giving him credit for the initial idea of course).
Others also see the same need for logging during Succession Games, the difficulty in Civ4 in alt-tabbing to another program, and the Python based design, and you get the perfect opportunity to actually automate this stuff.
Enter the autoevent logger mod. Take these files and put them in your customAssets folder in the mygames tree, and out pops a log of the things you do playing the game.
Rather than inundate eotinb with individual requests, let's decide here if we want to require DP's to use this logging feature, and what things we want to see in a DemoGame log. Then we can either collarborate with eotinb on adding the features we want into the mod, or build a special version ourselves (giving him credit for the initial idea of course).