eve online travel time calculator

DOTLAN EveMaps

• EVE InGame Browser

• Sovereignty
• Faction War

Navigation Tools

• Jump Planner
• Route Planner

Route Options

Avoid system/region, jumpbridge network.

• Add waypoints first

Avoid Region/System List

• Nothing to avoid.

Load/Save Route

[more stats] most violent systems (3 hours), [sovereignty changes] top sov changes (7 days), [alliance movements] alliance movements (7 days), donate / support dotlan.

A route planner for EVE Online that supports Ansiblex jump gates and wormhole connections.

Shade Orblighter

A resource for new Eve Online players

DOTLAN Tutorial: Planning Eve Routes

By Kshal Aideron

https://evemaps.dotlan.net/jump is the page that will help in planning Eve routes. On DOTLAN you can find this under the “Navigation” tab.

IMPORTANT: Choose the ROUTE PLANNER option in the list of Navigation Tools. If you leave it on the default option, you’ll be setting a jump planner which is something that we’re not covering in this article.

Today we’re going to plan an Eve route from Jita, the Caldari trade hub system to Dodixie the Gallente trade system.

Step One: Under the route planner, add the system you’re leaving from. In this example, we’ll be leaving from Jita. Click the add button.

Step Two: Add the system you want to travel to. In this example, we’ll be heading over to Dodixie, the Gallente system trade hub system. Click add.

Step Three: Choose route option. You can choose “fastest” which may take you through LowSec or NullSec. If you want to stay 100% in high sec, then make sure to check this option. In my example, I’m fine with going through Low since I’ll probably be flying in an interceptor. Unless a gate camp has an insta locker, I’ll be too fast for anyone to lock up and stop from warping off.

Step Four: Click the “Go” button to get your route.

If you have several systems where you’re going to pick things up, or drop things up, you can add each system to the route list and DOTLAN will give you the route you’ll want to follow.

Multiple Waypoints on Your Route

So I’m currently in Jita and I need to pick up several things in a bunch of different systems. I want to go only through HighSec. This is how I’d enter all of the stops I want to make:

So how do you do this in game? In the search bar, type in the first system that you want to go to.

Add this as a destination. Then look up your next destination and add it as a waypoint. If you add it as a destination, it will clear your last desto and add the one you just added as a new destination. So make sure to to always use WAYPOINT if you want multiple destinations.

Avoiding Flying Through a System

If there is a system you really want to avoid, you can add that on the route form as well. I’m going to leave the route options as “prefer highsec” and avoid Uedama, a known gate camping system. Lets see what happens.

When I look at the route that I planned, even though I have “prefer HighSec” it’s still putting me through 1 system of Low because there really is no option to stay 100% in High Sec when travelling Jita to Dodixie.

Now, of course, I will have to decide when planning Eve routes, if going through LowSec is a better risk then trying to get through Uedema. Of course, I can always check Eve Gatecamp Check to see if there’s been any kills on the Uedema gate lately!

Want to see what other 3rd party websites you can use for Eve Online, check here .

Eve main: Kshal Aideron Corp: FUN Inc NPSI community FC and newbro queen

Related Post

Getting to incursion focus with dotlan and jump clones, voice chat software used in eve online, dotlan tutorial: map resources for pi, leave a reply cancel reply.

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

This site uses Akismet to reduce spam. Learn how your comment data is processed .

3 Years of Eve Rookies

Is eve online worth playing in 2024, celebrating 2,000 members of eve rookies.

Tripwire is an open source wormhole mapping tool, hosted for free to the public, built for use with EVE Online .

FREE for a limited time!

Have an account? Log into Tripwire now!

Tripwire in 2024.

Detailed information about Tripwire updates will be posted on the Tripwire Discord and in the update thread on the Eve Online forums .

Some highlights from 2023 releases: improvements to automapping, wormhole selection dropdown (1.22), FW data, map and options updates (1.23), Thera and Turnur data from Eve Scout (1.24). As well as all of the map changes and new ships that CCP add.

Tripwire is also now an official CCP Partner Programme community app!

Tripwire in 2023

Tripwire continues to receive feature updates (in 1.20, it got one click return, an EVE time indicator and closest way home cues from K space) and maintenance (when CCP change how ESI works, or changes the map).

