Why does Kabam not fix the issues that don't benefit us? Poll

Kabam , please don't close this thread. It's an opinion post and not against any tnc.

Seeing how quickly you have identified the issue where Cull was doing insane damage and was benefitting the player base, I was wondering when will you fix Corvus who takes Coldsnap damage and is completely bugged on physical resistance nodes.6.2 sinister issues, indistructible The Champion on 6.2.6 issue and many more have gone into the state "we're looking into it ". Why do they not get fixed sooner ? Any why does issues that benefit us get fixed in a day or 2 ?

Comments

DarkestDestroyer

I think it does seem that anything against us is allowed to ride the waves longer than if we are benefited.

Wether it’s due to the fixes being easy or not, some things are still bugged, like surely things can take longer, but over 3 months? Really? When a vast variety have been fixed in a day or 2, it’s not like all the ones benefiting us are the same; they are all different so it can’t be a case of more complex vs easy fix?

Liss_Bliss_

People who don’t know anything about game development should never complain about some bugs being fixed and others being “ignored” if you have no clue what it takes to rewrite lines upon lines of codes for harder issues, or how pushed vs downloaded fixes work, then you should not sit here and split hairs.

What it comes down to is that you guys really only want bugs in the game that helps you. And when those bugs get fixed you all rant and QQ.

Get over it. And understand how things actually work when developing a game. It’s not as simple as the lot of you believe.
Wow.. I’ve seen my fair share of dumb blonde posts over the years in this forum... this post is.. just ... plain ****.

I don’t understand how all things works and I never will. But I also understand
a) it takes time to solve what matters;
b) that perception matters and
c) customer satisfaction is paramount.

It’s a recipe for disaster when you allow an issue lingers without proper and timely update or communication. Want one? Pure skills. 2 years and counting. No proposed resolution and no update (after fixing MD).

So don’t go about telling me that I need a PhD to make comments when I have been waiting over two years for a fix because I didn’t ask for yours.
Yep even if it is so technically difficult to fix certain bugs (which I highly doubt any bug would take months to resolve), there is no reason we can't have proper communication and confirmation about its bugged nature. Something like armour break/physical resistance interaction has not even been acknowledged; same for corvus taking coldsnap. ANYONE playing the game knows this is a bug.

Failure to fix I can understand involves technical issues; but failure to communicate?

Communication can be better I’ll give you that.

But by your own admission; “don’t think any bug can take months to fix” you are saying “well I don’t understand what all goes on to fix something but that doesn’t matter it should be easy to fix bugs so their failure to do so confirms they pick and choose what bugs to fix especially if a bug benefits the players” and that’s the point I am trying to make. Not all bugs are equal, some really are a few keystrokes to fix, while others take teams of people to figure out what went wrong.
As I mentioned, I am not in a position to say either way whether it is reasonable or unreasonable that bugs have been unresolved for months.

But my main gripe is I don't see why these known bugs are not publicly acknowledged and migrated to the known issues list. Doing that would bring much consolation to the community.

I read somewhere from an orange named individual, the reason they don’t “acknowledge every post” is because they have seen how (I’m gonna paraphrase here) vile and disgusting the community is. They will tell them to hurry, tell them they suck at their jobs, berate they because it’s always only about them and they don’t care about anything else. So they decided to lessen the vile content tossed at them with minimal communication. Be honest if every time you told someone the progress of an issue they threw insults after insults at you, the freaking MESSENGER, you would get tired of replying and acknowledging every issue.

Would it be nice to have every issue addressed at every step? Yeah, but that’s not feasible. Just like it’s not feasible for when someone makes a post and expected to not be labeled a “dumb blonde” because some caveman doesn’t agree with her.

Communication is paramount, and lack of communication doesn’t mean things aren’t being done behind the scenes.

Liss_Bliss_

I think it does seem that anything against us is allowed to ride the waves longer than if we are benefited.

Wether it’s due to the fixes being easy or not, some things are still bugged, like surely things can take longer, but over 3 months? Really? When a vast variety have been fixed in a day or 2, it’s not like all the ones benefiting us are the same; they are all different so it can’t be a case of more complex vs easy fix?

Actually it can. Think of the game as a car on lease. I have free “regular maintenance” and even free “intricate repairs” if I let them know something is wrong right away.

