Carm
   |
Posted - 2006.01.17 16:28:00 -
[1]
This is indeed a very good idea but there still are several problems :
1. A very old character could have charted any system in the world of eve and insta jump in any system. It does not sound realistic to me for several reasons. I will go in further detail later.
2. It would require huge amount of datas for each system you went to for each character.
About (1), I m not comfortable with definitive charting. We all know the universe is changing and although it changes slowly regarding the speed of the ships, the drift is, in my opinion, sufficient to justify that a system you didn't go through for a long time appears as if you never went there. So, I would prefer something based on the number of jumps in the last 2-3 weeks rather than an absolute number of jumps during the life of the character.
About (2), it's much more complicated and although your solution seems a very interesting one, I think this problem will keep it away from the code for ages ..
There might be a solution near to yours ... Let's imagine ...
There's a new skill : Jump charts
It allows you to store in your navigation computer the exact position of the objects in space you want (whatever could be the objet, gate or anything else) but :
- The number of such exact bookmarks is limited. You have 5 such bookmarks per level of Jump charts
- The precision is limited by how much you have worked on it (by working on it, I mean, using a "localization array", a skill, or just jumping over and over through it.
- The precision slowly decreases with time.
In Eve's interface, there will be a new folder in the bookmark area containing these insta's.
There's a last problem not adressed by this post, I grant you it would not solve the so called "BM abuse" but I think such a possibility would eliminate a lot of instas users, I find it personally painful to use instas and I would most probably throw away my instas library if there were such a solution.
If it isn't enough and if the great number of BMs is a problem (I stress IF) : Storing such BMs requires a lot of memory space (let's face it, you need to store the coordinates of the object at a given time and with an incredible precision, but you also need to store the complex equations that describe the movement of the objet in the given system. That does a hell of a lot of datas :)). That memory space could be a limitation of the ships or the character. This memory space could be upgraded with skills of course or augments if it's in the character / modules if it's in the ship.
If there was such a limitation, people would have less active bookmarks even if they still are instas.
To be completly coherent, inactive bookmarks should be less and less precise when time passes and region bookmark libraries would be obsolete in a few weeks and thus very hard to maintain. That would prevent people to share bookmarks. Staying a few minutes in a cargo hold would not be enough to have it loose a significant percentage of precision. That could easily be done by storing the date and time the bookmark was taken from the BM library and using it to modify its precision accordingly when it's put back into it.
Thus BM, instead of just storing a position, would store
- The position
- The precision of the position (read only when warping, written when a BM it's put back into the library or when something increases the precision: jump, jump chart scan, or ...)
- The date and time of last time it was taken from the BM library to a cargo hold or hangar (read when it's put back into the bm library, written when it taken from it)
Hope it's not to confusing ..
What do you think ?
|