Wrong development method - simple bug shows how bad it's. Feedback about bug fixing and developlent that will lead to worse experience

There’s one single bug that shows how bad organization and development is.
obraz-2024-10-05-102638186 hosted at ImgBB — ImgBB ← this simple bug that is very easy to fix is a bigger deal. It’s one issue that occurs from start of the season 1.5, One issue that was not fixed and shows how developers ignore minor bugs. For now it’s minor not much affecting bug - but lets move to 2 years later… if this development of ignoring minor bugs will not change we will have 50?100? 1200? little bugs that will occurs everywhere.

Last Epoch team - please care about minor simple bugs or those bugs will change into swarm.

it gives very bad experience seeing game with bug that is pretty simple to fix and occurrs after weeks. Not even talking… clicking this box makes game freeze, probably affecting your services and net-code stability.

You got so many things wrong.

  1. You’re reporting a bug, but posting it as a suggestion.
    Go to Bug Report section. Even better, go in-game, send them a “crash” report with screenshot and tell them clicking the box freezes the game. That is IF it actually freezes the game…

  2. There is no “season 1.5”.

  3. What are you even showing on the screenshot?
    You said clicking it freezes the game, but in the same post you said this bug doesn’t affect much and exists for 2 years, so which is it?!
    You didn’t describe the problem. Are we supposed to magically figure out what you’re thinking?

  4. There is this thing called prioritization. If you have a minor bug that doesn’t affect much (your own words), then it’s okay to not fix it for 2 years, because there are more important bugs to fix first.
    Y’know, stuff like crashes, and multiplayer issues, and online play disconnects, and skill bugs, and so on…

  5. You are assuming how a game studio develops a game based on what seems to be a minor graphical glitch that doesn’t affect the gameplay - a very common occurence in ALL games - and drawing conclusions about future development from this assumption.
    That’s delusional behavior. Don’t be a clown. :clown_face:

2 Likes

To fix it: a inherent situation coming from most modern engines, which Unity is one… and Unity is known to have some issues the devs defintiely will be 100% unable to ‘fix’ unless they make their own external modules to interact with those aspects.

So yes, that post is laughable beyond end. :rofl:

4 Likes

Not to mention that Mike has already said they’re already upgrading the Unity engine to the latest version. So many of these might be fixed (and I expect that many more will appear as well) when they release it.

Also, to emphasize Psoejd’s point about prioritization:
Pretty much all games have hundreds of bugs, if not thousands. Many of those are relatively simple bugs to fix. However, if you have dozens of bugs that are relatively easy to fix, it will still take a long time to fix them all. So you add priorities and simple bugs that don’t affect gameplay (and, like your example, are in a part of the game you’ll only cross once while leveling and many people won’t even see it) are put down the list and they may stay on the list for years.
In some games, such bugs might not ever be fixed at all because there are always more important bugs to fix and new stuff to add.

2 Likes

Yes, this one is very easy to fix.
They just need to remove the entirely nonsensical forge anvils from towns. They really have no purpose when anyone can simply press F and craft anywhere they like.
Unless they have plans for them in the future.

2 Likes

It’s close enough, given they reset/refreshed season 2 (or 1 if you want to think that 1.0 was cycle 0). In any event, it’s fairly obvious what he meant?

The stash in the same place as the forge Outcast Camp.

The stash being in the same place as the forge was introduced in 1.1 I think? Maybe the refresh, certainly not prior to 1.0. Though he could be talking about excessive lag when accessing your stash.

I thought that had been implemented with the cycle refresh?

No, Mike has said that they’re already using the new version internally, but it won’t be released until next year. Possibly not even with the next cycle. It’s supposed to be a massive change.

You are wrong with all of it and don’t even know how to read i guess.

1:No i don’t reported a bug - it’s known issue that was reported. What i did i provided feedback about bug fixing and developing structure inside studio. That’s was cosntructive feedback without hate or anything.
2: it’s common logic to call it 1.5 as it’s old season refreshed - just think a little,
3-4-5: It’s clear you don’t know nothing about development and how it will affect game later with this structure of bug fixing. Im working on net-code and services - and i know issuess like that are not just graphic (at most cases) - i pointed it - it cause lag when we click it - services are hidden so we don’t know what’s goin on them in backend. It’s possible sum of little bugs later will cause chaos and spread in a way developers don’t have even on mind.

There we have 1 little bug that doesn’t cause any “spike” on server (we don’t know. what if it will? but cause local massive spike on performance - when 1000 players clicks it - what if it cause a 1% services performance drop? and we get 100 or 200 another issuess like that.

Optimisation of code starts on little things by removing potential errors, asserts and leads to clear code.

6: At point 1 you are pointing yourself as a clown and calling others…

You can’t even read properly and think. Try to be better as a person. Calling other people clowns without even realizing what OP writed here will don’t make anything better. No offence ofc but grow up and be more mature.

I prefer to stick to official naming scheme, so Cycle 0, Cycle 1 and Cycle 1.1.7. Adds less confusion that way.

Thank you. I wonder why OP couldn’t spend those 5 seconds properly describing the issue…

So either it’s not been there for 2 years, or he means that stash lags when opened for 2 years?

Can you link the issue?

To be fair - and this is not meant as an insult, but as constructive feedback - your feedback isn’t written very concisely. In that regard, I understand how Psojed came to their line of thoughts regarding your feedback.

You wrote:

Not even talking… clicking this box makes game freeze

This box. Not ‘a storage chest’. This understandably misleads a reader, who uses the difference between ‘this’ and ‘a’ to build context, into linking your statement to the picture you posted.

Lags/Freezes when interacting with the storage chest is a problem in general, not limited to this box. I don’t know what causes it (net code, client, online database), but yes, stuff like this needs to be addressed.

This (referring to your picture) is a minor graphical glitch for all I know. Rather than having my client freeze, I can’t even interact with this box/forge at all. I click it and absolutely nothing happens.

Yeah, Psojed’s behaviour at times leaves even more to be desired than the minion AI.

Yeah, that’ll be him not being a native English speaker. They can use more lireral translations from their native language that either sound a bit odd or are less clear when used in English.