Now let’s say I notify them I am close to an oil change. I take it in and it gets fixed in 45 mins to an hour. Granted when I dropped it off there was nobody there in front of me and I know I can change my own oil in under 15 mins. But whatever.

Now let’s say I hear a knocking noise coming from the engine. And because I am busy I fail to report it, fail to schedule a time for them to look at it. 3 months down the road I notice my car getting hotter and hotter. So I finally tell them about it and take it in.

Well my friend, what could have been fixed easier now will take substantially longer and end up costing me money. Because it took me so long to bring it in there is more wrong with the engine because of one thing.

Also would I want my mechanics texting me every time they took a bolt out, or every time they grabbed the wrong socket size? No it take away from them actually working on my car. And sounds too much like they want my approval and validation along with “good job “Bruce”

Now look at the game, a few bugs can be easy to fix, like How they have weekly maintenance. But somethings can take longer because it’s more intricate or because that bug has branched and caused more bugs.

And honestly you guys are screaming at the wrong people. The forum devs aren’t the ones fixing things. They are the ones taking our issues to who needs to see it. They are the ones who have tied hands on communication because the one fixing it is t taking to them. So if they don’t have information to give to is, what are they supposed to do?

DrBruceWayne

We provide video, proof, information, literally everything needed to identify a bug and we get nothing, either ignored, or "passed to the team"

Nick Fury removes all suicides just like how Masochism/Buffet works, fix within hours

Not to mention: Corvus still takes Bleed/Coldsnap damage and his Armor Break's interaction with Physical Resistance (4+ months now)

Symb Supreme broken (4+ months now)

Backdraft Intercepts broken (4+ months now)

Only a fool can be siding with Kabam on this

Lormif

We provide video, proof, information, literally everything needed to identify a bug and we get nothing, either ignored, or "passed to the team"

Nick Fury removes all suicides just like how Masochism/Buffet works, fix within hours

Not to mention: Corvus still takes Bleed/Coldsnap damage and his Armor Break's interaction with Physical Resistance (4+ months now)

Symb Supreme broken (4+ months now)

Backdraft Intercepts broken (4+ months now)

Only a fool can be siding with Kabam on this

No true scottsman fallacy, it could also be that we are coders therefore we know how coding works. Only a non coder thinks that all bugs can be fixed in , especially things like "back draft intercept" where the cause of it not working anymore is them actually fixing the connectivity and slowness of the game for many.

unknown

This content has been removed.

Threedeadkings

Then you missed the point of the post. The point was not to not complain, it was to not be so out of touch and just assume it’s kabam playing dirty.

However the “dumb blonde” retaliation just shows where your mindset is so I’ll speak in terms you can understand. *puts on girls are stupid and can’t play game or understand them hat* some things are an easy fix, like Tarzan hungry so Tarzan kill. Some things are a hard fix, like your apparent misogynistic attitude, that will take years to correct. But if you want to scream foul every time Kabam fixes an issue that “benefits the player” but takes forever if it’s helping them, well you can’t fix stupid.

PS I’m actually a brunette, so your dumb blonde “joke” shows that you attribute stupid females with blondes, and that is a whole other can of worms. However I hear talking to a therapist about your problems help. And good news, I happen to be friends with a few, but you’ll have to get past them being blonde, female, oh yeah and smart.

All that side, I will reiterate my point. Stop commenting/posting screaming foul every time they fix something that could be used unfairly by players, because that is all this Cull nonsense is. People upset because something broke and numbers got inflated, so people will try to use this to their advantage knowing full well those damage numbers were never meant to be that high. And then cry like a schoolgirl with a skinned knee when their new toy is returned to his former self.

—————————

That wasn’t what you meant. You were very literal and expressive, demanding those without an ounce of coding knowledge to stop commenting because we have no clue how hard it is. Nothing in your entire content suggests otherwise. I did not for once misquote you.

And where did I ever openly and directly express that ‘dumb blonde moment’ must surely be of a softer gender? It can well be dumb brunettes or crappy dreadlocks for all I care. My message is against the ‘you’re not knowledgeable so shut up’ post. You chose to take offense and brand me personally as an myso-whatever. Never once in that post had made reference to you directly or question your ability to think just because you may well be of a softer gender (or not).

