These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Wormholes

 
  • Topic is locked indefinitely.
Previous page12
 

Wormhole timers,

Author
Jack Miton
School of Applied Knowledge
Caldari State
#21 - 2013-06-25 12:30:44 UTC
it's 5 min.
it's not 4 min.
it's not 4m27s.
it's 5 min.

you end up with a ~4:30 timer because it takes ~30sec to do the round trip.

no, the session timer is not 30s, but it was 3 years ago.

There is no Bob.

Stuck In Here With Me:  http://sihwm.blogspot.com.au/

Down the Pipe:  http://feeds.feedburner.com/CloakyScout

Evangelina Nolen
Sama Guild
#22 - 2013-06-25 12:38:36 UTC
it is 5 minutes. How has this not killed me by now I'll never know.
Nathan Jameson
Grumpy Bastards
#23 - 2013-06-25 12:39:07 UTC
While the rest of you were armchair quarterbacking, I was out and busily testing and recording timers on different types of wormhole connections:

H296 (C5->C5): 5 minutes
E175 (C5>C4): 5 minutes
X877 (C5>C4): 5 minutes
N766 (C4>C2): 5 minutes

Each link above connects to a screenshot showing the timer on the third-jump polarization message. As Jack Miton has stated, there are an additional 20 seconds for the session timers, plus approach-time and general syncing.

SCIENCE, BITCHES!!!

http://www.wormholes.info

Nebu Retski
Lead Farmers
#24 - 2013-06-25 15:51:47 UTC  |  Edited by: Nebu Retski
Nathan Jameson wrote:
While the rest of you were armchair quarterbacking, I was out and busily testing and recording timers on different types of wormhole connections:

H296 (C5->C5): 5 minutes
E175 (C5>C4): 5 minutes
X877 (C5>C4): 5 minutes
N766 (C4>C2): 5 minutes

Each link above connects to a screenshot showing the timer on the third-jump polarization message. As Jack Miton has stated, there are an additional 20 seconds for the session timers, plus approach-time and general syncing.

SCIENCE, BITCHES!!!

**** yeah I was right, it's an 8 bit counter giving you 4m26s (rounding down instead of up) for the timer. Just need to add the session change timer to it Blink

EDIT:
ooh pity I just noticed the last picture has 4m28s Sad. Pretty stupid amount for the timer if they don't use an 8bit counter.
Nathan Jameson
Grumpy Bastards
#25 - 2013-06-25 16:20:10 UTC
Nebu Retski wrote:
EDIT:
ooh pity I just noticed the last picture has 4m28s Sad. Pretty stupid amount for the timer if they don't use an 8bit counter.


It's...it's almost like...they can program whatever number they actually want.

http://www.wormholes.info

Nebu Retski
Lead Farmers
#26 - 2013-06-25 18:32:53 UTC
Nathan Jameson wrote:
Nebu Retski wrote:
EDIT:
ooh pity I just noticed the last picture has 4m28s Sad. Pretty stupid amount for the timer if they don't use an 8bit counter.


It's...it's almost like...they can program whatever number they actually want.

Shocked no way, how?

Seriously though, for optimization purposes, with that timer (~258 seconds) it would be wise for them to use an 8 bit counter (e.g. unsigned char = 8 bit counter -> 0-255) because it reduces their data foot print for WH timers to be 2-4 times smaller (on 32 bit software a short = 16 bit and an int = 32 bit). For the amount of data that the servers need to handle I would consider that every bit of data reduction would be a nice thing to have, but that of course doesn't mean CCP thinks of such things.
Svodola Darkfury
Federal Navy Academy
Gallente Federation
#27 - 2013-06-25 19:03:58 UTC
Nebu Retski wrote:
Nathan Jameson wrote:
Nebu Retski wrote:
EDIT:
ooh pity I just noticed the last picture has 4m28s Sad. Pretty stupid amount for the timer if they don't use an 8bit counter.


It's...it's almost like...they can program whatever number they actually want.

Shocked no way, how?

Seriously though, for optimization purposes, with that timer (~258 seconds) it would be wise for them to use an 8 bit counter (e.g. unsigned char = 8 bit counter -> 0-255) because it reduces their data foot print for WH timers to be 2-4 times smaller (on 32 bit software a short = 16 bit and an int = 32 bit). For the amount of data that the servers need to handle I would consider that every bit of data reduction would be a nice thing to have, but that of course doesn't mean CCP thinks of such things.



The hell are you talking about? It's 300 seconds. 5 Minutes. There is travel time, session time, and load time. That's why you don't see 5 minutes. What you're talking about is optimizing the tiniest bit of data usage on the whole server. My KEYBOARD runs a 5 minute timer without lag.

Svo.

Director of Frozen Corpse Industries.

Nebu Retski
Lead Farmers
#28 - 2013-06-25 19:59:36 UTC  |  Edited by: Nebu Retski
Svodola Darkfury wrote:
It's 300 seconds. 5 Minutes.


