You are correct! I never zoomed that far out. :) Disregard bug post. Foul
FoulFoot
I usually play with only a single star (the AI can't seem to handle multiple stars very well...), so maybe that's the problem. Foul
It doesn't work on randomly-generated SP maps. The planet is never created. Foul
Allied AI player's Titan froze in one of my systems. The Titan had been attacking another AI player, when I swooped in and nuked the planet with my fleet. I colonized the planet. The AI Titan then just sat immobile, for quite a long while. I built several Gauss cannons around it, as well as a thick minefield, as I intended to attack my ally shortly and wanted to get the drop on the Titan. Before declaring war, I moved my fleet through the minefield, and was
Captain Bizarre -- There's problems with the auto-build-on-resource option. If you turn it off, you should be able to play normally until this is fixed. ~SDC~
Erm... CariElf, not to sound dense... but what's your e-mail address? I poked around but couldn't find it. Foul
Tried a second game, and have the exact same problems. This time, the resources are in separate sectors. I'm unable to mine the resource, and the random 3-sector-warning message keeps popping up. I've got auto-build-on-resource turned on, and prompt-to-upgrade-starbase turned off. If that helps any. Foul ~SDC~
The first game I tried was fine, but in my current game... All sorts of problems with starbases. Two resources are within 4 squares of each other (there's three squares between them), but I could only colonize one of them. The other gives the message about being too close. This shouldn't happen, regardless of how close they are. I destroyed the first starbase, then built on the second resource successfully. Shortly thereafter, my starbase was wiped out. I was then unable
That solved it for me too. Incidentally, if you re-enter your serial number, click on another tab besides Dregin.net, then tab back to Dregin.net, your serial number will have disappeared again. You'll be registered for the current session, but you'll need to re-enter your serial number for each subsequent session. Annoying bug, but at least we can get the updates. ~SDC~
I've read several threads here of people not being able to see the 1.02 patch -- happening to me too. I've tried switching servers, made sure I'm logged in, etc. It's still showing that 1.01a.333 is the newest version, with no update avail. ~SDC~