Campaign Battle Frontiers My latest playtesting has convinced me to change the way ai attacks happen in the upcoming GSB campaign. Previously, there was a complex system involving local threat levels, which changed over time based on the strength of your fleet combined with the number of enemy-controlled systems linked to your world by hyperspace warp tunnel thingies. And that works fine, and its cool, and mostly staying. But what was happening was that you would conquer a system, push forwards and conquer the next system, and there was still a threat ‘behind the lines’ to recently conquered worlds. That was fine too, but I also coded a little ‘unlikely but possible sneak attack’ system whereby any of your worlds could get attacked at any time. If you didn’t have a big fleet sat there, this would be unopposed, you would lose the system, and maybe now have a gap in your supply lines. Frankly, in game terms, this is a pain in the exhaust-port. It’s frustrating and annoying to lose a system behind the lines, and it’s wasteful to keep a fleet in every system just in case. The good old ‘pushing-back the frontier’ system is better. I’ll keep the gradually lowering threat level thing, but ditch the sneak attacks. Once you have conquered a world, and parked a big-ass fleet there for a few turns, you can mvoe on and not fear losing it. It is, after all, a big map to conquer. On an unrelated note, can whoever codes the cursor stuff at ATI get their shit together please? Multiple monitor setups in windows 7 are basically chaos with an ATI card. Random cursor corruption when swapping monitors, and an invisible cursor if it goes into text carat mode and back again on the secondary montior… These are not new bugs, from what I read, so why are you tweaking drivers to get an extra 1 FPS on starcraft when you should be fixing basic windows functionality? Bah!