Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Dread Fortress SM Reaches, Hands, Brontes are broke.

STAR WARS: The Old Republic > English > General Discussion > Bug Reports
Dread Fortress SM Reaches, Hands, Brontes are broke.
First BioWare Post First BioWare Post

Nepthen's Avatar


Nepthen
02.18.2016 , 01:04 PM | #201
Not sure I buy this... if the intent was truly to have them in no later than 4.3 but hopefully 4.2, then the original post would have said so or at least a clarification response would have been out much sooner than this.

It is what it is... and it's still a month at best for a fix. I'm afraid at this point, the damage has already been done. I know it hit my raid team really hard.
Nepthen Kesslyte
Old Republic Dads
Host - Old Republic Radio
The Shadowlands

Warrgames's Avatar


Warrgames
02.18.2016 , 01:29 PM | #202
Quote: Originally Posted by EricMusco View Post
Hey folks,

I want to add some clarification to my original post. I mentioned that we are targeting Game Update 4.3 to have these fixed. The reason I stated 4.3 is that this would give us a buffer of time to make, test, and implement the changes.

However, I do want to note that we are actually quite hopeful that we can make these changes for 4.2. In this instance I wanted to play it safe as I would rather tell you it is fixed sooner than you expected, than say 4.2 and push it out. I will continue to provide you updates as I have them. I just wanted to alleviate some of your concerns. We are working to get this fixed as soon as possible!

-eric
No matter what you say; a bus is in your future.
"I don't like Tatooine, but I do like saying Tatooine." Theron Shan
Referral link: http://www.swtor.com/r/fSvsyK Click for free stuff.
"Nonsense repeated doesn't make it truth." Arcaan

GrandLordMenace's Avatar


GrandLordMenace
02.18.2016 , 01:37 PM | #203
Quote: Originally Posted by Nepthen View Post
Not sure I buy this... if the intent was truly to have them in no later than 4.3 but hopefully 4.2, then the original post would have said so or at least a clarification response would have been out much sooner than this.

It is what it is... and it's still a month at best for a fix. I'm afraid at this point, the damage has already been done. I know it hit my raid team really hard.
Agreed, it needs to be fixed next tuesday, unless it results in like a bug of equal caliber, it needs to be fixed.
Rydarus Veneris the Revanchist, Beater #fedaracarrychist
Vigilance Guardian guide on Dulfy! Like my guide? Support my Referral Link!
Last Guardian DPS because dead game

Rankyn's Avatar


Rankyn
02.18.2016 , 01:50 PM | #204
Quote: Originally Posted by EricMusco View Post
this would give us a buffer of time to make, test, and implement the changes.
Why start now?
Keep up to date with game events at
SWTORCalendar.com

commanderwar's Avatar


commanderwar
02.18.2016 , 01:54 PM | #205
Quote: Originally Posted by EricMusco View Post
Hey folks,

I want to add some clarification to my original post. I mentioned that we are targeting Game Update 4.3 to have these fixed. The reason I stated 4.3 is that this would give us a buffer of time to make, test, and implement the changes.

However, I do want to note that we are actually quite hopeful that we can make these changes for 4.2. In this instance I wanted to play it safe as I would rather tell you it is fixed sooner than you expected, than say 4.2 and push it out. I will continue to provide you updates as I have them. I just wanted to alleviate some of your concerns. We are working to get this fixed as soon as possible!

-eric
I fine with that, better than april

BenKatarn's Avatar


BenKatarn
02.18.2016 , 02:03 PM | #206
Quote: Originally Posted by EricMusco View Post
Hey folks,

I want to add some clarification to my original post. I mentioned that we are targeting Game Update 4.3 to have these fixed. The reason I stated 4.3 is that this would give us a buffer of time to make, test, and implement the changes.

However, I do want to note that we are actually quite hopeful that we can make these changes for 4.2. In this instance I wanted to play it safe as I would rather tell you it is fixed sooner than you expected, than say 4.2 and push it out. I will continue to provide you updates as I have them. I just wanted to alleviate some of your concerns. We are working to get this fixed as soon as possible!

-eric
Quite frankly Eric, making people mad by telling them "we plan to have raids fixed two months from now" is a really bad way to go at it. This is a major issue for a lot of people.
- = = The Atrias Legacy = = -

