Originally by: Cookie

---

... like, your 'warp-to-gate' accuracy increases the more often you use that gate (or to make it easier to calc, just the system) .. and decreases when you haven't visited that system for a while.

---

Originally by: Cookie

---

nah, shouldn't be very much work.
Just get this 'Systems i've visited' to work like it should, set filter for like .. last 14 days or so, 15km minus #of visits = warp distance to gate.

---

Originally by: Spanker

---

And people would complain even more than they do now

---

Originally by: DeTox MinRohim

---

Originally by: Rells

---

Originally by: DeTox MinRohim

---

The big load is client-side, the server will only be there to verify the authenticity or on the BM creation part (The server creates the BM and send the copy to the client - not the other way around).

---

To authenticate the BM, the server would need to store as much data as it does now and you are in the same boat. Warping at 0km removes the NEED for instajump bms.

---

As you put it for another poster and although I would not want to offend you, you don't seem to have much more clue on some part of the concept.

The server is already storing the data and can handle it. The proof being that although having problems doing so at the moment, it IS handling it. Being a MySQL DBA myself and having a few table with a few million lines, I kind of have a clue of this: Loading one line in this table will always be faster than loading 1000 lines and so on. (if the table is rightly indexed of course) Faster sending the data back anyway as there is less data to send back.

Take example in Jita: 14 stations - 8 gates = (for the worst: Stations, Stations2Gates, G2G) = 182.
(For those who are wondering: (8x7)+(14x8)+14)

You come into the system via the New Caldari jump gate. The server must do a WHERE Jita and sends back to your client all the lines corresponding to you People and places to green color all your BMs that are in Jita...... THAT is a real problem.

Having this particular check client-side makes the server completly free of that. The server sits there waiting so no process hoag when the 10000 people/hour/jumps in the system.

The server is also free not only from loading the concerned BMs but also sending you the information when you enter the system. Less lag as less packets sended. Reminder : For less hacking paranoia, the BMs client side doesn't need the store the coordinates... only the BM name, id, and system/constellation/region IDs (or names - The note can stay server-side as you only see it if you edit the BM).

When you click "Warp to X"... you send the same information to server to load that ONE particular line... etc...

In conclusion, the server will always be less process hoaged by checking the authenticity of ONE BM you click and sending the warp command than sending the warp command and ALSO sending your greens wich it does for every systems you enter in... and for every people entering the system.

---

Originally by: Jim McGregor

---

Edited by: Jim McGregor on 31/08/2006 06:19:38

Originally by: Infinity Ziona

---

Additionally important, as has been stated numerous times by players, devs and myself, is the issue of vulnerability. The mass, speed and low slot count is supposed to be a factor in a ships class during travel but at the moment is being completely bypassed by instas jumps.

It was flagged as being THE PRIMARY issue relating to instas by Oveur. Not the DB. Refocus your attention on vulnerability and leave the lag and hardware to the people who can actually do something about it and who have a clue.

---

If they remove bookmarks just to make people slow as turtles when travelling, then I believe alot of people actually WILL quit. Im not saying its right, but people have gotten so used to instas that a replacement basicly needs to do the same thing.

Alot of people simply dont have time to spend 3 minutes per system when travelling. And equipping MWD's etc might work sometimes, but what if you cant dock and switch gear at your destination, before fighting?

---

Originally by: Spanker

---

Edited by: Spanker on 08/09/2006 11:45:44

Haven't read the entire thread, nor am I going to. Too long. But.

Say you remove instas and put in a warp to 0m feature on gates. That would mean everyone always warps to 0m. That, in turn, would mean that all gatecamps would use bubbles. That would mean everyone would die at a gatecamp since there's no getting away from it. And people would complain even more than they do now

---

Originally by: tookar

---

Edited by: tookar on 08/09/2006 22:03:21
It seems simple to me just remove the damn things and allow people to have 100 bm each . This is enough for any reasonable 0.0 resident . It would also stop bs fleets roaming the galaxy as fast as an interceptor . People should ONLY have strategic bm in their own space in 0.0 unless sacrificing mobility in their own space to have some bm space for enemy space .more static borders with more realistic outcomes in wars between vastly different numbers of players where there SHOULD be one clear winner but due to these game mechanics never will be!

Should 600 pilots no matter how skilled be able to resist 10000 pilots? Its ridiculous . Even the 300 spartans vs 4 million persians was really 5000 greeks vs maybe 100000 persians in a small pass .

The reason 0.0 combat is so stale is that no fights happen that are not just ganks as any force that is one half the size flees and fights just small ganks hopefully the removal of local and instas would make this game even more fun than it is .


PS . All you guys who want warp to 0.0 you do realise that EVERYONE will be travelling just as slow so maybe just maybe you wont have top jump 15 jumps to sell your stuff anyway .

---