Medium Intercept Appreciation Post

Two things on this:

1.)Thank You. It’s a well written post that made me feel less crazy all those times I felt the animations weren’t working right. And at no point does it blame summoners for how we play… which was amazing to see.

2.) More like this please.

Comments

Searmenis

Well, it is nice, but with this rythme we ll have a decent gameplay in 5 years. (I m talking about the "another time" part of the post).
Plus, ok, let s hope the light intercepts are gone, what about the dashing back of the defender when you intercept, and hitting you a millisecond after your dashing forward ends? Is this another issue as well? @KabamDORK
No, If I'm understanding you correctly, this is what many refer to as a Side Step. You can also do this. Is this what you were referring to?

I don't know what a side step is

Interstellar17

Players should expect the biggest compensation package in history. This is such a fundamental error with the game but of course in game purchases don't get turned off while this bug has been happening.

unknown

This content has been removed.

BeastDad

Out of all the annoying things that have happened, parry and this problem have been the absolute worst.

There is zero excuse for fundamental aspects of the game not working over long periods of time.
For context, the fundamental aspect was built for 30 frames per second and only really became an issue as part of a systems upgrade to 60 frames per second which is being resolved on the next build. There are a few items that were affected by 60fps you can see on the Trello Board.

For context, this issue has cost the player base severely and there really needs to be some adequate compensation for it. I think the majority of players would appreciate some clarity on what is being planned for us in that regard.

Giantwalrus56

Out of all the annoying things that have happened, parry and this problem have been the absolute worst.

There is zero excuse for fundamental aspects of the game not working over long periods of time.
For context, the fundamental aspect was built for 30 frames per second and only really became an issue as part of a systems upgrade to 60 frames per second which is being resolved on the next build. There are a few items that were affected by 60fps you can see on the Trello Board.
For context, this issue has cost the player base severely and there really needs to be some adequate compensation for it. I think the majority of players would appreciate some clarity on what is being planned for us in that regard.

While I think a compensation package would be nice, I personally much rather have Kabam identify why this bug is happening first. Hopefully from there, they'll fix it. After that, if they think it's warranted, send a package. No sense in sending or talking about it yet. Last thing I want is a package so I possibly use it while still intercepting with my face

KLZ

We expect some fat compensation for this!!

Eakomo

there should be no appreciation till be problem is resolved, if fixing it for months in a row makes it even worse and even more apparent it should be a disdain with the work done already to the game

Buzerk1969

No acknowledgement unless the devs finds a fix. Hope we can change this mindset in future.
In a bug report, we need to be able to reproduce the bug for it to be acknowledged. If we can't reproduce it or reproduce it consistently, it remains under investigation until we can do that. There are sometimes we get videos of issues clearly happening to the individual, but if we can't take those same steps, same champs, same quests and produce the same results, we can't really acknowledge that without further investigation. That all being said, we can do a better job on transparency of this moving forward.

I’m sorry, I don’t buy this. Problem like this, just play the game, it happens so often, just playing the game makes you go, Mmm 🤔 there’s something wrong here. So when you say that, it is even more worrisome and also kind of prove a lot of things are being pushed without being properly tested.

Don’t say that’s not the case as recent updates have broken so many thing. (Like Rintrah being unplayable).

So thank you for the info, but also not that transparent (where is the in game msg?, why do player have to come here to find out about it?)

Yaga

No acknowledgement unless the devs finds a fix. Hope we can change this mindset in future.
In a bug report, we need to be able to reproduce the bug for it to be acknowledged. If we can't reproduce it or reproduce it consistently, it remains under investigation until we can do that. There are sometimes we get videos of issues clearly happening to the individual, but if we can't take those same steps, same champs, same quests and produce the same results, we can't really acknowledge that without further investigation. That all being said, we can do a better job on transparency of this moving forward.

Does the team have at least 2 or 3 of the most used devices that people are using to play the game? Not emulators, because they introduce other issues, but real devices? I can say that my M2 iPad Pro does different things than my iPhone 12. The AI of fights and the reaction times for defenders are sometimes different.

