The Carrier Update

[Teerin]

I addition to a cool-down time, and perhaps instead of having a fuel requirement, make it have a fee like /pimpship does. That should discourage excessive use, but allow this functionality to be employed for dire circumstances.

What has to be kept in mind is realism, and player interaction. Realistically, your example ship [LN]-LNS-Pine.Ridge would probably almost always have its four fighters docked when not in combat. So if you ignore the fact that example snub [LN]-Bob.Marley logged in docked at Norfolk Shipyard in New York, it could be legitimately assumed that he instead logged in docked on the carrier over in New Hampshire. So that part is good

While it saves time and hassle for the pilot of that fighter, and such a distance isn't so bad, imagine if instead [LN]-Bob.Marley was docked on Southampton Shipyard in New London. Yesterday, he assisted the BAF| in a counter-raid. But skipping all the way from New London to New Hampshire? Had he flown, he might have had an inRP (or PvP) encounter with another player along the way. That's gone now. Sure, he still gets to go raid Rheinland with the carrier and their friends, but this factor must be considered.

I don't know if a range limit could be implemented or how. If basing /requestdock on what system the fighter/bomber or carrier is in proves to be to complex, how about requiring this; "the carrier, strikecraft, and the base the strikecraft is docked on must all be of the same ID."?

---

---

"You see what your knowledge tells you you're seeing. ... how, what you think the universe is, and how you react to that in everything you do, depends on what you know. And when that knowledge changes, for you, the universe changes. And that is as true for the whole of society as that is for the individual. We all are what we know, today. What we knew yesterday, was different; and so were we."
- James Burke, The Day the Universe Changed (1985)