Not a bad idea, but I think it would be too much for players to remember. (for me at least
)
I am roughing out a flexible OoB system with Rod and DH, it will take some time to implement but just may satisfy all.
However it is contingent on stable SQL... if we get the kit source it may be doable, even if not, we still have not seen a high playerload test on an OP server running on a Linux hosted MySQL db...
I just got the parts for a second server PC today, I just need to get it built and get the current stable fedora distribution installed (I forgot to get cd blanks...
it needs 4...). I want to run the next SQL test on a Linux hosted db, we may find we don't need the source to fix SQL after all... (though it would still be nice).
The same strategy could be employed with the flatfile too, but would require periodic server shutdowns for OoB maintenance. (and would take me longer to develop)
The ideas that Rod, DH and I are exploring involve laying out the OoB for limited ships in a config file and then use it to count the total number of limited ships in the db (owned and unowned) and add or remove ships as necessary. (One possible strategy, which can account for trade-ins)
The idea is that the limited ships will be available to anyone with enough dough to buy it, when they run out, you'll have to ask a teamate to trade his in to give you a turn in a limited ship.
No promises here, but I intend to do this and am confident I can make it work.