Fix the bugs in the game!

"
ciel289 wrote:
the problem isnt fixing known bugs 99.9% of the time

its finding the bug and reliably reproduce them

if you can reproduce them you can start narrowing down what exactly caused it,this can be a lot of work with how many things happen in poe at once and how fast they happen


This is why it is necessary to rewrite your code from the ground up. It is simply too painful to blindly try and recreate something.
QA should be part of the process and switch to/ work with UX whenever their workload is light.

Trying to rebuild something from the ground-up is also the only way to know your code inside and out, hence making bug finding multiplicatively easier.

Rewriting code-base ground-up every 5-10 years just makes sense. The more you rely on imported stuff, the more you can stop relying on imported stuff during this process, and the team will be more proficient every 5-10 years hence a better code-base with better documentation.

Get the dual QA/ UX guys to help with documentation so it's a better experience to read through.
Last edited by Ogre_Dylan#3868 on Sep 5, 2024, 2:45:53 AM
"
Dylan_Schreiner wrote:
"
ciel289 wrote:
the problem isnt fixing known bugs 99.9% of the time

its finding the bug and reliably reproduce them

if you can reproduce them you can start narrowing down what exactly caused it,this can be a lot of work with how many things happen in poe at once and how fast they happen


This is why it is necessary to rewrite your code from the ground up. It is simply too painful to blindly try and recreate something.
QA should be part of the process and switch to/ work with UX whenever their workload is light.

Trying to rebuild something from the ground-up is also the only way to know your code inside and out, hence making bug finding multiplicatively easier.

Rewriting code-base ground-up every 5-10 years just makes sense. The more you rely on imported stuff, the more you can stop relying on imported stuff during this process, and the team will be more proficient every 5-10 years hence a better code-base with better documentation.

Get the dual QA/ UX guys to help with documentation so it's a better experience to read through.


To be fair this is why Destiny got Destiny 2, and why PoE is getting PoE2.
I hope they use the now ‘complete’ main dev phase of PoE2 experience and staff to pull code blocks from PoE2 into PoE1 to improve it.
(ALL typos lack of caps, punctuation and general errors are copyright Timbo Industries - Laziness Division)
They can't even get basic skills like leap slam to work properly. It's more broke now than ever. Good luck with the other stuff
Still waiting on Left Click + Shift Cyclone and Voltaxic Burst after-death mechanics to be fixed.
So now that we have PoE2, GGG needs to revert the nerfs to 'slow down' PoE1.

Never forget the great Alt Qual Gem deletion, the Ex > Div swap and loss of various crafting methods. Bring back Fire Nova Mine!

Enjoy Path of Nerfs Dos!!
You should post this in the bug report forum, I feel like that would be much more helpful. Along with using /bug
Buying Tattoos (Settlers) #3654153 ★ How To Itemize Beasts? #3559583 Unlock Sandwraith Map Device Kill Tracker #3461595 ★ Deli Music Off #3450767
Bestiary UI/Trading #3380585 ★ Upgrade Tabs to Quads Option #3452458
VISAGE GUILD RECRUITMENT - #3694978 ★ Forum Threads ★
"
KingExodusGG wrote:
You should post this in the bug report forum, I feel like that would be much more helpful. Along with using /bug
This topic is not about fixing specific individual bugs. Its about GGG priorities. Focus more on bug fixing over other things. Fixing known bugs should be considered as something valuable. Quality matters. Things should work properly and not "randomly" miswork.
Consequently this belongs in 'Feedback and Suggestions'. And specific bugs mentioned in this thread are just examples/proof of persisting bugginess of game for the "disbelievers".

And this suggestion to instead post bugs in the bug forum is kind of in opposition to this thread. All the bugs mentioned in this thread are "well known" to players - have been posted on reddit/etc. GGG shouldnt demand from players to post well known bugs in the bug forum. If those bugs really are not known to the relevant people in GGG then GGG should improve the communication inside GGG so that GGG employees knowing those bugs report them properly to their collegues.
No wonder it's lost, it's in the middle of the jungle!
Please upload some photos and provide a better description because it's impossible to understand anything from your explanation. It seems more like personal issues rather than actual errors.

And just a tip: don't report bugs on Reddit, as this platform isn't meant for that.
🌞 Designer of SimpleFilter see My Item Filters 🌞
🌞 I treat PoE as an art 🌞
"
Please upload some photos and provide a better description because it's impossible to understand anything from your explanation.
Its very simple to understand: I want GGG to focus more on bug fixing. This doesnt require photos.

"
It seems more like personal issues rather than actual errors.
https://www.pathofexile.com/forum/view-thread/3526332/page/1#p25340730 See here for example of well known longstanding bug that gets maybe 1 reddit post per 2 months. But this is just proof of bugginess of game - the focus of this thread is not about fixing this particular bug.

"
And just a tip: don't report bugs on Reddit, as this platform isn't meant for that.
Im not reporting bugs on Reddit. And this thread is not for reporting bugs.
No wonder it's lost, it's in the middle of the jungle!
In addition to the above: I just tried adding to an old bug report by me as I encountered the bug again and nociced that the thread was locked with "This thread has been automatically archived. Replies are disabled.".

=> Dont lock bug report threads without fixing the bugs.
No wonder it's lost, it's in the middle of the jungle!
The (Necro) Settler bugs are still in the game. Like:
Game freeze/crash when using moveskill in Kingsmarch, happens frequently. THIS WAS NOT FIXED. Probably reason is that moveskill causes more birds to fly at the same time. There is obviously a general code fail that it cant handle gfx overload. This is evident in other situations too. The counter algorithm/s which exist may make it worse than better also.

Also not fixed is "at sea" when its in harbour.

Etc.

Also the display of the wrong Atlas skill tree is still in and fairly easy to reproduce. Same Harvest bug. Etc.

Even one person dedicated to bug fixing could make a major change. Do away with the arbitrary rescheduling of employees that leads to everybody being a jack-of-the-trades and no one being an expert at something. Certain things like game balance or bug fixing require dedicated people with expertise. Create them instead of preventing their creation.
No wonder it's lost, it's in the middle of the jungle!

Report Forum Post

Report Account:

Report Type

Additional Info