A possible optimization is memoizing or caching a lot of planning, depending how the AI works; in one of my (low calibre) games, I found the AI replanning a lot of what it had done before; recalculatinf scoring of the same targets, etc; I changed it to try and think numerous turns ahead, and cache whatever coudl be cached, and then during certain operations of opponents or itself, it'd 'dirty' up some of the cache, causing those parts to recalculate; ie: try and minimize the amoun
skeezixcodejedi
I had it rotated so it was perfectly horizontal/vertical, to try and minimize the chance for error. Eithe way, it makes no sense that 9 would go northeast, and 1 would go south instead of southwest; regardless of how mis-angled they are, they have to be ordinal .. opposite key is opposite direction :) And this is a quite easy thing to code, relative to other things like AI etc; so presumably the boys are working on the hard real game impacting stuff first,. but hopefull
Keys dont' map to directions right :) I encountered this early on, seemed weird, but thought maybe map rotation was to blame; I just discovered the menu option to disable snap-back, so I could rotate so the grid is nice and horizontal/vertical .. no angles. Press say '9' to go north-east, works; then press '1' say to go south-east. Try the various reversals.. they don't work consistently. ie: I just did '7' to go northwest, and then '
Govern -> Details -> Details - >Details .. (hit it a few times, since it appears to do nothing) Exit the Govern screen.. oh, theres the Details panel... 3 times. Dismiss, dismiss, dismiss.. there we are, back to map. So not sur eif Details should pop up on top, or behind.. if on top, woudl be okay; if behind, well, dont' pop up more than one :) jeff
Windows 7, beta 2. Run the gane, but dont' do anything; let the screensave kick in. It does, audio stops; wiggle mouse to wake things up, and FE is blackscreen crashed.. have to alt-tab out and kill it :) jeff
Just an FYI for stardock support team .. When creating an account, you can enter any old password; it would seem the database storage truncates the password to 12 characters, but later comparisons do _not_. So if you enter a 15 char password, it stoes 12. If you then try to authenticate with 15, it _fails_, and the user has no idea why. If the user guesses that it has been truncated to 12, it then work