If you would check each of the pictures in Nathan Jamesons post above you would see that every picture has a timer at 4m26s, 4m23s, 4m24s, 4m28s

Add 20 seconds for 2 session change timers and some delay's between clicking jump, that comes pretty damn close to 5 minutes ;). I simply stated earlier that it looked interesting to me and that it looks like they use an 8 bit counter, but I can't say for sure if that is what CCP does or not.

Svodola Darkfury wrote:
What you're talking about is optimizing the tiniest bit of data usage on the whole server. My KEYBOARD runs a 5 minute timer without lag.

Your keyboard doesn't run the most advanced gaming universe, it barely does anything so it's not very difficult to run a timer on it. For heavy duty servers on the other hand it pay's off if you can use simple systems to reduce every data usage and a decent programmer should never have an issue using something like a 8 bit counter for a timer (let alone coming up with it).

But to make it clear to all of you that are aggressively set to the 5 minute timer, I'm not stating that CCP uses an 8 bit counter to give you a timer of ~4m26s + 2*10s + couple of seconds delay. To me it merely looks like it, but without seeing some code or having CCP state that's how they do it I can never state it as fact. For all I care they use an 64 bit long and throw around unnecessary data.
Nathan Jameson
Grumpy Bastards
#29 - 2013-06-25 23:23:46 UTC
Nebu for CSM! He understands the important issues!

http://www.wormholes.info

Rroff
Antagonistic Tendencies
#30 - 2013-06-26 00:06:28 UTC  |  Edited by: Rroff
Nebu Retski wrote:

But to make it clear to all of you that are aggressively set to the 5 minute timer, I'm not stating that CCP uses an 8 bit counter to give you a timer of ~4m26s + 2*10s + couple of seconds delay. To me it merely looks like it, but without seeing some code or having CCP state that's how they do it I can never state it as fact. For all I care they use an 64 bit long and throw around unnecessary data.


AFAIK They use python for much of the server game logic, the size of data stored in types only restricted for compatibility reasons.

It would potentially be a fair resource saving if the jump timers could be stored in only 8bits but I'd have thought for reliability reasons they'd need to store the actual event time tho could explain why sometimes it seems a bit unreliable how long the timer actually is - I have definitely managed in some cases to rejump a direction only 4 minutes after the first pass in that direction.
Chris Winter
Bene Gesserit ChapterHouse
The Curatores Veritatis Auxiliary
#31 - 2013-06-26 01:18:20 UTC
More likely they just store the time of your last two jumps and compare it when you try to jump through. Far simpler than actually running a timer.

Svodola Darkfury wrote:
Blodhgarm Dethahal wrote:
http://wiki.eveonline.com/en/wiki/Wormholes#Polarization

"If you jump the same wormhole twice within 5 minutes, you are polarised and cannot jump that wormhole any more until 5 minutes after the initial jump."


5 minutes per side as well. This means in rare cases you can be clear on one side of a wormhole but when you try to jump back you'll have a timer on the other side.

Example: you jump through a B274 and wait 3 minutes. Then you jump back through the K162 (starting a new timer) and wait 2 minutes. Now your original 5 minute timer is clear, so you jump back through the B274, but you are still timered approximately 3 minutes on the K162 side.

1) -> B274 (B274 timer started)
2) 3 minutes
3) -> K162 back into the wormhole (K162 timer started)
4) 2 minutes
5) -> B274 (B274 new 5 min timer)
6) -|> try to jump K162 again, but ~3 minutes remaining.

Svo.

It's not "per side." It's for the wormhole itself. In step 6, you have transited the wormhole twice in the last five minutes, so you have a timer. Your mistake was thinking you have a new timer in step 5, when it's really the same timer that "rolls."
Jack Miton
School of Applied Knowledge
Caldari State
#32 - 2013-06-26 02:27:24 UTC  |  Edited by: Jack Miton
Chris Winter wrote:
More likely they just store the time of your last two jumps and compare it when you try to jump through. Far simpler than actually running a timer.

Svodola Darkfury wrote:
Blodhgarm Dethahal wrote:
http://wiki.eveonline.com/en/wiki/Wormholes#Polarization

"If you jump the same wormhole twice within 5 minutes, you are polarised and cannot jump that wormhole any more until 5 minutes after the initial jump."


5 minutes per side as well. This means in rare cases you can be clear on one side of a wormhole but when you try to jump back you'll have a timer on the other side.

Example: you jump through a B274 and wait 3 minutes. Then you jump back through the K162 (starting a new timer) and wait 2 minutes. Now your original 5 minute timer is clear, so you jump back through the B274, but you are still timered approximately 3 minutes on the K162 side.

1) -> B274 (B274 timer started)
2) 3 minutes
3) -> K162 back into the wormhole (K162 timer started)
4) 2 minutes
5) -> B274 (B274 new 5 min timer)
6) -|> try to jump K162 again, but ~3 minutes remaining.

