Has happened in 100% of games with kindred so far after recently purchasing her. The first 2 or 3 buffs will hit camps in the enemy jungle. The fourth will hit Rift Herald but every subsequent proc will hit Rift Herald. Even after 20 minutes. The passive remains working and you can see it disappear once the time runs out however it will again retarget a jungle monster that is no longer there.
Orionxhavok1 votesTesting this in a custom game at the moment to make sure it is recreated a third time.
Orionxhavok1 votesat 19:45 Rift herald died and kept the buff active. Will monitor Baron to see if the buff will ever transfer to him, as well as solo baron later to see if he gives a stacks though he does not hold the buff.
Orionxhavok1 votes50 Minutes in-game now. After 16-18 minutes Kindred's passive only hits baron. Not sure if that's intentional, however killing baron when he does not have the buff DOES still give a stack of kindred's passive. After killing Baron, the passive will wait for baron to respawn. Still could be a bug, at least the big guy does give a stack at least.
Orionxhavok1 votesResults inconclusive. Second baron did not give a stack.
Orionxhavok1 votes[slayer-jinx-unamused] Here's to hoping this gets clarified/fixed/attention. 3rd baron did give away a stack, so he's only somewhat a Scrooge. For newer kindred players however I wish more clarity was provided to let players know their passive will stop hunting camps and only target baron after 15-20 minutes.
SympleSynz1 votesThis is incorrect. After 6 stacks, the passive is supposed to start marking baron or rift herald. Targeting baron after 15-20 minutes should only be happening once Kindred is at 6 stacks. But if you're having issues where you aren't at 6 and Wolf is targeting Baron, then that is an issue according to the patch notes.
MtZenon1 votesAlso noticed this. However, I was already at 6 stacks from jungle monsters so I'm not sure if that makes a difference.
Orionxhavok1 votesMakes getting above 8-10 stacks impossible
SympleSynz1 votesThat shouldn't affect getting 8-10 stacks because after 6, on this new patch, the passive will mark baron or rift herald (baby baron). As long as you get your champ kills, you'll get your stacks.
Edit: My bad, to clarify, meant after 6th stack.
Orionxhavok1 votesThis means you have to have enough stacks already/be fed enough or active enough in order to chase down and get them solely off of champions. However, I simply feel like having it on a 6 minute timer waiting for baron to respawn and forcing your team to attempt baron every single time it's up is a little overkill. Alternating between Baron and Dragon even would help.
Edit: Alongside the fact that you're never told by the champions kit or any tooltip that after a certain point you will be forced to get stacks from only baron or champions. It only says "Enemy jungle camps" Seems like pre-6 you should only worry about hording as many stacks as possible because they're few and far between afterwords.
Edit x2: Did just realize you meant after 6 stacks instead of level 6. So that makes it a balancing tool then, was never notified that baron/Rift Herald would be the sole target of stacks. Still bummed that it's planned that way and not meant to alternate at the very least. Really caps one of the 5 endless stacking champions potential in a way not many of the others are. Really wish this was a bug.
[zombie-nunu-tears]
SympleSynz1 votesAgreed about using Dragon in addition for stacks would be good, but the concept behind targeting Rift Herald is to get that top laner and jungler to actually go for Rift Herald. Targeting Baron is to still give Kindred an opportunity to get stacks from an objective rather than from kills only as well as trying to give teams more incentive to go for Baron. From what I can tell, this preseason is all about speed and snowballing (ending games within 35 minutes, taking inhibs in under 20). For the bug situation, just verify that Wolf targets Rift Herald or Baron prior to 6th stack. If that's the case, then it's an actual bug. When I get a chance, I'll try and test it out in a custom or bot game.
Orionxhavok1 votesThere's still the issue of Rift Herald holding onto his stack as he turns into baron, and baron not giving a stack then. But that would only be an issue to a team that went for baron the minute it spawns in, that and baron occasionally not granting a stack (Happened once, not 100% sure the buff wasn't in the middle of refreshing at that moment) Thanks however.
SympleSynz1 votesYeah, with baby baron leaving just before baron comes up and it looking like baron is marked, can be an issue. When you test it out, get 6 stacks, have it target baby baron, wait for the switch, and give it some time and see if that mark ever goes away. When taking a mark, there should be a delay on the mark disappearing when the target is gone.
Orionxhavok2 votesI actually did check that. I watched the switch happen and the mark remained for at least a minute after Herald tag teamed out.