by Mr Horizontal on Tue Jun 17, 2008 11:26 pm
The actual number of moons matters, because you need to be able to plan how many POS's to bring etc if you're going to spam the entire system or systems. Given corps can only deploy 1 POS per day per system, and alliances 5, this has to be planned quite well!
Could do symbols though I suppose, but I was thinking just put it next to the belt count ie:
Nonni*
0.51 (5/2)
C R F L
Where the 5 signifies the belts, and 2 signifies the moons.
No system has more than 50 moons (the maximum), so if you're going to fraction them, I'd suggest 0-16, 17-33 and 34+. But what tends to happen is you have roughly 3 systems in a constellations with lots of moons and the other 3 have few moons, kind of like the belts.
Here are several more reasons for moon counts:
- In Nonni, Litiura and Elonaya (for example) there are no moons available, so you want to see which system further afield is likely to have spare moons to put your POS up and plan your training for Scientific Networking according to how many jumps away it is.
- For 0.0, when planning where to put POS's, you might want to target systems with as few moons and as many belts as possible and put a POS in each of them, so attackers will have to get rid of your POS's before being able to put theirs up and claim sov.
- Finally in sub 0.3 lowsec it's a good idea to find a cluster of hard-to-reach lowsec with as many moons as possible to put a reaction chain in.
So in all it's about the same value as being able to look at the sec status (ie as close to -1.0 as possible for 0.0) and the belt count to see that the system in question is going to have some seriously good roids.