They knew about this 4 days ago!
People have been posting for days about it, so yea i’d say that’s a fair estimation.
In a word, possibly.
Go take a look at 10000 Where’s Waldo pictures. Tell me how many times you find him right off the bat. Statistically, it is going to happen. Same with fixing code. Sometimes it takes forever to find and stabilize. You fix it but break that and so forth. Sometimes it takes a quick glance and a few keystrokes.
6 Likes
Did you just compare WoW to Where’s Waldo…
I’m done lol
Jeez…
A man can show you he can walk on water, but you guys will whine that he doesn’t know how to swim.
5 Likes
No… Mastadon is simply saying that software development and fixing/finding bugs is like playing Where’s Waldo. As a software developer myself, I agree with that sentiment. Even though I developed the application, sometimes I just don’t know where the bug is in the code.
On the other hand, it’s sometimes not as simple as changing a single line of code. The function for one thing can be spread out between multiple files.
4 Likes
If you go AFK then you will be kicked without getting Deserter
I did. Would you like a different analogy. Pick 10,000 haystacks and find the black needle.
Statistically there is a probability of finding the needle quickly on at least a haystack. The analogy is irreverent. The message was sound.
Lets say, for example that I found a solution to bug A. I tested the solution, and indeed bug A is fixed. Yay me go team. By team I mean me. But then bug B develops, directly related to the fix from Bug A. Now I need to chase this chain down…next thing you know we are at bug XXXIV.
Now, lets go back to bug A, before anything was done. My counterpart down the corridor happens to be stopping by the office to talk about something. Probably Brenda in accounting. It is always Brenda in accounting. They take a look at my screen and everything absolutely clicks. They tell me to change a simple command buried in the middle of the code, that two things were inverted. BAM fixed. Push it and it works. Nothing else is broken.
I assure you, having many friends in the video game programming industry and talking to them regularly, this is a very realistic scenario. Except the Brenda part. I just wanted to have some fun with that.
5 Likes
Could you at least add something like this to the breaking news section and possibly alleviate some peoples frustration with a loss of time.
It may not be seen by everyone, but it will be seen by more than those who come here after they find out about the bug. Like the little boy throwing starfish back in the water after the tide goes out, he wont be able to save them all but it mattered to at least that one.
1 Like
Make 20 fake characters and fill the broken instance with those so it stops affecting us. It doesn’t fix the underlying issue but it makes it less impactful.
How long they’ve known about it doesn’t mean too much.
It can take a short amount of time, it can take a long amount of time, for anything related to coding.
Why?
Well let’s look at some questions that can be asked.
Well, what is the glitch specifically?
What triggers the glitch and can we reproduce it? Is it only in certain setups (such as it only happens if you have three vowels in the name)?
Once you identify stuff like that, you can move onto looking into the code which can bring its own set of questions.
Ok, did we make a typo?
Or is it from broken/missing code or something along those lines?
Ok, we corrected that! But did we break something else in the process? Such as things that were connected to the bugged code.
5 Likes
it’s understandable they haven’t found a fix, but preventing player frustration can be done fairly quick, removing deserter debuff, for example from effecting any player
Anecdotal only, but the last three times the group went slowly (or normal speed) and let the glaives be built BEFORE the beach was taken, the last boss worked correctly.
2 Likes
If you have feedback or suggestions about this, you need to post in Dungeons, Raids and Scenarios.
The Devs don’t take feedback or suggestions from the Customer Support forum and the SFAs are not liaisons with them.
2 Likes
Vrak, given that this issue is interfering with our ability to run this Warfront, and it has a time-gated availability, are there any plans to extend the timer to account for this? Or is the Alliance just out the time? I’d really like to get that 385 item on a couple of characters, and this is wrecking the process.
It’s unlikely. The events are normally hard-coded and it’s an on-going event. If you don’t get it this time, there is always next.
1 Like
I couldn’t say, Shareel, but I don’t believe something like that is easily manipulated. Much like the deserter debuff, it is built into the system so can’t be adjusted on the fly.
5 Likes
It seems the main reason for this bug is players skipping parts of the war front I have been reading a lot of these posts and so far if you don’t skip anything do it the way it is to work shouldn’t be a problem.
2 Likes
That does seem to be the case, yes. And in the last attempt, people were urging others to do just that, but stopping people from zerging is difficult at best. Those of us that were desperately trying to complete the other objectives before the vanguard finished taking the beach barely managed to get it done.
That said, if there is a desire to force people to complete the other objectives, then do that. I understand that this is (apparently) a bug, rather than a feature, so it was an unintentional goad to players to complete the rest of the Warfront activities. But this is a real pain to those of us that do not want to waste our time, and are at the mercy of the rest of the group, who refuse to listen.
2 Likes
Taken from a thread in General Discussion.
May be a quick way to resolve what creates the problem, and tomorrow’s resets will take care of any existing instances that are back filling and not concluding.
Also you might could quadruple the HP of those two robots, and when a glaive is built, have it reset that cranked up HP to normal.
2 Likes