It should be possible to increase (or decrease) your shield recharge rate when you are in a specific system.
Basically, you place a self-destructing spob* in the system, and in its OnDestroy field, have it give you the recharge outfit. To have the outfit removed properly, you'll want to add a fires-every-day cron** to remove the outfit. Make sure the spob regenerates every day, so that it can re-give you the outfit if you are still in the same system after one day has passed.
If you were really fancy, it might be possible to fake a near-planet effect, by placing a self-destructing spob with a short-range weapon near the spob you want to have have the effect, and having it also trigger a mission when it dies. That mission would call in a self-destructing ship, and when that ship appeared, it would remove the outfit and resurrect the spob, which would destroy itself again if the player was still in range. Wash, rinse, and repeat.
This effect could also be extended to other outfit types, even...
...weapons. A weapon that you can only use when you are near a particular spob. That would be cool.
---------
*To make a self-destructing spob, give a spob a low strength value, and also give it a very long range planet-type weapon. When the player enters the system, the spob will fire at them, regardless of whether or not they are flying a planet-ship, and it will destroy itself, triggering its OnDestroy field. See my Guide to Spob-based Weapons for information on how to make a spob fire at the player.
**Perhaps this would be an actual use for the bugginess of crons? I seem to recall Guy listing bugs in that resource, including the following:
" pre hold off is 0 and duration and post holdoff are both positive (cron never terminates and executes OnEnd every day for the rest of your life)"
It seem that this would be perfect for this sort of application, assuming it hasn't been worked around in the 1.0.9 update. (The famous always-existing crons from the Nova scenario, which always appeared in the pilotlog with negative numbers, and blocked most news from appearing in the Bar, are no longer showing up in my pilotlogs. However, I have tested identical crons in a testbed scenario, and for the first few days, at least, they work exactly as Guy outlined above. :huh: )
----------
I'm sorry if none of the above made sense. It's late here, and I tend to make inaccurate assumptions about how well people can follow my train of association when I'm tired. Just tell me you can't understand a word I said, and I'll post a more detailed explanation tomorrow.
Edwards