The gist is, this isn’t about CO. It may well be a result of CO’s announcement but there’s no soap operas here. It’s again you who’s sensationalising it. The topic is as simple as ABC (please read it again if that’s too overly complex for you). Again, it’s you who’s jumping with your assertions.

You don’t like your Mechanic calling you every minute about every bolt they pulled but I do. That’s accountability to me. That’s communication to me. That’s an expression of customer service to me. Now who in the world are you to chide, chaff, or shut others down from requesting an improvement to it?

So again, why is it so important for me to understand coding in order to comment about how I feel? Does it matter? all these silly posts suggesting ‘it’s a complex issue so don’t question the dev’’ is whitewash to me.

Try telling your bank that it a ‘complex issue’ why you’re continuously late servicing your mortgage and see if you get similar empathy.

xNig

To the OP,

The logic is actually pretty simple.

If it’s an issue that affects everyone, then everyone is put on the same playing field, eg, everyone fighting Sentinels in AQ gets rekted trying to punish his SP1.

However, if it’s an issue that gives benefits to a small subset of players, eg the recent Cull bug, then it only benefits the players with those champs and unevens the playing field for everyone else, eg people using Cull to 100% Variant or A6 with minimal item use while others have to slog through it.

crossshatter

People who don’t know anything about game development should never complain about some bugs being fixed and others being “ignored” if you have no clue what it takes to rewrite lines upon lines of codes for harder issues, or how pushed vs downloaded fixes work, then you should not sit here and split hairs.

There are things that are easy and simple to fix and then some that take compiling data and basically rewriting entire blocks of code. There are things that can be pushed on the backend, and things that require a download.

I’d rather a bug stay in the game and it be fixed and no other issues come up, than a fix be listed and it break 4 other things. You all see biased content being fixed faster because that’s what you want to see. But you fail to see what they actually do to make the game run.

I’d love to see even one of you sit at a desk for 10 hours looking at lines of code, running tests on each correction, thinking you fixed something then seeing it break again. I’d love to see you guys trying to fix something for days upon months and then reading on the forums that you think Kabam doesn’t care. I’d love to see you actually fix something game breaking only to see users complain you only did it because the players benefited from it.

What it comes down to is that you guys really only want bugs in the game that helps you. And when those bugs get fixed you all rant and QQ.

Get over it. And understand how things actually work when developing a game. It’s not as simple as the lot of you believe.

Then that makes them bad devs.Listen,I know it’s hard to rewrite that ton of codes but this is their job,fix bugs within their game.if it’s like what you said then the game will be awful and the game maintaining that doesn’t let us play will be for no reason
[removed by Moderator]

Diksh619

They fix what they can. There is a priority list, however. Same list that any game team I can think of adheres to. If there's an issue that breaks the game or is exploitative, that becomes a top priority. They have to resolve it as fast as they can. This isn't something that's ideal, and most often involves the fastest resolution that creates the least amount of subsequent problems. They don't have a choice in those cases. Some issues take longer to resolve, some aren't resolved yet. Some aren't even issues, just people misunderstanding what's at play. One thing is for sure. No Dev wants any bugs. Let alone picks and chooses based on what hurts Players. That's just not a thing.

Brother do you work for or have worked for KABAM in the past. You seem to be very sure about how they operate. Please take our sides sometimes sir!

unknown

This content has been removed.

Threedeadkings

They fix what they can. There is a priority list, however. Same list that any game team I can think of adheres to. If there's an issue that breaks the game or is exploitative, that becomes a top priority. They have to resolve it as fast as they can. This isn't something that's ideal, and most often involves the fastest resolution that creates the least amount of subsequent problems. They don't have a choice in those cases. Some issues take longer to resolve, some aren't resolved yet. Some aren't even issues, just people misunderstanding what's at play. One thing is for sure. No Dev wants any bugs. Let alone picks and chooses based on what hurts Players. That's just not a thing.
Brother do you work for or have worked for KABAM in the past. You seem to be very sure about how they operate. Please take our sides sometimes sir!
Your side is deliberately getting itself misinformed.

I could absolutely despise kabam as a company and I would still find it exceptionally silly to believe that they're basically willingly sabotaging their own game.

This isn't you vs kabam and friends, this is essentially you vs reason.

Sure, we purposefully and wilfully will ourselves to be misinformed. And of course it sure ain’t ‘we vs Kabam and friends’. It’s all about reasoning.