Please consider helping fund the server maintenance or contributing to development so we can keep this resource going and up to date!

This login method requires that you first create a Tripwire account via User Registration .

Forgot your login? Use SSO method instead .

Username can contain spaces

Password is case sensitive

Remember me

This simply enables corporate Tripwire administration for your character. You must first complete User Registration .

Character must have one of these roles: CEO, Director, or Tripwire Admin

We are a small team of IT professionals that have come together to provide us all with a more enjoyable EVE experience. We each have many years of industry experience and an active life but still try to find some time to dedicate to this project. We hope you enjoy!

Daimian Mercer

Natasha Donnan

All Eve Related Materials are Property Of CCP Games EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.

This Privacy Policy governs the manner in which Tripwire collects, uses, maintains and discloses information collected from users (each, a "User") of the tripwire.eve-apps.com website ("Site"). This privacy policy applies to the Site and all products and services offered by Eon Studios. Personal identification information We may collect personal identification information from Users in a variety of ways, including, but not limited to, when Users visit our site, register on the site, and in connection with other activities, services, features or resources we make available on our Site. Users may be asked for, as appropriate, name. We will collect personal identification information from Users only if they voluntarily submit such information to us. Users can always refuse to supply personally identification information, except that it may prevent them from engaging in certain Site related activities. Non-personal identification information We may collect non-personal identification information about Users whenever they interact with our Site. Non-personal identification information may include the browser name, the type of computer and technical information about Users means of connection to our Site, such as the operating system and the Internet service providers utilized and other similar information. Web browser cookies Our Site may use "cookies" to enhance User experience. User's web browser places cookies on their hard drive for record-keeping purposes and sometimes to track information about them. User may choose to set their web browser to refuse cookies, or to alert you when cookies are being sent. If they do so, note that some parts of the Site may not function properly. How we use collected information Tripwire may collect and use Users personal information for the following purposes:

• - To improve customer service Information you provide helps us respond to your customer service requests and support needs more efficiently.
• - To personalize user experience We may use information in the aggregate to understand how our Users as a group use the services and resources provided on our Site.
• - To improve our Site We may use feedback you provide to improve our products and services.
• - To send periodic emails We may use the email address to respond to their inquiries, questions, and/or other requests.

How we protect your information We adopt appropriate data collection, storage and processing practices and security measures to protect against unauthorized access, alteration, disclosure or destruction of your personal information, username, password, transaction information and data stored on our Site. Sensitive and private data exchange between the Site and its Users happens over a SSL secured communication channel and is encrypted and protected with digital signatures. Sharing your personal information We do not sell, trade, or rent Users personal identification information to others. We may share generic aggregated demographic information not linked to any personal identification information regarding visitors and users with our business partners, trusted affiliates and advertisers for the purposes outlined above. Third party websites Users may find advertising or other content on our Site that link to the sites and services of our partners, suppliers, advertisers, sponsors, licensors and other third parties. We do not control the content or links that appear on these sites and are not responsible for the practices employed by websites linked to or from our Site. In addition, these sites or services, including their content and links, may be constantly changing. These sites and services may have their own privacy policies and customer service policies. Browsing and interaction on any other website, including websites which have a link to our Site, is subject to that website's own terms and policies. Changes to this privacy policy Tripwire has the discretion to update this privacy policy at any time. When we do, we will revise the updated date at the bottom of this page. We encourage Users to frequently check this page for any changes to stay informed about how we are helping to protect the personal information we collect. You acknowledge and agree that it is your responsibility to review this privacy policy periodically and become aware of modifications. Your acceptance of these terms By using this Site, you signify your acceptance of this policy. If you do not agree to this policy, please do not use our Site. Your continued use of the Site following the posting of changes to this policy will be deemed your acceptance of those changes. Contacting us If you have any questions about this Privacy Policy, the practices of this site, or your dealings with this site, please contact us at: [email protected] This document was last updated on January 27, 2017

We'll counter-attack as soon as we properly outnumber them

Eve gate is temporarily unavailable, in the meantime we can recommend the following sites to keep you entertained:.

