Swift bow not giving enough focus

[edling]

Hi

I just had to make a post about this since the gm i talked to made no
sense.

Sometimes swift bow and 2 quick shots wont give u the 2 focus needed
to use penetration shot (reduced to 2 focus with traith ofc)

I talked to a GM about this and aperently it was a "hidden feature of the game" and not a known bug.

If u ask me this makes no sense whatsoever , what do u think?

The same GM also told me that Traps cant be used on other players in duells
and against monster players.
Im not 40+ so i cant know if they work against monster players but reading on the forums i defently get the impresseion that they work fine.

So whats going on , is this GM completly clueless or he is right ?

[Scappydog]

There have been some reports from US forums that both Swift Bow and the New Blindside are not always giving the stated focus gain since Book 12. I haven't had a chance to try this out for myself yet, but I'm damned sure that pre-book 12 you would get always get a focus gain of 1 from QS and 2 from Swift.

Suggest we all keep an eye on our focus gains in the next few days. This could be a bug or another unannounced intentional change.

[Scappydog]

Just run a quick test.

Quick Shot: Gave 0 or 1 focus ( had 3 zeroes in a row ). However on occasion I got an extra focus point after autoattack fired off following QS, giving a focus gain of 2.

Swift Bow : Gave 1 or 2 focus ( never saw it give zero ). Again on a few occasions I got an extra focus point following an autoattack giving a focus gain of 3.

There is something very weird going on. It's like there is a random roll now to see how much focus the shot gives you with maybe an added chance of a focus point from autoattack.

The focus loss from movement is definately less.

[Isfret]

I had the exact same problem.