So reason this with me. I have not heard about any shape and form about pure skill for a good 2 years. So what would be my main reason to not voice my dissatisfaction and form my own conclusion that other issues takes precedent over another?

Oh wait.. i know the answer:

it’s a ‘complex issue and it cannot be resolved overtime or maybe an aeon for that matter’;

or perhaps this is better -

‘Shut it. The devs knows best. You’re not the devs and you don’t know coding and so you don’t know the complexity that comes with it’..

Right... reasons... pfft... if only we even have one to cling to ...

unknown

This content has been removed.

HENRIQUE_FORTE

When act 6.2 was released, Champion and Sinister were bugged. These bugs were very harmful to the players. What would a decent company do? Shut down 6.2. until fixed. What did they do? Kept act 6.2. and allowed players to melt units/revives/money to defeat those champions.

Bugs benefit players = instant fix. Fact.

Lormif

People who don’t know anything about game development should never complain about some bugs being fixed and others being “ignored” if you have no clue what it takes to rewrite lines upon lines of codes for harder issues, or how pushed vs downloaded fixes work, then you should not sit here and split hairs.

There are things that are easy and simple to fix and then some that take compiling data and basically rewriting entire blocks of code. There are things that can be pushed on the backend, and things that require a download.

I’d rather a bug stay in the game and it be fixed and no other issues come up, than a fix be listed and it break 4 other things. You all see biased content being fixed faster because that’s what you want to see. But you fail to see what they actually do to make the game run.

I’d love to see even one of you sit at a desk for 10 hours looking at lines of code, running tests on each correction, thinking you fixed something then seeing it break again. I’d love to see you guys trying to fix something for days upon months and then reading on the forums that you think Kabam doesn’t care. I’d love to see you actually fix something game breaking only to see users complain you only did it because the players benefited from it.

What it comes down to is that you guys really only want bugs in the game that helps you. And when those bugs get fixed you all rant and QQ.

Get over it. And understand how things actually work when developing a game. It’s not as simple as the lot of you believe.
Then that makes them bad devs.Listen,I know it’s hard to rewrite that ton of codes but this is their job,fix bugs within their game.if it’s like what you said then the game will be awful and the game maintaining that doesn’t let us play will be for no reason
[removed by Moderator]

No it does not make them bad dev... Yes it is their job to fix the bugs, but that does not mean it needs to be on your arbitrary time frame. In fact this game is good in relation to fixing bugs relative to many other large scale games.

Ultra8529

We can argue all day back and forth as to whether Kabam is truly selective over the kind of bugs that they fix, but we won't get anyway.

I would argue that the mere fact that there is such a perception (86% of the voters hold this view at the time of writing) is a problem in and of itself. It is indicative of a lack of trust as to how the game is being run and managed. This problem won't exist if Kabam is more open, transparent and communicative with regard to its bug fixes.

Put well-established bugs on the known issues list. What's so hard about that? All it does then is create accountability in that the players then have a legitimate expectation for that issue to be resolved eventually. Neglecting to do that sends a strong signal that you are not recognising it as an issue at all, which then starts the road down believing that Kabam is not going to fix that bug.

Lormif

We can argue all day back and forth as to whether Kabam is truly selective over the kind of bugs that they fix, but we won't get anyway.

I would argue that the mere fact that there is such a perception (86% of the voters hold this view at the time of writing) is a problem in and of itself. It is indicative of a lack of trust as to how the game is being run and managed. This problem won't exist if Kabam is more open, transparent and communicative with regard to its bug fixes.

Put well-established bugs on the known issues list. What's so hard about that? All it does then is create accountability in that the players then have a legitimate expectation for that issue to be resolved eventually. Neglecting to do that sends a strong signal that you are not recognising it as an issue at all, which then starts the road down believing that Kabam is not going to fix that bug.

This problem would persist no matter how open and transparent they are. If you look at any game and narroow in on the ones that keep an open bug report for each and every bug out in a public forum they will still have this issue. When a game involves micro transactions it will be even worse.

The problem with the "known issues" list is their idea of what it is for may be very different than ours. For them it may be "issue confirmed", not as in the problem you see, but the problem that is causing the problem you see. Both are valid interpretations, the issue causing the bug being known seems to be how they look at it.. From a developers perspective that will be how they like to handle it..

Ultra8529