FlavivsAetivs's Avatar


FlavivsAetivs
02.18.2016 , 02:14 PM | #207
Quote: Originally Posted by EricMusco View Post
Hey folks,

I want to add some clarification to my original post. I mentioned that we are targeting Game Update 4.3 to have these fixed. The reason I stated 4.3 is that this would give us a buffer of time to make, test, and implement the changes.

However, I do want to note that we are actually quite hopeful that we can make these changes for 4.2. In this instance I wanted to play it safe as I would rather tell you it is fixed sooner than you expected, than say 4.2 and push it out. I will continue to provide you updates as I have them. I just wanted to alleviate some of your concerns. We are working to get this fixed as soon as possible!

-eric
Hello Eric,

No matter what you say, you're gonna get flak from the community. But I honestly believe it would have been better in this case to say "we will try and fix it in 4.2, but may be unable to until 4.3".

I think the problem is that your staff often gives definitive statements which they can't always live up to. Giving and clearly stating that an "estimated time [or range of time] when this can be fixed" might be better. Giving "At best, in x days, at worst in 4.x and we will give a more precise estimate as we work on the problem", just for example, would probably be a much better way to communicate.

I know from experience as a Rome: Total War modder that giving a definitive date and not living up to it can lead to lots of disappointment.

That being said, I think that maybe you should work hard to push for a fix sooner than 4.2, because that may be what it takes to keep some of these ops communities.

I don't usually address the Devs directly, I can be very critical, but I mean this in the best interest.

~ Eudoxia
A.K.A. Magister Militum Flavius Aetius
Eudoxia Eudoxya
<Aeterna Vigilantia>
Jedi Covenant

gabigool's Avatar


gabigool
02.18.2016 , 02:17 PM | #208
Quote: Originally Posted by EricMusco View Post
Hey folks,

I want to add some clarification to my original post. I mentioned that we are targeting Game Update 4.3 to have these fixed. The reason I stated 4.3 is that this would give us a buffer of time to make, test, and implement the changes.

However, I do want to note that we are actually quite hopeful that we can make these changes for 4.2. In this instance I wanted to play it safe as I would rather tell you it is fixed sooner than you expected, than say 4.2 and push it out.
I assume what this REALLY means is you're actually quite hopeful that you can make these changes in a hotfix sometime in the next few days. In this instance you wanted to play it safe as you would rather tell us it is fixed sooner than you expected, than say hotfix and lump it into some future update.

Quote: Originally Posted by EricMusco View Post
I just wanted to alleviate some of your concerns.
It does not.

Quote: Originally Posted by EricMusco View Post
We are working to get this fixed as soon as possible!
This could have been fixed in less time than it took to be acknowledged.

This is a hotfix caliber issue. Do not mistake it as otherwise.

Don't get me wrong, I'm glad you guys are at least aware of the fact that the community considers this important. But this retraction does not fix the issue of you treating this with the same degree of weight of say a cartel market toy. These are fundamental core gameplay mechanics that are horribly broken and affect numerous people.

Hotfix.

Dreamsky's Avatar


Dreamsky
02.18.2016 , 02:19 PM | #209
No offense to the QA team, but your QA are donkey *****. At least your QA process is donkey *****. Don't you have like a list of things to check out in your close testing? If not here's a sample one:

1. Test the things that was changed
2. Test all related NPC vendors
3. Do a run in the most popular flashpoints, with no death god mode, and check completion time against records
4. Do a run in the most popular operations, in god mode and check completion time and note anything odd.
5. Do 2 hours of PVP.
6. Do 2 hours of Starfighter.
7. Check cartel item drop rate.

Make sure you do the first 5 every time and you'll have much less complaints.

FlavivsAetivs's Avatar


FlavivsAetivs
02.18.2016 , 02:26 PM | #210
Quote: Originally Posted by Dreamsky View Post
6. Do 2 hours of Starfighter.
Don't even need to, we have a long list of bugs that have been there for up to 2 years buried somewhere in the GSF forums. They've never fixed a single GSF bug.

None of them are game-breaking as far as I can tell, just a nuisance.

~ Eudoxia
A.K.A. Magister Militum Flavius Aetius
Eudoxia Eudoxya
<Aeterna Vigilantia>
Jedi Covenant