MCoC is the only game that I feel like I have to record every single thing I do in the game, even buying crystals (looking at your Quantity 1 6-star crystal moving to the bottom of the list), to make sure I'm not going crazy.

DrZola

Assuming the fix works, what’s the plan going forward? Just an earnest “my bad” and good luck?

Dr. Zola

BeastDad

Assuming the fix works, what’s the plan going forward? Just an earnest “my bad” and good luck?

Dr. Zola

For the first time ever, I am thinking about taking a long break from the game due to this issue. It is absolutely destroying ever single game mode. It is inexcusable at this point.

DrZola

Assuming the fix works, what’s the plan going forward? Just an earnest “my bad” and good luck?

Dr. Zola
For the first time ever, I am thinking about taking a long break from the game due to this issue. It is absolutely destroying ever single game mode. It is inexcusable at this point.

I’m still trying to understand how longstanding the issue has been. I’m also skeptical of the assertion that 60 fps is the cause of the issue—rather than what revealed it.

But who really knows? I doubt I would, since I’ve usually just muttered “well, I guess that intercept didn’t work” instead of recording and trying to chronicle each and every occurrence. There’s no reason to think any of it is intended, but I am mindful of champs and nodes that need intercepts to max damage or deal damage. It would be hard to argue this is a “no harm, no foul” problem.

Dr. Zola

Average_Desi

Assuming the fix works, what’s the plan going forward? Just an earnest “my bad” and good luck?

Dr. Zola
For the first time ever, I am thinking about taking a long break from the game due to this issue. It is absolutely destroying ever single game mode. It is inexcusable at this point.
I’m still trying to understand how longstanding the issue has been. I’m also skeptical of the assertion that 60 fps is the cause of the issue—rather than what revealed it.

But who really knows? I doubt I would, since I’ve usually just muttered “well, I guess that intercept didn’t work” instead of recording and trying to chronicle each and every occurrence. There’s no reason to think any of it is intended, but I am mindful of champs and nodes that need intercepts to max damage or deal damage. It would be hard to argue this is a “no harm, no foul” problem.

Dr. Zola

This very specific issue, not missing intercepts, but 'missing intercepts even when both are at the same place and the left side should override and land a hit' is new and was a result of 60fps, and after the January fix. So around 2 months at this present moment.

I'm not saying you haven't faced issues before , but just not this specific one. I have definitely felt the "this should've landed before", because I had seen the Jan patch notes talking about the intercept fix and was in a lookout for anything weird

DrZola

Assuming the fix works, what’s the plan going forward? Just an earnest “my bad” and good luck?

Dr. Zola
For the first time ever, I am thinking about taking a long break from the game due to this issue. It is absolutely destroying ever single game mode. It is inexcusable at this point.
I’m still trying to understand how longstanding the issue has been. I’m also skeptical of the assertion that 60 fps is the cause of the issue—rather than what revealed it.

But who really knows? I doubt I would, since I’ve usually just muttered “well, I guess that intercept didn’t work” instead of recording and trying to chronicle each and every occurrence. There’s no reason to think any of it is intended, but I am mindful of champs and nodes that need intercepts to max damage or deal damage. It would be hard to argue this is a “no harm, no foul” problem.

Dr. Zola
This very specific issue, not missing intercepts, but 'missing intercepts even when both are at the same place and the left side should override and land a hit' is new and was a result of 60fps, and after the January fix. So around 2 months at this present moment.

I'm not saying you haven't faced issues before , but just not this specific one. I have definitely felt the "this should've landed before", because I had seen the Jan patch notes talking about the intercept fix and was in a lookout for anything weird

That’s interesting, and yes—the issue being addressed was limited to Medium vs. Medium tiebreak between Attacker and Defender.