Keep yourself up to date with the most recent news, Dev Blogs and events from EVE Online.

Twitter is a rich source of instantly updated information and you can read the latest tweets from the EVE team.

Catch up on the latest EVE Trailers, Alliance Tournament, Fanfest and behind the scenes videos from CCP Games.

The official wiki to support EVE Online. This resource is the one stop center for all information relating to EVE.

Tune into the DJ’s who play non stop music for the masses.

Explore killboards, forums and even player-created tools like EVEmon.

Even when the EVE forums are down, EVE Search allows players to read the most recent EVE Online forum threads.

Alternatively you can  visit some of our Fansites from around the world including Starfleetcomms in the UK , EVE Germany , EVE Russia , EVE Hungary and EVE Denmark .

Thank you for your patience and please come back later when the EVE website will be fully functional. Facebook and Twitter will have the most up to date information regarding the status of our website.

To help with event planning, here is a quick converter between time-zones.

Note that as various places switch to/from daylight savings time, these may be an hour or two off, worst-case. It is good practice to give times and dates for all events first in EVE Time , with converted local times included afterwards if at all. Individual players are best-placed to convert EVE Time to their local timezone while accounting for local timekeeping quirks.

• 'plus' is ahead, 'minus' is behind
• 'midnight' is counted as part of the previous day
• does not include daylight savings time

Online tools