Svo.

It's not "per side." It's for the wormhole itself. In step 6, you have transited the wormhole twice in the last five minutes, so you have a timer. Your mistake was thinking you have a new timer in step 5, when it's really the same timer that "rolls."

im about 98.3% sure this is wrong.
will check when I get home though.

EDIT:
it actually only makes a difference if you can get into the same WH through a different entry within 5min which is fairly difficult.
If youre just jumping back and forth through a single hole your timers will be the same either way.

if you have a c2 with 2 HS exits that happen to be 1 jump apart.
jump out HSa
reenter c2 through HSb
go to jump out HSa again

do you now have a timer?
id be willing to bet you do.
but if youre right about it being a twice in 5 min per wh timer then you would not have a timer.

There is no Bob.

Stuck In Here With Me:  http://sihwm.blogspot.com.au/

Down the Pipe:  http://feeds.feedburner.com/CloakyScout

Svodola Darkfury
Federal Navy Academy
Gallente Federation
#33 - 2013-06-26 07:42:25 UTC
Chris Winter wrote:

It's not "per side." It's for the wormhole itself. In step 6, you have transited the wormhole twice in the last five minutes, so you have a timer. Your mistake was thinking you have a new timer in step 5, when it's really the same timer that "rolls."



This is quite possibly true. It could be a conceptualization error on my part. But like Jack is talking about with Triangulation, I think I'd still have the timer on the other side. I'm not entirely sure I explained it properly in my steps either.

When i try to jump back through the K162 side, I've got a 3 minute timer. If I jump through immediately at those 3 minutes, I have a 2 minute timer on the other side. I'm PRETTY sure that's accurate, but I haven't tested it RECENTLY and now you're making me feel not confident. :p

Svo.

Director of Frozen Corpse Industries.

Nathan Jameson
Grumpy Bastards
#34 - 2013-06-26 08:35:23 UTC
The simplest way to state it is:

You cannot pass through the same wormhole connection more than two times in the same five minute period.

That's it. Every time you successfully jump a wormhole, that five minute period starts recounting from the new next-to-last jump that you made.

http://www.wormholes.info

Chris Winter
Bene Gesserit ChapterHouse
The Curatores Veritatis Auxiliary
#35 - 2013-06-26 09:29:11 UTC
Svodola Darkfury wrote:
Chris Winter wrote:

It's not "per side." It's for the wormhole itself. In step 6, you have transited the wormhole twice in the last five minutes, so you have a timer. Your mistake was thinking you have a new timer in step 5, when it's really the same timer that "rolls."



This is quite possibly true. It could be a conceptualization error on my part. But like Jack is talking about with Triangulation, I think I'd still have the timer on the other side. I'm not entirely sure I explained it properly in my steps either.

When i try to jump back through the K162 side, I've got a 3 minute timer. If I jump through immediately at those 3 minutes, I have a 2 minute timer on the other side. I'm PRETTY sure that's accurate, but I haven't tested it RECENTLY and now you're making me feel not confident. :p

Svo.

It's not that you have a "2 minute timer on the other side," it's that you now have 2 minutes left until you won't have passed through more than twice in the last five minutes.

Basically, what Mr Jameson said.
Nathan Jameson
Grumpy Bastards
#36 - 2013-06-26 10:56:13 UTC
Chris Winter wrote:
Basically, what Mr Jameson said.


THE GREAT AND POWERFUL OZ HAS SPOKEN

http://www.wormholes.info

Ashimat
Clandestine Services
#37 - 2013-06-26 11:10:20 UTC
Nebu Retski wrote:
Jack Miton wrote:
your timer will be 4m30s odd. certainly more than 4min.

Interesting. I haven't measured the time, but if it's around 4m30s then I supose CCP is simply using an 8-bit counter that increments by 1 every second. That gives you 256s in total or about 4m27s and automatically overflows back to 0 after 4m27s.

roflol, how old are you? 8-bit counters? jeez.

Got blog: http://thecloakedones.blogspot.com

Euthanasia Anneto
Embers Children
#38 - 2013-06-27 05:58:46 UTC
It's 5 indeed to what most are telling.

When cycling a sh!thole I jump, wait timer and jump back and re-jump after 4 minutes as my times are always correct on that..

Start calculating: Add in the time you first jump (2-3'ish seconds), few secs loading, 20 secs wait timer, approach-unloak 2~5 secs, and jump 2~3 secs few secs loading and warp off and return on the wh 4 mins later you can clearly start jumping forth and back.

Don't ask me what the exact times but counting all up, you're clearly on 5 minutes and so a Orca can cycle a 2bn WH in exactly 20mins. During those 20minutes it's the most fun part of the game. Thinking who'll be tackling and dropping that Orca

.EC.. of [TOHA], Industrialists with guns. We're overe there, some where and no where... Contacting go through ingame convo's .EC.. and [TOHA] are recruiting, get in contact with us

Previous page12