Feanor wrote: »

ArchMikem wrote: »

"Forums, are you ever going to stop complaining?"

They're both moot questions, aren't they.

Asking for bugs to be fixed is forbidden now too?

@Feanor when zos doesnt want to fix the ones that actually matter that break the game for everybody yea pretty much. exploits can wait a bit. but they havent even fixed a few bugs that have been issues for years so just dont hold your breath. pvp still being one of the main bug hubs.

I think it’s just mass laziness and bad management. It really does happen as I described in another post in industry like this. I’m making assumptions here. But we all are in this thread.

So they have a change control process. Probably. Probably an internal ticketing system. Issues are brought up there is someone or a team prioritizes and assigns issues out to teams or individuals.

Sometimes it’s a simple variable change on an item. Like the ownership property on some containers in cyrodel. So they assign that to the junior level design guy or gal. Low hanging fruit. Just change the ownership property on the container and test it. Easy right?

They probably have internal test server they can run on their own workstations to test benign changes like this. Like it pulls data from test environment but the server instance runs on their workstation. Totally possible since they’re the only one connecting via localhost on the workstation. Test their changes.

Then when the test is fine they comit their changes to the global internal test sever. This is the server the QA team uses. This is before the changes are committed to the PTS. This is still on internal test server.

So back to junior design guy. Junior design guy has a time sheet. He has to put his time on the ticket for all time spent changing the ownership variable on the container. As well as testing it.

Well, that takes 15 minutes to change and 15 minutes to test. Right? So ... the design guy figures that he can’t possibly screw up a simple variable change. Low hanging fruit. So he writes in his time sheet that he fixed the issue AND tested it. But the reality is he never tested it. Why should he since it was such a benign change that most definite works.

So now we lie on time sheet and get 15 extra minutes to browse Facebook on phone or screw around at the water cooler or whatever.

Now changes are committed to internal test environment and he updated his ticket indicating he tested. And ticket is escalated to internal QA team.

Now the QA team does the same thing. They see benign change and don’t specifically test it on their internal server. Who cares? How can you possibly screw it up?

Now the QA team gets an extra hour or so to lie about in their time sheet. All the testing they said they did that they didn’t really do. So you can have that third beer at lunch and hide the fact you took a 1.5 hour long lunch in your time sheet. Because you said you tested the item container ownership change that was made but you didn’t really test it.

Fast forward to today and we have someone post that they can’t loot some containers in Cyro anymore. Certain containers. They wrote in patch notes they changed ownership variable so items in those containers are no longer considered stolen.

But due to laziness and BS at every level, the reality is that they didn’t do it right. And actually made the containers unlootable completely.

Then someone goes to forums and complains. Then Gina asks around. I bet her job is constantly asking these lazy devs and testers what is going on and I bet her job is to hold them accountable. So they lie to her too.

Then we get a response from her in forums. It basically says that we mismarked the container and will fix it in the future patch.

Now the original persons that screwed this up has fire lit under them. They quickly fix it. Takes minutes. Originally, they clicked a checkbox wrong due to phone going off at that moment because of new cat meme on Facebook or perhaps a fight with significant other. Not this time. Because fire is lit under them, it actually works this time. That change is committed to internal test server and actually tested fine this time.

No one got in trouble. No one is disciplined. No one that screwed up such simple low hanging fruit gets a sit down talk to by the management.

Now imagine this happens every day with every bug or change control ticket.. That’s why you have the game you have.

All assumptions and speculation. But that’s what we are doing in this thread.

DMuehlhausen wrote: »

@ZOS_GinaBruno You should just in response to this release a Patch Notes post with every fix, bug, upgrade, change etc since launch day.

Or just a list of all the bugs outstanding and their status.

There is always the RTO issue. ESO may now just be considered a Legacy system.
Minimal support and minimal ongoing investment.

As players, we should all consider future software investments, from our own perspectives.
We should all assess which suppliers represent value-for-money; and those suppliers that are client-focused.

The problem is that large corporations don't consider end users as customers. We're more resource nodes to be harvested.
Shareholders are the customers that matter.


None of us have to be here. Right?