I do make many, many Bug reports ingame and one thing that really really is bugging me out, is I will never get a feedback if it is an acknowledged Bug, me misunderstanding the function, or anything else.
I have to research the web and or discord, ask around if anybody is aware of the problem, if its a problem after all and so on. Is it planned, to give players a feedback at any point?
I dont know how hard it would be to implement smth like that, but for the one who checks the report a clickbox: acknowledged Bug/works as intended/under review and to get that information as player would be awesome.
I rly love LE and try to be as helpfull as a player can be. I try to find use for nearly all items and stuff and combos, just to check it how and understand how it works. So it often happens nobody seems to have the same issue, since its a very very unpopular build or combo.
I even tried to standarize my reports like:
Issue:
Items:
Affix:
Skills:
Skillnodes:
Passive nodes (if needed):
What i expect:
What is actually happening:
putting that time and effort in every Report and having absolutly no feedback is hard.
Posting everything a second time on the forum - after searching if there is an other bug report with same issue and if there is alrdy an answer or not, what was the discussion there, is it rly the same problem, etc⌠to avoid unnessecary Threads and even then not to get any answer is hard to take.
So maybe there would ne an option with a reported bug log and the clickbox answer of the reviewer. Just to know if its a real bug, me misunderstanding the function or even âwe dont know, have to check carefullyâ (under review) would soothe my soul
You acknowledge that something is going on, but you never, ever write down even remotely what the bug does until it is fixed. You provide the issue post-mortem for that one.
Even acknowledging it at all is risky for that. What do you think happens when it is acknowledged? Heaven for anyone which wants to exploit that. âHey, I hear there is something existing⌠letâs check the internet out to find what exactly it is and do it too!â
Thatâs a fundamental rule that you are very careful in regards to exploits and dupes with providing info to your customers, if you donât youâll swiftly have a major issue likely killing your product.
Gameplay bugs should be public. Exploit bugs shouldnât. Every time theyâre revealed they only hurt the game. And this is not just for LE.
Exploit bugs are almost always already known by the devs. Almost always theyâre already working on fixing them, since theyâre priority issues.
If you think the devs arenât aware of it, then you should contact them privately (or use the bug report tool)
Making an exploit/dupe known will only lead to a lot of people that werenât aware of it going out of their way to try it out and try to benefit from it, further crashing your economy.
EDIT: As an example to maybe get my point across better:
Imagine a self checkout machine in the supermarket. It has a vulnerability where if you flash your phone light on the scanner it will scan all items at 0.01c rather than their price.
The ones in charge detect this issue and it will require 2 days to fix.
If you donât say anything, maybe youâll get 2-3 people using it, most of the time by mistake. Youâll be monitoring the situation and you can easily identify it.
If you announce that thereâs a vulnerability, more people will be trying to find out what it is and more will stumble upon it by trial and error and sometimes by word of mouth.
If you announce that thereâs a vulnerability and exactly what it is, youâll get thousands of people abusing it in the couple days until itâs fixed. And thereâs no way to properly track it anymore as well.
Especially because, unlike what you said, making it public wonât make the devs work on it faster. Theyâre already working on it as fast as they can. It will still take 2 days to fix. That hasnât changed. What changed is how many people will be exploiting it and how much it will affect the economy.
So exploits/dupes should always be handled as discreetlly as possible and should only be made public after theyâve been fixed, if at all.
If there is a duping or currency bug it should be tackeled instantly. I remember playing WoW one day and doing a quest and I was happy because there was enough respawn at once. The ntthey wanted to ban me because they thought i abused a bug when i was only happy to do a quest in a sane time because the mobs respawned in a fast enough rate so 10 people were able to do it without stealing kills.
If the spawn was disabled there wouldâve been no issue outside of waiting for a day tops untill itâs fixed. Devs solve issues but most devs only patch if they have xyz done and donât treat economy bugs and exploits as severly as you do. If bugs are out in the open they can punish everyone using it and avoid false positives when someone is simply doing a quest for 5 minutes vs people who kill enemys 24/7 for a week and accumulate a ton of wealth while the devs sit on their hands.
As I said above. Everything that makes Devs move instantly and donât wait arround is a good thing. Noone can say âI donât know!â if it is public.
And should be permabanned for it
I understand your point i just ahve a completely different view on it and I think devs of games should be held accountable if they leave bugs in the open or take their sweet time fixing things. There are plenty of ways to get stuff done fast and to implement a solution untill stuff can finaly be fixed.
Just a spawn. Not so severe if switched off. My recent dupe bug report was on a much more important mechanic. And Iâm not gonna tell you where and how
They generally do, but it takes time for devs to become aware of an issue, work out how itâs happening, work out how to fix it without breaking something else & then make sure that their proposed fix functions as intended.
So you want the devs to have to punish more people?
Kneejerk reactions arenât a good thing from devs or players.
Which would be a much wider group of people if you had your way & exploits were widely known.
And they generally wind up creating more work than the time they âsaveâ.
Sure. But until then all the bot accounts that werenât aware of it become aware of it and exploit it hard, crashing the economy even further. And they donât care if they get perma banned because that is already their fate, itâs just a matter of how much profit they can squeeze out before that.
Which, in this case, would be a lot more than usual.
But the issue is that almost always the devs are already working on a fix for it. It becoming public wonât make them fix it faster. Programming isnât a miracle solution where you look at your bug and it magically disappears instantly.
It often requires several changes and testing those changes before it can be released.
If there is a bandaid solution to be applied they already did it. But even that bandaid solution requires time to implement.
If you place a pizza in the oven for 30 minutes it will be ready to eat. There isnât a magical solution that will make the pizza be ready in 1 minute. If you simply try to turn the heat what you end up with is a charred mess, which is the perfect analogy of what happens when exploits/dupes are publicly shared.
Absolutely, and while I usually am in the group of âDevelopers, tell is everything going on at all times!â this is one of the major exeptions.
Tackle it but go ahead and even delete the posts related to it in the second they come up. Inform the people that itâs been known and acknowledged and worked on when they provide the information⌠but donât ever let the information leak out and hinder the speed of leaking to the utmost of your ability.
Itâs not only one game which got killed by bad management of that aspect, itâs really really dangerous and good games have broken entirely because of it.
So a bug-report on the bug-report section should get someone permabanned?
You cannot have it both ways⌠you either have a information embargo about the topic and hence remove it whenever visible with no mention at all (action or not is a separate topic) or you make it visible to everyone. There is no reliable in-between.
And thatâs the proper action! Kudos.
Only the devs should know about it, but reporting and making it publicly visible by a customer should never lead to negative consequences. Remove post, acknowledge per PM, praise for providing information and then get the issue fixed. But never leave it visible.
Exactly. If they need to pay access and get 10⏠more out then the license price is then theyâve already won. You can after all run 10 or 20 per machine at once, multi-clienting is really hard to tackle as so many options exist which arenât visible to devs and even shouldnât be visible to them at times.
And thatâs completely up to you. Just to amuse me. How long did it take to be removed?
And still there are games that leave such bugs in their games for days, weeks and even months given my experience on the topic. Not only are devs slow to handle this kind of stuff from my experience but they only tap ppl on the wrist about it. In my WoW example somone made millions with the bug and got a 24h ban and that was it. Not even the money was removed.
If said persons are bug abusesers? Yes.
What still leaves people who play legit or who are so smart they are never cought.I rather have a smaller playerbase of genuine players then a snakepit that jumps on every opportunity there is to use punishable means to get things.
And itâs not about saving time itâs about saving fairness and the ingame community. The integrety of the whole product so to speak. Yes this takes time and effort but it should be done if it helps to keep stuff in line.
Depends on the reactionspeed. On top of this I know someone in an extended friendgroup how programmed bots for a living while he was student. The whole cheating and botting community works openly togheter and much faster and more efficent then ordinary users. There are vulanrability spread cheats for all kind of engines and what worked in the past and what might possibly work after certain changes. itâs crazy to me.
The ammount of stuff they got and money they made was sad but they were always ahead. So will there be more real harm done if bugs are out in the open or if they are hidden and devs can take their time instead of taking some more options to stop the problem? Havenât there been games were P2P trade was disabled just to stop some shady stuff? Just to throw an example in here.
Not from my experience no. There is even a game where a dupe was reported to the devs in a beta. They didn#t reacted to it, it was made public in the beta so they need to adress it. Guess what? it was useable for 3 seasons in that game and people did so.
Other games had more holes in it then swiss cheese and had to disable family share on steam for example ebcause people cheated with this option however they did it. Donât know donât care.
wtf? If a Pizza needs 30 Minutes in the oven and it is ready after 30 minutes then itâs working like intended. What kind of an example is this? If I drop a stone it falls to the erath! Do you want to come up with an even more binary example that isnât exploitable to make a point?
And Iâm fine with it. Iâm in the group of âDevs have chosen to put their game and themselfs out into the open and should be held accountable for what they do or donât.â. They are no charity case we need to prop up or children who didnât knew better. It was their choice and they take money for it so get your stuff done. From my personal experince LE devs are in the âfaster responceâ bracked but there is still room to get better at it.
This would be a thing but mostly youâll hear something like âThis is an ongoing prcess and we always work on improving our product.â kind of politician talk. I need to go through stuff maybe I cann find the google doc of that game I canât remember the name of that had a spread sheet of known bugs, prioritys and what was done. This was transparent and people were able to visit the sheet and search for bugs and if they were already reported. Good times.
There are some steps to this. Finding a bug? No problem. Testing arround to reproduce it? No problem. Use it again and agian and again. Big problem. So obviously noone is punished for reporting bugs and I donât know why you are doing mentaly gymnastics to make a âBug abusers should be punishedâ into this âBut what aboutâŚ?â section.
As I said somewhere above. Iâm for transperency and everything that makes devs work faster on important stuff. Iâm for clear boundry people can be pointed at and be told âPlay stupid games, win stupid prices. You are banned.â.
I get everyones point who says that this âgamebreakingâ stuff should be handled with secrecy so itwonât spread but again, from my experience the devs and tester and players canât keep up with the people who made exploiting systems their living.
From my point of view itâs fair game if everything is out in the open and punished if bugs are knowingly abused. People who want to mess arround and cheat and whatnot have an offline mode to have fun with and thatâs completely fine.
where and how