- Joined
- December 3, 2020
- Messages
- 9,001
- Points
- 326
1. Bug reports being denied with template responses
Whenever a bug report gets denied, the response is almost always the same template with multiple possible reasons such as:
• Insufficient information
• "Our" inability to replicate the issue
• The bug may have already been reported by someone else beforehand
• This may not have been a bug
But which of these reasons is it actually?
From the player side, the report is being made because we already believe we have gathered the required information. If the issue had insufficient information, then what exactly was missing? What part of the report was not enough?
If the issue could not be replicated, how exactly was it tested and under what conditions? why am I able to replicate it whenever I want ?
If the bug may have already been reported by someone else beforehand, was there ever any report? Bug reports are private specifically so players cannot abuse them, so from our side there is no way to verify that claim. The only thing we can judge by is whether the bug existed for a long time. If the bug has been present for years, then unless someone reported it at the exact same time, the only other possibility is that another report has been sitting there pending for years. If that is the case, then what were the developers doing all that time?
And if the final possibility is that “this may not have been a bug”, then that raises another question. If it is not a bug, then why are players punished or warned for abusing it? If a developer states that something is not a bug, does that mean players are free to use it however they want without getting into trouble?
Because all these possibilities are listed together in a template response, the reporter has no idea which one actually applies. Like why in world would we report if we thing any of that criteria is missing? That means there is no way to improve future reports or even understand what went wrong with the current one.
This exact same template system also exists for suggestions, where multiple possible reasons are listed without explaining which one actually applied. So staff gives all this incentives for players to make reports and give suggestions but dont even even handle the one at hand properly, so why bother ?
2. Suggestions being denied but implemented later anyway
There have also been cases where suggestions were denied, and later the developers implemented something related to it on their own anyway.
One example is the “Non-player spectator warning” suggestion. The idea was simple: players should receive a warning intimation if someone is spectating them, because ghosting is allowed and they should not consider stealth as a viable strategy as the spectating player would just give off any strategy you were planning.
The suggestion was rejected.
Then later the developers implemented their own version of it when no one even asked. Not only was no credit given to the original suggestion, the implementation itself completely missed the point. The system only notifies you if a friend is spectating you. But why would that even matter? You can already see your friends using the friends list command. The entire reason the suggestion existed was to detect non-friends spectating and potentially ghosting gameplay. One point which was given against the original suggestion was that what if staff was spectating, then what, the warning would just warn the player and he would stop cheating. Are telling me you can't code in an exception for staff? Are you that incompetent even when all your code is being written by GPT ?
So multiple players point out an issue, a suggestion is made and rejected, and then developers go and implement their own version anyway while completely ignoring the original reasoning behind it. At that point it raises a simple question: why ask for suggestions at all if the plan is to ignore them and do your own thing ?
3. Punch to deposit
Another example is the “punch to deposit” feature.
Players had been suggesting this feature for a long time and those suggestions were consistently denied. Then later the developers decided to implement it anyway, but in a very reckless way.
The feature was added without any option to toggle it off. This means players who do not want the feature now have to deal with accidental deposits, and it also creates issues when fighting near chests because accidental clicks can trigger deposits.
So first the suggestion is denied whenever players bring it up. Then the developers implement it anyway on their own terms. Then they make the feature mandatory for everyone without any option to disable it. And on top of that, the original suggesters do not even receive credit.
So first the suggestion is rejected because the developers apparently do not like it, then they do it anyway, force that feature on everyone which they earlier did not liked, and the people who suggested it do not even get acknowledged?
4. Accepted suggestions that seem to go nowhere
Even when suggestions are accepted, it is often hard to tell what actually happens afterward.
For example, I suggested that lootbox boosters should multiply lootboxes instead of increasing drop chance so that the effect would actually be visible instead of feeling like a placebo. That suggestion was accepted, but even after months there is no clear way to tell if anything was done with it.
There are also several suggestions that were accepted around five months ago which do not appear to have been implemented yet, at least not in any visible way:
• Bedwars mode filter in arguments instead of a dropdown
• Left-Right trim in punishments search
(these suggestions are accepted but not implemented)
From the player side it becomes difficult to understand whether these are still planned, partially implemented, or simply forgotten.
After a while this whole process starts to feel a bit strange. Bug reports get denied with templates that do not explain the reason. Suggestions get denied the same way, sometimes show up later in a different form, sometimes get implemented without credit, and sometimes get accepted but never appear afterward.
At some point it starts to feel like there is very little accountability in how these things are handled. And while all this is going on management shamelessly pretend to be interactive with players, asking for ideas which they very well know they wont implement, promising fake incentives. Don't even get me started on player reports as that is even more bogus.
And then after all that, when players stop bothering with reports or suggestions and quietly leave, and they wonder why people leaving out of nowhere.
Whenever a bug report gets denied, the response is almost always the same template with multiple possible reasons such as:
• Insufficient information
• "Our" inability to replicate the issue
• The bug may have already been reported by someone else beforehand
• This may not have been a bug
But which of these reasons is it actually?
From the player side, the report is being made because we already believe we have gathered the required information. If the issue had insufficient information, then what exactly was missing? What part of the report was not enough?
If the issue could not be replicated, how exactly was it tested and under what conditions? why am I able to replicate it whenever I want ?
If the bug may have already been reported by someone else beforehand, was there ever any report? Bug reports are private specifically so players cannot abuse them, so from our side there is no way to verify that claim. The only thing we can judge by is whether the bug existed for a long time. If the bug has been present for years, then unless someone reported it at the exact same time, the only other possibility is that another report has been sitting there pending for years. If that is the case, then what were the developers doing all that time?
And if the final possibility is that “this may not have been a bug”, then that raises another question. If it is not a bug, then why are players punished or warned for abusing it? If a developer states that something is not a bug, does that mean players are free to use it however they want without getting into trouble?
Because all these possibilities are listed together in a template response, the reporter has no idea which one actually applies. Like why in world would we report if we thing any of that criteria is missing? That means there is no way to improve future reports or even understand what went wrong with the current one.
This exact same template system also exists for suggestions, where multiple possible reasons are listed without explaining which one actually applied. So staff gives all this incentives for players to make reports and give suggestions but dont even even handle the one at hand properly, so why bother ?
2. Suggestions being denied but implemented later anyway
There have also been cases where suggestions were denied, and later the developers implemented something related to it on their own anyway.
One example is the “Non-player spectator warning” suggestion. The idea was simple: players should receive a warning intimation if someone is spectating them, because ghosting is allowed and they should not consider stealth as a viable strategy as the spectating player would just give off any strategy you were planning.
The suggestion was rejected.
Then later the developers implemented their own version of it when no one even asked. Not only was no credit given to the original suggestion, the implementation itself completely missed the point. The system only notifies you if a friend is spectating you. But why would that even matter? You can already see your friends using the friends list command. The entire reason the suggestion existed was to detect non-friends spectating and potentially ghosting gameplay. One point which was given against the original suggestion was that what if staff was spectating, then what, the warning would just warn the player and he would stop cheating. Are telling me you can't code in an exception for staff? Are you that incompetent even when all your code is being written by GPT ?
So multiple players point out an issue, a suggestion is made and rejected, and then developers go and implement their own version anyway while completely ignoring the original reasoning behind it. At that point it raises a simple question: why ask for suggestions at all if the plan is to ignore them and do your own thing ?
3. Punch to deposit
Another example is the “punch to deposit” feature.
Players had been suggesting this feature for a long time and those suggestions were consistently denied. Then later the developers decided to implement it anyway, but in a very reckless way.
The feature was added without any option to toggle it off. This means players who do not want the feature now have to deal with accidental deposits, and it also creates issues when fighting near chests because accidental clicks can trigger deposits.
So first the suggestion is denied whenever players bring it up. Then the developers implement it anyway on their own terms. Then they make the feature mandatory for everyone without any option to disable it. And on top of that, the original suggesters do not even receive credit.
So first the suggestion is rejected because the developers apparently do not like it, then they do it anyway, force that feature on everyone which they earlier did not liked, and the people who suggested it do not even get acknowledged?
4. Accepted suggestions that seem to go nowhere
Even when suggestions are accepted, it is often hard to tell what actually happens afterward.
For example, I suggested that lootbox boosters should multiply lootboxes instead of increasing drop chance so that the effect would actually be visible instead of feeling like a placebo. That suggestion was accepted, but even after months there is no clear way to tell if anything was done with it.
There are also several suggestions that were accepted around five months ago which do not appear to have been implemented yet, at least not in any visible way:
• Bedwars mode filter in arguments instead of a dropdown
• Left-Right trim in punishments search
(these suggestions are accepted but not implemented)
From the player side it becomes difficult to understand whether these are still planned, partially implemented, or simply forgotten.
After a while this whole process starts to feel a bit strange. Bug reports get denied with templates that do not explain the reason. Suggestions get denied the same way, sometimes show up later in a different form, sometimes get implemented without credit, and sometimes get accepted but never appear afterward.
At some point it starts to feel like there is very little accountability in how these things are handled. And while all this is going on management shamelessly pretend to be interactive with players, asking for ideas which they very well know they wont implement, promising fake incentives. Don't even get me started on player reports as that is even more bogus.
And then after all that, when players stop bothering with reports or suggestions and quietly leave, and they wonder why people leaving out of nowhere.
Last edited:
