Arsenic_Touch wrote: »They're "investigating"
Arsenic_Touch wrote: »They're "investigating"
It takes 2 mins to investigate : Go to crafting station, craft 3 parts, try it...
How much does it take to fix it???
Arsenic_Touch wrote: »They're "investigating"
It takes 2 mins to investigate : Go to crafting station, craft 3 parts, try it...
How much does it take to fix it???
andre.roques.3b14_ESO wrote: »Your issue is likely not the highest priority...i.e. not as many people have reported it as an issue compared to issue x. After that, then there is the priority in regards to problems that were reported equality to yours... anyway. The idea that a fix on a game system as extensive as ESO or any MMO can happen within anything shorter than one development cycle/sprint just isn't realistic. I believe the only time that they will try something faster is if something is phenomenally game breaking. Even then, hot fixes are more likely to cause other issues and are high risk endeavors, at best.
Basically, I am suggesting that it may not be so cut and dry and easy to fix as you're suggesting.
andre.roques.3b14_ESO wrote: »Your issue is likely not the highest priority...i.e. not as many people have reported it as an issue compared to issue x. After that, then there is the priority in regards to problems that were reported equality to yours... anyway. The idea that a fix on a game system as extensive as ESO or any MMO can happen within anything shorter than one development cycle/sprint just isn't realistic. I believe the only time that they will try something faster is if something is phenomenally game breaking. Even then, hot fixes are more likely to cause other issues and are high risk endeavors, at best.
Basically, I am suggesting that it may not be so cut and dry and easy to fix as you're suggesting.
You ever played Diablo 3? Hotfixes there were super fast and often... anyway, maybe if they fix this set they will brake other 2 so...
Me and all my friends reported this 20 minutes after the update was out and i can only imagine how many more reported this thing... These (and many others) are bugs that should be fixed and applied in hotfixes DAILY... Are we supposed to wait for update nr3 to have this fixed?? You guys are so unprofessional...
Kewljag_66_ESO wrote: »Me and all my friends reported this 20 minutes after the update was out and i can only imagine how many more reported this thing... These (and many others) are bugs that should be fixed and applied in hotfixes DAILY... Are we supposed to wait for update nr3 to have this fixed?? You guys are so unprofessional...
This is my speculation on this. I dont think that 220% sneak speed was ever intended. I think it was suppose to be 22% but someone did a typo and the programmer didnt know. 220% is a very odd number and very excessive. just 100% would double your sneak speed. 220% would make you move in sneak faster than you could sprint. this has to be unintended or everyone would travel this way. remember this was not in the PTS patch notes so it didnt get tested, i think they finally saw it when it was about to go live and all they could do was bug it / break it /turn it off until they figured out what to re program it to. i am posative when it works it will not be 220%
Kewljag_66_ESO wrote: »Me and all my friends reported this 20 minutes after the update was out and i can only imagine how many more reported this thing... These (and many others) are bugs that should be fixed and applied in hotfixes DAILY... Are we supposed to wait for update nr3 to have this fixed?? You guys are so unprofessional...
This is my speculation on this. I dont think that 220% sneak speed was ever intended. I think it was suppose to be 22% but someone did a typo and the programmer didnt know. 220% is a very odd number and very excessive. just 100% would double your sneak speed. 220% would make you move in sneak faster than you could sprint. this has to be unintended or everyone would travel this way. remember this was not in the PTS patch notes so it didnt get tested, i think they finally saw it when it was about to go live and all they could do was bug it / break it /turn it off until they figured out what to re program it to. i am posative when it works it will not be 220%
OK, so then how long does it take to remove one 0 from set description??????????????????????????
andre.roques.3b14_ESO wrote: »Your issue is likely not the highest priority...i.e. not as many people have reported it as an issue compared to issue x. After that, then there is the priority in regards to problems that were reported equality to yours... anyway. The idea that a fix on a game system as extensive as ESO or any MMO can happen within anything shorter than one development cycle/sprint just isn't realistic. I believe the only time that they will try something faster is if something is phenomenally game breaking. Even then, hot fixes are more likely to cause other issues and are high risk endeavors, at best.
Basically, I am suggesting that it may not be so cut and dry and easy to fix as you're suggesting.
You ever played Diablo 3? Hotfixes there were super fast and often... anyway, maybe if they fix this set they will brake other 2 so...
nerevarine1138 wrote: »andre.roques.3b14_ESO wrote: »Your issue is likely not the highest priority...i.e. not as many people have reported it as an issue compared to issue x. After that, then there is the priority in regards to problems that were reported equality to yours... anyway. The idea that a fix on a game system as extensive as ESO or any MMO can happen within anything shorter than one development cycle/sprint just isn't realistic. I believe the only time that they will try something faster is if something is phenomenally game breaking. Even then, hot fixes are more likely to cause other issues and are high risk endeavors, at best.
Basically, I am suggesting that it may not be so cut and dry and easy to fix as you're suggesting.
You ever played Diablo 3? Hotfixes there were super fast and often... anyway, maybe if they fix this set they will brake other 2 so...
You honestly think that the coding for Diablo 3 is anywhere near as complex as the coding for this?
Oh, and fixes didn't come in fast enough for the D3 crowd either. Because apparently gamers today are all spoiled children who think that games magically release without bugs and that when there is a bug (which totally doesn't happen in a good game, of course), it can be fixed with a band-aid and dreams.
GothicPython wrote: »Kewljag_66_ESO wrote: »Me and all my friends reported this 20 minutes after the update was out and i can only imagine how many more reported this thing... These (and many others) are bugs that should be fixed and applied in hotfixes DAILY... Are we supposed to wait for update nr3 to have this fixed?? You guys are so unprofessional...
This is my speculation on this. I dont think that 220% sneak speed was ever intended. I think it was suppose to be 22% but someone did a typo and the programmer didnt know. 220% is a very odd number and very excessive. just 100% would double your sneak speed. 220% would make you move in sneak faster than you could sprint. this has to be unintended or everyone would travel this way. remember this was not in the PTS patch notes so it didnt get tested, i think they finally saw it when it was about to go live and all they could do was bug it / break it /turn it off until they figured out what to re program it to. i am posative when it works it will not be 220%
OK, so then how long does it take to remove one 0 from set description??????????????????????????
It's not just removing the 0, it's actually completely fixing the bonus w/e it's actually supposed to be, because right now you get no speed increase at all.
Me and all my friends reported this 20 minutes after the update was out and i can only imagine how many more reported this thing... These (and many others) are bugs that should be fixed and applied in hotfixes DAILY... Are we supposed to wait for update nr3 to have this fixed?? You guys are so unprofessional...
Kewljag_66_ESO wrote: »Me and all my friends reported this 20 minutes after the update was out and i can only imagine how many more reported this thing... These (and many others) are bugs that should be fixed and applied in hotfixes DAILY... Are we supposed to wait for update nr3 to have this fixed?? You guys are so unprofessional...
This is my speculation on this. I dont think that 220% sneak speed was ever intended. I think it was suppose to be 22% but someone did a typo and the programmer didnt know. 220% is a very odd number and very excessive. just 100% would double your sneak speed. 220% would make you move in sneak faster than you could sprint. this has to be unintended or everyone would travel this way. remember this was not in the PTS patch notes so it didnt get tested, i think they finally saw it when it was about to go live and all they could do was bug it / break it /turn it off until they figured out what to re program it to. i am posative when it works it will not be 220%
OK, so then how long does it take to remove one 0 from set description??????????????????????????
I work in construction, i painted a whole house today on my own under 35°...
Me and all my friends reported this 20 minutes after the update was out and i can only imagine how many more reported this thing... These (and many others) are bugs that should be fixed and applied in hotfixes DAILY... Are we supposed to wait for update nr3 to have this fixed?? You guys are so unprofessional...
This game has complex coding????? Bahahahahahaha
This game has complex coding????? Bahahahahahaha
Nah ESO has simple coding..I can only lolz at you..
Just for your comparison Diablo 3 + WoW, don't even come close to how complex coding ESO has. This phasing system is incredibly complex and something none Blizzard game is doing much.
They can have all the budget in the world, but diablo 3 released as the most broken hack & slash game ever (to be honest it was a horrible game anyway).
Also Torchlight 2 was just a much better game in every aspect.
This game has complex coding????? Bahahahahahaha
Nah ESO has simple coding..I can only lolz at you..
Just for your comparison Diablo 3 + WoW, don't even come close to how complex coding ESO has. This phasing system is incredibly complex and something none Blizzard game is doing much.
They can have all the budget in the world, but diablo 3 released as the most broken hack & slash game ever (to be honest it was a horrible game anyway).
Also Torchlight 2 was just a much better game in every aspect.
Don't know what version of Diablo 3 you played but in my 2000+ hours i've never found a game breaking/progress bug, never...
ZOS_GinaBruno wrote: »Hey everyone. We currently have this slated to be fixed when Update 3 goes live. To be clear, the issue with this set is not just a tooltip error, but also the application of the bonus itself. There are many factors that go into fixing an issue, including coding and localization. That said, the correct percentage for the stealth bonus is 60%, and not 220%.
not a few clicks, but with the change of one variableIf there exists other set bonuses with the same stat that work, then the fix should take a few mouse clicks.
did you outsource coding to india and they did outsource it to vietnam, or why does it take so long and needs !localization! ???There are many factors that go into fixing an issue, including coding and localization.
ZOS_GinaBruno wrote: »Hey everyone. We currently have this slated to be fixed when Update 3 goes live. To be clear, the issue with this set is not just a tooltip error, but also the application of the bonus itself. There are many factors that go into fixing an issue, including coding and localization. That said, the correct percentage for the stealth bonus is 60%, and not 220%.
ZOS_GinaBruno wrote: »Hey everyone. We currently have this slated to be fixed when Update 3 goes live. To be clear, the issue with this set is not just a tooltip error, but also the application of the bonus itself. There are many factors that go into fixing an issue, including coding and localization. That said, the correct percentage for the stealth bonus is 60%, and not 220%.