Hi guys, I've been thinking about this... I think it is possible to 'triangulate' silo locations using the hit event. Imagine a fighter flying along and a silo shooting at it. The silo has a certain shot frequency and the hit event tells you how often a shot impacts the fighter. But... the hit frequ...

Thanks Martin, I hope you do continue working on Joshua. At some point Grace will need a playmate... I've been thinking about how to make the Fight activity work. This will be used for task groups made up of some mixture of battleships, carriers and subs fighting some other mix of battleships, carri...

Yes, it would be good to be able to access the shots.

A partial solution is the Hit event - you can at least tell that your units are getting shot. I don't know any way to access the data behind each shot though - shots don't seem to appear in the data returned by GetAllUnitData().

cheers

Thanks Trickser... I expect that Grace is going to rely a lot on heatmaps. As I'm defining it, each heatmap is a 36 by 20 grid of 10 degree squares. For example here's map[land] (a box represents a 1, no-box represents a 0) which tells Grace where her fleets can't go: http://img517.imageshack.us/img...

Hi all, Hopefully I'm not too late for this bot party... I'm working on a DEFCON bot called Grace (named in honour of Grace Hopper). I'm using the Lua framework by Peter Cawley. Things are at a pretty early stage, but the intelligence within Grace will be distributed in a roughly hierarchical manner...

Disclaimer - I'm not an expert DEFCON player, but based on a few games played, and few more observed these are my notes on the important factors that determine a winner in 1v1 play. At the end I've tried to think how they might be applied to writing a bot. Any comments/criticisms welcome. Primary fa...