If I understand correctly from Dave’s post, the “tie goes to the Attacker” policy was based on mechanics and coding that had been in place for a very long time. It sounds like the 60 fps upgrade (forgive me—when was that introduced?) created an issue where a single 60 fps frame could produce a result counter to the usual tiebreaker policy that might otherwise not have occurred in 30 fps.

January update, if I understand correctly again, was supposed to resolve that, but issues remained. The hope is that the April update does the trick.

Is that your understanding as well?

Dr. Zola

Average_Desi

Assuming the fix works, what’s the plan going forward? Just an earnest “my bad” and good luck?

Dr. Zola
For the first time ever, I am thinking about taking a long break from the game due to this issue. It is absolutely destroying ever single game mode. It is inexcusable at this point.
I’m still trying to understand how longstanding the issue has been. I’m also skeptical of the assertion that 60 fps is the cause of the issue—rather than what revealed it.

But who really knows? I doubt I would, since I’ve usually just muttered “well, I guess that intercept didn’t work” instead of recording and trying to chronicle each and every occurrence. There’s no reason to think any of it is intended, but I am mindful of champs and nodes that need intercepts to max damage or deal damage. It would be hard to argue this is a “no harm, no foul” problem.

Dr. Zola
This very specific issue, not missing intercepts, but 'missing intercepts even when both are at the same place and the left side should override and land a hit' is new and was a result of 60fps, and after the January fix. So around 2 months at this present moment.

I'm not saying you haven't faced issues before , but just not this specific one. I have definitely felt the "this should've landed before", because I had seen the Jan patch notes talking about the intercept fix and was in a lookout for anything weird
That’s interesting, and yes—the issue being addressed was limited to Medium vs. Medium tiebreak between Attacker and Defender.

If I understand correctly from Dave’s post, the “tie goes to the Attacker” policy was based on mechanics and coding that had been in place for a very long time. It sounds like the 60 fps upgrade (forgive me—when was that introduced?) created an issue where a single 60 fps frame could produce a result counter to the usual tiebreaker policy that might otherwise not have occurred in 30 fps.

January update, if I understand correctly again, was supposed to resolve that, but issues remained. The hope is that the April update does the trick.

Is that your understanding as well?

Dr. Zola

I had asked about the same . I'll tag Dave's reply. The 60 fps was in November I believe.

No acknowledgement unless the devs finds a fix. Hope we can change this mindset in future.
In a bug report, we need to be able to reproduce the bug for it to be acknowledged. If we can't reproduce it or reproduce it consistently, it remains under investigation until we can do that. There are sometimes we get videos of issues clearly happening to the individual, but if we can't take those same steps, same champs, same quests and produce the same results, we can't really acknowledge that without further investigation. That all being said, we can do a better job the transparency of this moving forward.

This is from the January patch notes. Only after this did I start having issues.
Could you help understand what the difference in the January path and the upcoming April patch is?
In our post to the players, we mentioned that there was an additional element to this problem that we discovered after the fix went live that attributed to similar experiences but not the exact ones we fixed previously. Front facing, this simply felt like it was still happening, but not in all the same situations as before. TLDR, we found extra stuff that was still making it happen for some players ( if not all ), and we patched it and will be shipping it with our next update.

BeastDad

Assuming the fix works, what’s the plan going forward? Just an earnest “my bad” and good luck?

Dr. Zola
For the first time ever, I am thinking about taking a long break from the game due to this issue. It is absolutely destroying ever single game mode. It is inexcusable at this point.
I’m still trying to understand how longstanding the issue has been. I’m also skeptical of the assertion that 60 fps is the cause of the issue—rather than what revealed it.

But who really knows? I doubt I would, since I’ve usually just muttered “well, I guess that intercept didn’t work” instead of recording and trying to chronicle each and every occurrence. There’s no reason to think any of it is intended, but I am mindful of champs and nodes that need intercepts to max damage or deal damage. It would be hard to argue this is a “no harm, no foul” problem.

Dr. Zola

It went from an occasional problem to an every day disaster the past few months.

unknown

This content has been removed.