Not understanding new notice
Not understanding new notice
I have had multiple scenarios where I've spammed K xxxxx or k h.xxxx and it takes 4 or 5 times entering the command to hit them. Got stabbed tonight after spamming k h.seanchan with notice on pracced to 90%. 5 commands went through and I got stabbed still. Was chasing this guy around for a while and would constantly have to hit it 4-5 times if he was hidden to hit him. Is that really how it is supposed to be?
Re: Not understanding new notice
Actually have 93% notice.
Re: Not understanding new notice
Do you have the log? Using kill h.xxxx should work almost 100% first time with 93% notice pracced.
Re: Not understanding new notice
This should be in help I think but anyway, can't remember who did this so going to guess Markus
Notice % k vs 94 hide Longest failure series
78
84 1
86 4
88 14
90 25 8
92 22 11
93 34 7
94 50 5
95 59 5
96 69 3
97 76 3
98 75 3
99 81 4
Notice % k vs 99 hide Longest failure series
99 44 5
Notice % k hidden vs 94 hide
66
72 24
78 80
84 100
Notice % k hidden vs 99 hide
72 1
77 40
82 83
84 97
86 100
Notice % k vs 94 hide Longest failure series
78
84 1
86 4
88 14
90 25 8
92 22 11
93 34 7
94 50 5
95 59 5
96 69 3
97 76 3
98 75 3
99 81 4
Notice % k vs 99 hide Longest failure series
99 44 5
Notice % k hidden vs 94 hide
66
72 24
78 80
84 100
Notice % k hidden vs 99 hide
72 1
77 40
82 83
84 97
86 100
Re: Not understanding new notice
Short version -
If notice is on:
k h.whatever (with 87? notice) will always hit the hidden.
k whatever will not always hit the hidden, but will miss less frequently with higher notice
If notice is *not* on:
You're probably about to get stabbed, because not even using h. will save you.
If notice is on:
k h.whatever (with 87? notice) will always hit the hidden.
k whatever will not always hit the hidden, but will miss less frequently with higher notice
If notice is *not* on:
You're probably about to get stabbed, because not even using h. will save you.
Re: Not understanding new notice
To explain that, the second column is how many times out of 100 it hit the hidden.
This bit:-
Notice % k vs 94 hide Longest failure series
93 34 7
means with your notice, 93%, k guy vs only 94% hide, it hit him 34 times out of 100 and failed 7 spams in a row.
Notice % k hidden vs 99 hide
86 100
means with 86% notice, k hidden hit the hidden 100 times out of 100.
That's not a huge test sample and certainly missing 5 might be possible, but I'd guess you're using k target not k h.target. If you're spamming k target because you're moving or low moves, spam it like you're trying to break your own finger, if you're expecting them to be there use k h.target and spam SLOWER, since it's much higher chance of hitting but takes a move per spam, you can mix them up too for more chance of getting that hit as they walk in but less moves. It's more complicated than old notice, where ~87% meant you'd hit them in a couple spams and you have to pay more attention to your moves to keep using k h.target.
There's tricks to it though. For example, weaves, charge, stab and targetted emotes don't use a move when you target them h.target, so all of those should always have the prefix, you can spam to start a weave or charge (not too hard ofc so you don't interrupt it) or spam poke h.target to see them then hit k h.target to engage.
This bit:-
Notice % k vs 94 hide Longest failure series
93 34 7
means with your notice, 93%, k guy vs only 94% hide, it hit him 34 times out of 100 and failed 7 spams in a row.
Notice % k hidden vs 99 hide
86 100
means with 86% notice, k hidden hit the hidden 100 times out of 100.
That's not a huge test sample and certainly missing 5 might be possible, but I'd guess you're using k target not k h.target. If you're spamming k target because you're moving or low moves, spam it like you're trying to break your own finger, if you're expecting them to be there use k h.target and spam SLOWER, since it's much higher chance of hitting but takes a move per spam, you can mix them up too for more chance of getting that hit as they walk in but less moves. It's more complicated than old notice, where ~87% meant you'd hit them in a couple spams and you have to pay more attention to your moves to keep using k h.target.
There's tricks to it though. For example, weaves, charge, stab and targetted emotes don't use a move when you target them h.target, so all of those should always have the prefix, you can spam to start a weave or charge (not too hard ofc so you don't interrupt it) or spam poke h.target to see them then hit k h.target to engage.
-
Firimei Lang
- Posts: 1268
- Joined: Fri Feb 05, 2016 6:09 pm
- Location: UK
Re: Not understanding new notice
Great information there, thank you.
Re: Not understanding new notice
A long time ago I posted a log where I saw a guy walk in, fired off 3 kill darks, then 1 kill h.dark and maybe 1 more h.dark (though that seems unlikely), but definitely a look next - still saw the hidden and then got stabbed. This was with 93% notice. The simple truth of the matter was - if I believed he was there I should have walked out of the room after I failed the kill h.dark. The look was a wasted command.
All that aside, I hate that last hide change. 99% hide is a must for a rogue. It makes you really damn slippery. Feels like most rogues doubleline a hide rather than a direction - the chaser has to have notice on and will potentially fail the kill dark in the next room while you figure out the ideal direction. Love this game, but don't think we've ever really figured rogues out.
All that aside, I hate that last hide change. 99% hide is a must for a rogue. It makes you really damn slippery. Feels like most rogues doubleline a hide rather than a direction - the chaser has to have notice on and will potentially fail the kill dark in the next room while you figure out the ideal direction. Love this game, but don't think we've ever really figured rogues out.
Re: Not understanding new notice
I had something similar happen this week. 91% notice, 4 k seanchans, 1 look and 1 k seanchan that I had stacked (otherwise I'd have used h.seanchan), and got stabbed. Normally k dark/k seanchan works fine for me, but that was just a bad run. It also makes me believe that the look command has some innate bonus that the kill command doesn't have.Paigey wrote:A long time ago I posted a log where I saw a guy walk in, fired off 3 kill darks, then 1 kill h.dark and maybe 1 more h.dark (though that seems unlikely), but definitely a look next - still saw the hidden and then got stabbed. This was with 93% notice. The simple truth of the matter was - if I believed he was there I should have walked out of the room after I failed the kill h.dark. The look was a wasted command.
Re: Not understanding new notice
Don't practice any notice. Instead practice bash!