You can also use various online tools to get an overview of how your own (and others') local time maps to EVE Time: e.g. The Personal World Clock or EVE Online Time Converter .

See EVE Server Time page for how to add a second time zone clock for Eve Server Time (UTC) on Windows.

• Getting Started

Navigation menu

Personal tools.

• Login with EVE SSO
• View source
• View history
• Recent changes
• Random page

EVE University

• Alliance Auth
• Editing Guide
• Categorization
• What links here
• Related changes
• Special pages
• Printable version
• Permanent link
• Page information
• Browse properties
• This page was last edited on 31 May 2022, at 05:29.
• Content is available under Creative Commons Attribution-ShareAlike unless otherwise noted.
• Privacy policy
• About EVE University Wiki
• Disclaimers

Long-Distance Travel Changes Inbound

MAKE SURE TO READ THE UPDATES IN APPENDICIES B AND C

Hi everyone,

We are about to make some significant changes to how long-distance travel in various forms works in EVE, with the aim of significantly increasing minimum travel times between two arbitrary distant points, most particularly in regards to jump drive and portal based movement. The overarching reason for this is that the current ease of movement has shrunk the practical dimensions of New Eden considerably, to the detriment of the game experience.

Why this?/Why now?

• Nullsec is stagnant and needs a change. This is the first of many steps in our plan.
• Big fights are cool, but they’re crowding out more accessible and more frequent smaller ones.
• These changes have positive implications for people not involved in sovereignty warfare, for example making use of capitals in lowsec less risky.
• We expect the impact of these changes to be emergent, and as a consequence are unpredictable and will take a while to develop on TQ. This plays into our longer-term plans, as you’ll see in a second!

How do these changes fit into the Nullsec plan?

As we’ve previously discussed at Fanfest, in our recent forum post , and in the premiere episode of The o7 Show , a group of developers here at CCP has been working on Nullsec and associated game systems with the goal of releasing a series of changes to shake up the status quo and improve the overall state of Nullsec. We are planning to deploy changes over several phases, which will each provide specific improvements individually while also fitting into one greater whole.

Phase One contains the long-distance travel changes, as well as some other associated changes planned in Phoebe in November. These changes are not intended to be a silver bullet to fix all of Nullsec’s issues in one fell blow. Instead, they represent a significant improvement to specific areas of concern for Nullsec (and Lowsec) while also setting the stage for the later changes.

Phase Two is focused on medium-term changes to the ways that organizations capture and hold Nullsec space and infrastructure. We are working with the CSM as we firm up our plans for this phase and as we develop internal prototypes. It is during this phase that we expect to make greater progress towards smaller and more diverse Nullsec holdings. It is too early to go into great detail about what these changes will contain, but currently most of our conceptual prototyping has loosely fallen into categories that could be described as “occupancy-based” systems and more “freeform” systems that decentralize sov to focus more on control of the individual pieces of infrastructure. As we continue this investigation we will be working closely with the CSM and following all appropriate player feedback.

Phase Three is the stage that CCP Seagull discussed in the EVE Keynote at Fanfest this year . This stage is intended to build upon the changes that we are planning for starbases/structures and corps/alliances in 2015, changes that will open up new possibilities for more dynamic warfare and more granular control of territory. This phase is also intended to lead quite deliberately into the future through our vision for player-built stargates.

By splitting the task of improving Nullsec into manageable chunks, we are ensuring that we get you the best changes as quickly as possible rather than holding back needed updates. We’re happy to be getting the first significant chunk of these changes out to you all later this year.

What is changing?

We are going to allow capital ships to use gates in lowsec/nullsec, and we are aiming to make gate-to-gate travel take less time than jump travel over distances of more than ~20 LY. We've run simulations for capital ships travelling between arbitrary pairs of systems, and settled on the target movement speed of no less than 3 minutes per lightyear for travel over 20 LY. This should allow us to bring about the main change we want to see – less sustained use of jump travel – while still preserving its value for short bursts of movement.

How is this going to be achieved?

The primary change is the addition of a new mechanic, called "jump fatigue".

Jump fatigue is tracked for each character, persisting between play sessions and over downtimes as appropriate.

Every time you use any jump drive, jump bridge or jump portal (hereafter all treated as "a jump"; note that this does NOT include stargate travel!), you will accumulate jump fatigue. If your fatigue is below 1 before a jump, your fatigue will be 1 + (light years travelled) after the jump. For subsequent jumps, the fatigue is multiplied after each jump by 1 + (light years travelled). This stays on the character as mentioned earlier, and decays at a rate of 0.1 per minute.

After a jump is complete but before your fatigue is increased, you gain a jump cooldown timer. The length of this timer is a number of minutes equal to your jump fatigue (before being increased by that jump!), and you are unable to make another jump of any kind until this timer expires. Note importantly that, because fatigue decays at a slower rate than a cooldown timer, you will retain fatigue for a length of time after your cooldown timer expires. Additionally, there is a minimum jump cooldown of 1 + (light years travelled) minutes. (See Appendix A for examples.)

The status of both your fatigue and your cooldown timer will be displayed in the timer bar in the upper left corner of the screen:

In addition:

• Almost all jump-capable ships will have their range reduced to 5 LY after skills; this is both necessary to allow us to not penalize short-distance travel in a cleaner way, and also as a goal in and of itself to constrain the distance covered in single hops. . (Note that jump portal range on a ship is always the same as its own jump drive range.)
• As above, capital ships will be able to use stargates, but will for the time being they will still be barred from entering Highsec (that is a larger discussion that we would like to revisit in future).

You will only be able to move your medical clone to the station you are currently docked at. This prevents obvious movement workarounds with suicide-cloning.  (If your clone contract is revoked by the station owner, we are keeping the current behavior that it is moved to your home system as defined in the character sheet.)

Hitpoints and resistances on various sovereignty-related structures will be revisited, to balance out the reduced ability to use Supercarriers against them. Stay tuned for a follow-up blog on this.

We will be releasing a collection of other smaller changes in Phoebe that will be of interest to many of the same people who are affected by these travel changes. These include a rebalance of starbase weapons, a rebalance of stealth bombers and heavy interdictors, enabling of lowsec doomsdays, and changes to interdictor bubble mechanics. More information to come.

What's not changing?

• Starbase jump bridges already have a 5 LY range, so they don't need range adjustments.
• We are hoping to leave skills as they are for the initial release; we will likely readjust them in the near future, but we want to see how behavior settles down first.
• Jump clones are being left alone for the time being. We are likely to want to revisit them once the initial changes shake out, the use of ship caches becomes clear and so on, but they serve a diverse enough set of purposes (null-null movement, null-highsec movement, implant swapping etc.) that we don’t want to make major changes too quickly.

What's being special-cased?

• Jump Freighters and Rorquals will gain a role bonus: 90% reduction to effective range jumped for the purposes of all these calculations, but will otherwise get all the described changes. This means that, for all the math we’re doing on this feature, whenever we use the range jumped as a variable we first multiply it by 0.1. We will still likely want to revisit the logistical power of these ships in future, but for now we want to bring them into the new system without nerfing them too hard.
• Black Ops ships will have their range unchanged, but will otherwise get all the described changes.  This also keeps the range of their jump portals unchanged. We don’t feel that Black Ops range needs adjustment right now.

What are the anticipated consequences?

In the short term, we would anticipate a reduction in the degree to which the average non-trivial capital fight escalates, and the number of parties involved. This seems likely to increase the frequency of capitals being deployed in small-scale engagements, in both lowsec and nullsec.

Over the medium term, we see the potential for more substantial changes in the nullsec status quo as the various competing parties work to adjust their internal objectives to the new situation; it seems plausible that the general reduction in travel capabilities will lead to more localism, but we don't want to make any firm predictions in this area. We're confident that these changes improve the overall system of lowsec and nullsec gameplay and take them in better directions, but any set of changes that would allow us to accurately predict their consequences would by their nature be too simple to be interesting for very long.

What's next?

• We will be actively participating in the comments thread of this blog and listening elsewhere around the internet.
• These changes will be appearing on the Singularity test server in the next couple of weeks.
• We anticipate shipping them in Phoebe, which comes out in November.
• We are expecting to make follow-up adjustments in Rhea, in December.
• The medium-term shake-out of these changes will be very impactful on sovereignty-system changes we are anticipating making next year, so we are expecting to revisit all this again as the work on those changes progresses.
• Greyscale, on behalf of the Nullsec Working Group (Scarpia, Fozzie, Ytterbium, Rise, Bettik, Delegate Zero, Masterplan and Nullarbor)

**** Update: As mentioned above, we're taking feedback and responding in the thread, so look for those blue bars. Greyscale has also created a short FAQ that will be updated as needed as the first reply to the thread.

Appendix A – Examples

Little Bobby Tables is sitting in his Archon in UJY-HE in at the top of Deklein, just after the Oceanus release. He wants to travel to Atioth, at the bottom of Geminate, which is around 50 LY as the space-crow flies. He consults a popular jump planning service, which gives him a route of four jumps and 53 LY. He’s travel fit and has max skills, so his jump range is 14.625 LY and he’s expecting to be limited primarily by the session change timer. The journey takes him around two minutes.

A month or so later, he’s back in UJY-HE, and Phoebe has just shipped. His Archon’s jump range is now 5 LY. He consults his jump planner, and finds that his route is now 12 jumps and 54 LY. He hasn’t jumped anywhere since the release, so he has no jump fatigue.

His first jump, of 4.85 LY, takes him to U-TJ7Y. Because he has no fatigue before the jump, he gains a minimum-length jump cooldown timer: 1 minute, plus 4.85 minutes for the distance travelled, for a total of 5.85 minutes, or 5 minutes 51 seconds. He also gains a jump fatigue value of 5.85.

He waits for just under six minutes. In this time his jump fatigue decays down to 5.27. He then makes his next jump – 3.57 LY to LEK-N5. He gets a 5 minute 16 second jump cooldown timer, because his fatigue was 5.27 when he jumped, and his minimum timer would be 4 minutes 34 seconds based on range travelled. He then gets a fatigue increase after the jump. Because he travelled 3.57 LY, his fatigue is multiplied by 4.57, taking it up to 24.06.

He waits out his timer, which also reduces his fatigue to 23.53. After his cooldown timer expires, he makes his third jump, to RO0-AF, a distance of 4.19 LY. He gains a jump cooldown timer of 23 minutes 32 seconds, and his fatigue is multiplied by 5.19, up to 122.14.

After waiting for 23.5 minutes at the convenient local station, his fatigue is down to 119.79. He jumps again, to 2R-CRW – 4.9 LY. At this point his cooldown timer is 2 hours 2 minutes 8 seconds, and his fatigue is 706.74. At this point his total distance travelled is 17.51 LY, leaving him with 37.04 LY to go. He looks at his map, and finds a 40-route jump through nullsec to get to the same destination, and figuring two minutes per system, his warp travel time for the whole journey is a bit over half the cooldown for his next jump. He decides to fly there directly rather than trying to jump any further.

The next week, he finds he needs to take his Ark from HED-GP to 373Z-7, at the bottom of Stain. It’s been long enough that his fatigue has entirely decayed, so he’s starting fresh again. He plots the route, and sets off.

First jump takes him to 5-N2EY, 4.73 LY. Because his jump freighter counts distances as being 10% of their actual distance, he incurs a minimum timer of 1.47 minutes, or 88 seconds. His fatigue similarly becomes 1.47, dropping to 1.32 while he waits out the delay.

He jumps again when his timer expires, to 4NBN-9, a 4.88 LY jump. His timer after this would be 79 seconds, but because this is a longer jump his minimum is 89 seconds (1.488*60). His fatigue is multiplied by 1.488, taking it to 1.97, and then dropping back to 1.82 as he waits out the timer.

This continues until he reaches 373Z-7, with a total journey time of around 7.5 minutes, and a jump distance of 22.3 LY.

Appendix B - Frequently Asked Questions

Can supercapital ships use gates after this change?

Does this make it too difficult for new pilots to get out into 0.0?

Yes, it probably does. Following further discussion after publishing this dev blog, we have come up with the following additional feature:

For players less than thirty days old, once per player corporation joined, or For all players greater than thirty days old, once per year:

You may push a button in your corp interface (while a member of a player corp and docked) that:

• Moves your medical clone to a station designated by your corporation, and
• Then moves you to the (new) station containing your medical clone

The exact method of corporations designating the target station is still being ironed out, but it will involve at the very least being able to designate a default station for all corp members and will likely be allowed for any station with a corp office, regardless of system sec status. This seems to us like it solves the "I want to recruit people to Nullsec" concern, and also gives non-Nullsec recruiters an easier way to get genuinely new players to the right location quickly and easily.

Is the balance for Black Ops final?

No. Please give feedback!

Very large fatigue values will take a loooong time to decay, is this too much?

Possibly yes, we'll have a look at this.

Does a titan providing a bridge gain fatigue when people jump through it?

No. Only if the titan itself jumps.

Is the ability to push your fatigue up to really high numbers a good idea?

Probably not, no. We're looking at just capping fatigue at 1 month.

Appendix C - Updates

Conclusions we have reached through this exercise:

• The ease of nullsec logistics permitted by jump freighters, and to a lesser extent jump bridge networks, is not aligned with where we would like nullsec industry to be.
• It is however, pretty well aligned with where nullsec industry is right now. As we improve the status quo for industry in nullsec, we will want to reevaluate this balance along with the impact potential changes would have on logistical work for other areas of the game.
• We're pretty happy with the impact of the proposed changes on the movement of non-covert combat ships, as it relates to both jump drives and jump bridges for all ranges.
• We're not overly concerned about the battle rorqual; if it starts being used in a widespread fashion we will nerf it, but we're not expecting this to happen.
• We're also not overly concerned yet about High Grade Ascendency equipped capital fleets, since such capital movement would be very vulnerable to disruption and because it relies on very rare items. If this becomes a widespread usage pattern we will likely take action, and we'll be keeping a close eye on everything surrounding capital movement after Phoebe.
• Black ops are working in a generally OK manner on TQ right now, and we want to minimize harm to their use with these changes.
• We don't like repeating decimals.

Therefore, changes we are making to the previously-announced plan:

• Jump freighter max range will be bumped up to 10LY, and they will keep the 90% fatigue-distance reduction. This represents a slight range reduction compared to TQ so some cynos will need to be repositioned, but otherwise leaves them largely alone. Note that, because ranges multiply together for fatigue purposes, one 10LY jump is substantially less fatiguing (multiply by 11) than two 5LY jumps (multiply by 36). Rorquals will stay at 5LY/90%.
• All ships designated as having a "hauling" role in ISIS (i.e. the following ship groups: Industrial, Blockade Runner, Deep Space Transport, Industrial Command Ship, Freighter) will similarly get a 90% reduction to distance counted for the purpose of fatigue generation. Obviously they can't jump themselves, but this does apply to the use of bridges or portals.
• We are adding some additional code to allow us to put a bonus on jump portals that reduces fatigue generation for all ships jumping through that portal. This will be applied to Covert Jump Portals, with a value of around 50% (subject to further tuning). This means that all ships using a black ops portal will generate less fatigue.
• We're going to bump the max range of black ops ships up slightly to 8LY, and likewise give them a ~50% fatigue bonus.
• Finally, we're slightly nerfing the skill Jump Drive Calibration from 25%/level to 20%/level, and tuning base ranges accordingly. This allows us to give most capital ships a base range of 2.5LY, rather than 2.2r LY, and still hit our max range targets. More work on these skills will probably be done in future, this is just minimum changes necessary to get these changes on TQ so we can see how they play out in practice and establish how comparatively valuable their different bonuses are.

For more details on these updates, please see this forum thread .

Essential Posts

Patch Notes - Version 21.05 # 2

EVE Online Directors’ Letter

Insurgencies Intensify - Havoc Update

Community Beat for 19 January

Get Ready for the Anger Games 6

Targeting time / Locking time - Calculation

According to EVE University , and I quote:

To calculate the locking time (in seconds):

So, in the following scenario, we have an Astero (attacker) and a Venture (the target), pretty simple. What we need to calculate the targeting time, is Astero’s scan resolution (620 mm) and Venture’s signature radius (40 m). By doing the calculation above for this scenario, it results that the locking time would be 0.04 seconds, which is totally wrong. I want to find out how to calculate correctly the targeting time. Does anyone know how it really works?

I just put that formula into excel, and it gave me 3.36 seconds using the Astero locking a Venture example. Also tested using some of the other example in the graph on the E-Uni web page, and it seems consistent.

The excel-formula I used was =40000/(B6*ASINH(C6)^2)

Where B6 is the scan resolution (in mm) and C6 is the Signature Radius (in m).

Learn to calculate. The answer is around 3.3 seconds.

The REAL answer is " 3.3 seconds PLUS the time needed after decloaking which is 5 or 6 seconds depending on cloaking skill".

Oh, yes. I did it wrong. Now I see is actually 3,359 seconds. Thanks guys.

It is important to remember to round up to the next second with lock and warp times due to server ticks.

So, the calculated lock time of 3.### in practice means you lock it in four seconds if you have low ping.

Alternatively, and because a tie goes to the runner, so to speak, and again due to the way ticks and commands are dealt with, the Astero can lock any venture which takes five seconds or more to warp, assuming each actor clicks their respective commands (lock, warp) on the same server tick.

What i dont get is where did the unit of seconds come from If the formula only uses distances.

scan resolution itself should be something/second as unit i guess

not as dpi or anything just scanned volume per second or something

Because thats the time of a server “tick”, it only processes data on each tick, its why anything with a sub 2 second align time is considered an instawarp because regardless of scan res it takes 2 seconds for you to lock and actually activate a module on a target as anything under a second is rounded up to a second, and lock time doesn’t use distances, it uses signature radius, aka how fat the target is, the lower the sig the longer the lock time and the higher you need to boost your scan resolution for it to counter that difference

Just came upon this thread and saw people mentioning how if you warp sub 2s you’re apparently safe from getting locked, keep in mind that’s not true.

If you have sub 2s (but above 1s) align time, you can still be locked, pointed, and caught before warping if there’s someone on the gate with all of high enough scan resolution, quick human response time (and proper overview setup to help), and also very importantly, low latency to the server. With a setup like that, you can semi-reliably catch everything unless it’s cloaky (since that’s done at the 1st tick/second, not after 2s, so you’d need to decloak them by proximity too), or it has sub 1s warp (which very few specific setups have).

Here’s an additional resource about it: http://eve.501gu.de/misc/travelceptor_vs_instalocker.png

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Travel Time Calculator

Quick links, travel duration calculator.

Travelmath provides an online travel time calculator to help you figure out flight and driving times. You can compare the results to see the effect on the total duration of your trip. Usually, the flight time will be shorter, but if the destination is close, the driving time can still be reasonable.

Another popular tool is the time difference calculator, which can be used to check the time zone change anywhere in the world. This is especially useful if you're making international calls, since you can find the best time to schedule your phone call.

Home  ·  About  ·  Terms  ·  Privacy