It really messes my rotation up:(

[Dofolo]

ffs was wondering why I couldn't do my usual attack sequence.

By book 15 there won't be any hunters left ~:-(

[OMWiener]

didn't really notice it that hard. I think it makes the fight a bit more challenging, so that you cannot choose the same rotation you did last time, you gotta be more on your toes (or make a focus build).

[Bell of Eternity]

Any reports on champions' fervour? It is basically a same type of mechanic as hunter focus so it naturally should have been changed to similar semi-random pips, yes?

[Sirak]

there is the theory in the US forum, that it has something to do with the 3sec movement-focus-mechanic new to book 12. so if you move, stop and shoot immediatly you might not get the full bonus of the shot.
should be tested if someone has time.

[Scappydog]

Have just re-run the test I did last nite to see if there was anything in this.

Picked an area with a high density of low lvl mobs so I didn't have to move. I used only quickshot for this test.

Remaining static and taking down 6 mobs I got +1 focus from each. Even though I didn't move I did still get an extra focus point once.

I moved until all my focus had gone and returned to same area. Same result as above.

I then moved, but not so far as to lose all focus and started seeing the zero focus gain.

In both scenarios I was still getting the extra focus point now and again, apparently after an autoattack.

So yes, it does look like it's the new focus/movement mechanic that might be screwing things up.

[Bell of Eternity]

I did a quick test as well, and it confirms everyone's suspicions: the mechanics are messed up. Before B12, we were losing focus every second of movement. Post-B12 we were supposed to lose a point of focus per 3 seconds of movement.

In reality, we lose focus for fractionary movement. I tested like this: focus up to full. Make the tiniest of movements, just a single step forward. Wait three seconds. You will then observe a loss of one point of focus. In other words, focus loss is on three-second ticks, but even small movement during those three seconds will result in focus loss.

There's another test to see how the mechanic is messed up: Acquire a target. Start at zero focus. Take a tiny step forward. Immediately, make a Quick Shot. Wait three seconds. You will lose one point of focus you just gained from the shot. If the three-second pulse is server-global instead of starting a countdown on your motion, it might be that your step and shot will land on separate 3-second cycles and there's no focus loss, but I've yet to observe that happening.

So, if you start focusing up and/or shooting BEFORE having stood still for three seconds, you will lose one point of focus. I don't see Turbine going to fix this, because they have likely implemented this to prevent a step-stop-step abuse (short motions to avoid focus loss). In other words: working exactly as intended.

correction - one thing Turbine should, and might, do is ignore focus loss when our focus is zero to start with. This avoids the delayed focus loss of my example #2.

[MéLAnoR]

I did a quick test as well, and it confirms everyone's suspicions: the mechanics are messed up. Before B12, we were losing focus every second of movement. Post-B12 we were supposed to lose a point of focus per 3 seconds of movement.

In reality, we lose focus for fractionary movement. I tested like this: focus up to full. Make the tiniest of movements, just a single step forward. Wait three seconds. You will then observe a loss of one point of focus. In other words, focus loss is on three-second ticks, but even small movement during those three seconds will result in focus loss.

There's another test to see how the mechanic is messed up: Acquire a target. Start at zero focus. Take a tiny step forward. Immediately, make a Quick Shot. Wait three seconds. You will lose one point of focus you just gained from the shot. If the three-second pulse is server-global instead of starting a countdown on your motion, it might be that your step and shot will land on separate 3-second cycles and there's no focus loss, but I've yet to observe that happening.

So, if you start focusing up and/or shooting BEFORE having stood still for three seconds, you will lose one point of focus. I don't see Turbine going to fix this, because they have likely implemented this to prevent a step-stop-step abuse (short motions to avoid focus loss). In other words: working exactly as intended.

correction - one thing Turbine should, and might, do is ignore focus loss when our focus is zero to start with. This avoids the delayed focus loss of my example #2.Why not implement it as losing focus via meters we move? This 'd fix it.
I have a question ; with full focus will i move only a step then do i lose every focus earned via skill in 27 secs?

[Scappydog]

In theory you should lose one focus point for every three seconds. So if you have full focus and move one step, after 3 secs you should only lose 1 point and no more. But it will be worth testing.

[Scappydog]

Just run a quick test.

From a full focus start took one step. After 3 secs one focus point lost, no more.

From a zero focus start. Selected target, took one step and fired QS. +1 focus followed by -1 focus when the 3 secs was up.

From a zero focus start after 3 secs of non movement. Select target fired QS +1 focus, no loss.

So yes, if you fire within that 3 second window you will lose a focus point when the timer catches up, even if you start with zero focus. Wait for 3 seconds after stopping movement and you get no loss.

At least knowing what is going on helps.

[Bell of Eternity]

Why not implement it as losing focus via meters we move? This 'd fix it.
I have a question ; with full focus will i move only a step then do i lose every focus earned via skill in 27 secs?
Yes, implementing it by distance might be wiser, but the current system is built on timer. They'd need to tear it down and re-code it up from the ground. That would take some time. My suggestion is just a minor alteration to focus loss function, to put it in pseudocode: if(focus==0) return;

To your question: if you have full focus and take only a single step, you will lose 1 point of focus after 3 seconds are up. Naturally it won't matter how you gained the focus.

[MéLAnoR]

Yes, implementing it by distance might be wiser, but the current system is built on timer. They'd need to tear it down and re-code it up from the ground. That would take some time. My suggestion is just a minor alteration to focus loss function, to put it in pseudocode: if(focus==0) return;

To your question: if you have full focus and take only a single step, you will lose 1 point of focus after 3 seconds are up. Naturally it won't matter how you gained the focus.Yeah i tested it too and we don't lose focus after that 3 focus removes 1 focus.It might be a really pain if we did continue losing focus lol

[Scappydog]

Just made another interesting observation. Does any one recall losing focus pre Book 12 if a mob threw you? Just being doing the trolls in Lonelands for the deed and noticed that one focus point drops when they hurl you into the distance.

[Amwrath]

One of the annoying things is the fact that when you run, stop and use focus to get +9focus, you usually end up with 8.

Which is caused by the timer thing. I get 8 focus more often than I get 9 with the skill.

[Legotho]

My suggestion would be to lose a point of focus when you start moving, and then have 3 seconds of safe movement. So move the focus loss to the start of the 3 second cycle, instead of the end.

It would certainly mean that if you're running, and stop to start firing, or whatever else to gain focus, you'd be sure not to lose that focus immediately after gaining it. Whether there's another quirk waiting to scupper people with this, I don't know...

Hmm... So, if I've got exactly enough focus to use penetrating shot, under the current system, I can take a few steps, use the shot, and then lose the (now non-existent) point of focus. Under my version, that'd be impossible. I've no idea which is fairer!

[Walaydir]

I agree with Legotho. That's the way it should be implemented.

[Scappydog]

Or the timer doesn't start if you have zero focus, thats whats catching people out. Why should you lose one focus point after stopping when you had zero to start with?