Using unique constraints
 

From tick 211 to 216 there were several planets with coords 200:4:2, would be nice to avoid that in the future.

Re: Using unique constraints
 

:up:
(It was only two, btw.)

Re: Using unique constraints
 

(Still a bit odd)

Re: Using unique constraints
 

(No, that was in fact quite even)

Re: Using unique constraints
 

There were 3 planets at tick 211.

200 4 2 "Pandemonium" "Zeus" Ter 30 14490 14490 0
200 4 2 "hilltop" "bluefish" Ter 30 14530 14530 0
200 4 2 "red" "redfish" Ter 30 14530 14530 0

Re: Using unique constraints
 

(I think you'll find I've just been proved correct)

Re: Using unique constraints
 

There were only two when I finally got Cin to fix it!

Re: Using unique constraints
 

in tick 211 there was 3x 200:4:2 and 2x 200:4:25
in tick 212 there was 2x of both 200:4:2 and 200:4:25
in tick 213 to 216 there was 2x 200:4:2

Re: Using unique constraints
 

Have you fixed the bug then?

Re: Using unique constraints
 

it's not a bug, it's a new feature being tested

Re: Using unique constraints
 

And it happens again, now there are two planets with rulername BotRuler1 och planetname BotPlanet1 =\

Re: Using unique constraints
 

It's a feature, you can set multiple farm planets and hit them all at once with one single fleet. \o/

Re: Using unique constraints
 

It seems who ever coded the botname generations didn't do that correctly and it doesn't check for existing names, something which isn't a very good idea, for very obvious reasons

Re: Using unique constraints
 

Well if PA's database would be designed correctly this wouldn't be an issue.