Hey Beowolfe, long time no see ![]()
Nice attempt at a save, however you've overlooked two things and had me draw out the Excel sheet, just to confirm my suspicions. Granted, I didn't check the actual numbers initially, I based it on a purely instinctual feeling. I've played long enough with this race, to have a gut feeling of what it's about. This, in my opinion, is exactly what you lack because of your inexperience at attacking.
The points are:
1) The game rounds up
2) Diagonal movement
1 - Rounding
Your table looks all nice and fine there, however you forget, that IC rounds up for travel times. (Infact your table is wrong). So for a 3 tick travel time in a straight line, say from 1,1 to 1,4 will be:
Camaar (200%) = SQRT (0^2 + 3^2) / (1+2) = 1. ......ie, 1 TICK (Why do you have 2?)
Camaar (150%) = SQRT (0^2 + 3^2) / (1+1.5) = 1.2 .....ie, 2 TICKS.
Custom (100%) = SQRT (0^2 + 3^2) / (1 + 1) = 1.5 .....ie, 2 TICKS.
Banker (0%) = SQRT (0^2 + 3^2) / (1 + 0) = 3 TICKS.
As you can see, the difference at 3 ticks is a whole tick already. This gets worse and worse as distance increases.
2 - Diagonal Movement
Related to rounding. Basically when you calculate the distance diagonally it introduces decimal places and isn't rounded. This then gets rounded up.
Case for 1,1 to 2,2 (ie, 1 tick diagonally):
Camaar (200%) = SQRT (1^2 + 1^2) / (1+2) = 1. ......ie, 1 TICK.
Camaar (150%) = SQRT (1^2 + 1^2) / (1+1.5) = 1.414 .....ie, 1 TICK.
Custom (100%) = SQRT (1^2 + 1^2) / (1 + 1) = 0.707 .....ie, 1 TICKS. <<------ (this is same for anything greater than 60% speed)
Banker (0%) = SQRT (1^2 + 1^2) / (1 + 0) = 1.414 .....ie, 2 TICKS.
Case for 1,1 to 3,3 (ie 2 ticks diagonally):
Camaar (200%) = SQRT (2^2 + 2^2) / (1+2) = 0.94. ......ie, 1 TICK.
Camaar (150%) = SQRT (2^2 + 2^2) / (1+1.5) = 1.13 .....ie, 2 TICKS <<-------------- (new camaar difference)
Custom (100%) = SQRT (2^2 + 2^2) / (1 + 1) = 1.414 .....ie, 2 TICKS.
Banker (0%) = SQRT (2^2 + 2^2) / (1 + 0) = 2.83 .....ie, 3 TICKS.
The difference exists when you factor it all in.
Also, to rebutt your other point - It's not uncommon for myself, or other attackers to send fleets beyond 3 ticks. Infact, it happens more often than not these days. So it's slowed down already vs attackers - and when the competiton gets heated, 1 tick or 2 tick difference in travel time, is telling.
Ofcourse, to reiterate, its a different playstyle and I said its still playable. Just based on what you want. Effectively they've sacrificed the Camaar's specialty of speed, in favour of Science to make it more like Custom. For me, it's always been about speed relativity. If you drop a custom speed to 75%, then I'm happy with 150%. If it's not, then personally, I don't think the -10% research is enticing enough to take 150% speed.
Like I said, I used to love Camaar and played them forever. But I won't with these changes - with Military research being fixed, people will be silly to not take 50% cons science, considering the value of that is only sacrificing a mere 50% speed.