We can argue all day back and forth as to whether Kabam is truly selective over the kind of bugs that they fix, but we won't get anyway.

I would argue that the mere fact that there is such a perception (86% of the voters hold this view at the time of writing) is a problem in and of itself. It is indicative of a lack of trust as to how the game is being run and managed. This problem won't exist if Kabam is more open, transparent and communicative with regard to its bug fixes.

Put well-established bugs on the known issues list. What's so hard about that? All it does then is create accountability in that the players then have a legitimate expectation for that issue to be resolved eventually. Neglecting to do that sends a strong signal that you are not recognising it as an issue at all, which then starts the road down believing that Kabam is not going to fix that bug.
This problem would persist no matter how open and transparent they are. If you look at any game and narroow in on the ones that keep an open bug report for each and every bug out in a public forum they will still have this issue. When a game involves micro transactions it will be even worse.

The problem with the "known issues" list is their idea of what it is for may be very different than ours. For them it may be "issue confirmed", not as in the problem you see, but the problem that is causing the problem you see. Both are valid interpretations, the issue causing the bug being known seems to be how they look at it.. From a developers perspective that will be how they like to handle it..

If that were the case, I don't see why no mod has come out and said so at all. Again - communication.

unknown

This content has been removed.

Lormif

We can argue all day back and forth as to whether Kabam is truly selective over the kind of bugs that they fix, but we won't get anyway.

I would argue that the mere fact that there is such a perception (86% of the voters hold this view at the time of writing) is a problem in and of itself. It is indicative of a lack of trust as to how the game is being run and managed. This problem won't exist if Kabam is more open, transparent and communicative with regard to its bug fixes.

Put well-established bugs on the known issues list. What's so hard about that? All it does then is create accountability in that the players then have a legitimate expectation for that issue to be resolved eventually. Neglecting to do that sends a strong signal that you are not recognising it as an issue at all, which then starts the road down believing that Kabam is not going to fix that bug.
This problem would persist no matter how open and transparent they are. If you look at any game and narroow in on the ones that keep an open bug report for each and every bug out in a public forum they will still have this issue. When a game involves micro transactions it will be even worse.

The problem with the "known issues" list is their idea of what it is for may be very different than ours. For them it may be "issue confirmed", not as in the problem you see, but the problem that is causing the problem you see. Both are valid interpretations, the issue causing the bug being known seems to be how they look at it.. From a developers perspective that will be how they like to handle it..

If that were the case, I don't see why no mod has come out and said so at all. Again - communication.

Has anyone else asked them? Sometimes the communication has to start with you.

unknown

This content has been removed.

Ultra8529

We can argue all day back and forth as to whether Kabam is truly selective over the kind of bugs that they fix, but we won't get anyway.

I would argue that the mere fact that there is such a perception (86% of the voters hold this view at the time of writing) is a problem in and of itself. It is indicative of a lack of trust as to how the game is being run and managed. This problem won't exist if Kabam is more open, transparent and communicative with regard to its bug fixes.

Put well-established bugs on the known issues list. What's so hard about that? All it does then is create accountability in that the players then have a legitimate expectation for that issue to be resolved eventually. Neglecting to do that sends a strong signal that you are not recognising it as an issue at all, which then starts the road down believing that Kabam is not going to fix that bug.
This problem would persist no matter how open and transparent they are. If you look at any game and narroow in on the ones that keep an open bug report for each and every bug out in a public forum they will still have this issue. When a game involves micro transactions it will be even worse.

The problem with the "known issues" list is their idea of what it is for may be very different than ours. For them it may be "issue confirmed", not as in the problem you see, but the problem that is causing the problem you see. Both are valid interpretations, the issue causing the bug being known seems to be how they look at it.. From a developers perspective that will be how they like to handle it..

If that were the case, I don't see why no mod has come out and said so at all. Again - communication.
Has anyone else asked them? Sometimes the communication has to start with you.

Yes there have been tons of posts asking moderators why certain issues have not been migrated to the known issues list.

The reply? Nothing. Silence.

Lormif

We can argue all day back and forth as to whether Kabam is truly selective over the kind of bugs that they fix, but we won't get anyway.

I would argue that the mere fact that there is such a perception (86% of the voters hold this view at the time of writing) is a problem in and of itself. It is indicative of a lack of trust as to how the game is being run and managed. This problem won't exist if Kabam is more open, transparent and communicative with regard to its bug fixes.

Put well-established bugs on the known issues list. What's so hard about that? All it does then is create accountability in that the players then have a legitimate expectation for that issue to be resolved eventually. Neglecting to do that sends a strong signal that you are not recognising it as an issue at all, which then starts the road down believing that Kabam is not going to fix that bug.
This problem would persist no matter how open and transparent they are. If you look at any game and narroow in on the ones that keep an open bug report for each and every bug out in a public forum they will still have this issue. When a game involves micro transactions it will be even worse.

The problem with the "known issues" list is their idea of what it is for may be very different than ours. For them it may be "issue confirmed", not as in the problem you see, but the problem that is causing the problem you see. Both are valid interpretations, the issue causing the bug being known seems to be how they look at it.. From a developers perspective that will be how they like to handle it..

If that were the case, I don't see why no mod has come out and said so at all. Again - communication.
Has anyone else asked them? Sometimes the communication has to start with you.
Yes there have been tons of posts asking moderators why certain issues have not been migrated to the known issues list.

The reply? Nothing. Silence.

that is not the type of question we are talking about.

Ultra8529

We can argue all day back and forth as to whether Kabam is truly selective over the kind of bugs that they fix, but we won't get anyway.

I would argue that the mere fact that there is such a perception (86% of the voters hold this view at the time of writing) is a problem in and of itself. It is indicative of a lack of trust as to how the game is being run and managed. This problem won't exist if Kabam is more open, transparent and communicative with regard to its bug fixes.

Put well-established bugs on the known issues list. What's so hard about that? All it does then is create accountability in that the players then have a legitimate expectation for that issue to be resolved eventually. Neglecting to do that sends a strong signal that you are not recognising it as an issue at all, which then starts the road down believing that Kabam is not going to fix that bug.
This problem would persist no matter how open and transparent they are. If you look at any game and narroow in on the ones that keep an open bug report for each and every bug out in a public forum they will still have this issue. When a game involves micro transactions it will be even worse.

The problem with the "known issues" list is their idea of what it is for may be very different than ours. For them it may be "issue confirmed", not as in the problem you see, but the problem that is causing the problem you see. Both are valid interpretations, the issue causing the bug being known seems to be how they look at it.. From a developers perspective that will be how they like to handle it..

If that were the case, I don't see why no mod has come out and said so at all. Again - communication.
Has anyone else asked them? Sometimes the communication has to start with you.
Yes there have been tons of posts asking moderators why certain issues have not been migrated to the known issues list.

The reply? Nothing. Silence.
that is not the type of question we are talking about.

I don't see why not? If the moderators have a different idea as to what it means to be a "known issue", that would naturally be the explanation given as to why something is not making its way onto that list despite repeated requests.

Again, it is incumbent on them to be transparent and explain their reasoning and thought process. Players will just keep asking and wondering otherwise.

Colinwhitworth69

Kabam , please don't close this thread. It's an opinion post and not against any tnc.

Seeing how quickly you have identified the issue where Cull was doing insane damage and was benefitting the player base, I was wondering when will you fix Corvus who takes Coldsnap damage and is completely bugged on physical resistance nodes.6.2 sinister issues, indistructible The Champion on 6.2.6 issue and many more have gone into the state "we're looking into it ". Why do they not get fixed sooner ? Any why does issues that benefit us get fixed in a day or 2 ?

You are creating a argument without using a significant set of facts. To evaluate your issue, you would need to provide evidence of many bugs that were fixed or have not been fixed, so we would know whether this is actually an issue outside of Cull Obsidian.

Every release comes with a list of bug fixes, so you could start there by figuring out whether this was a bug raised by players and whether it was a bug that benefited players or made the game harder for us. But even then that would only address the known fixes, not the unknown list of bugs raised by players or Kabam itself.

Don't jump to conclusions without the facts. You might be right, but at this point all you are doing is stating an opinion based on one event. And in the age of social media, such statements get passed around by people until some believe they are fact.

Kabam Lyra

Hi all,

We appreciate everyone's concern about the timeliness of bug fixes. The process of identifying an issue, replicating it through in-house testing, determining and implementing a fix is something that can vary in the amount of time it takes depending on the nature and severity of the issue. Bug fixes are not prioritized in such a way as to purposefully disadvantage players.