@ZOS_GinaBruno The next patch?!? Didn't your already apply this fix to the PC? Why not apply this to the consoles the same way?
ESOFanBoyz wrote: »@ZOS_GinaBruno The next patch?!? Didn't your already apply this fix to the PC? Why not apply this to the consoles the same way?
Probably because patching on consoles works very differently. ZOS can patch PC whenever they feel like it. With consoles they need to wait for Sony/Microsoft to approve the update and that takes quite a bit of time from what I have heard.
ESOFanBoyz wrote: »@ZOS_GinaBruno The next patch?!? Didn't your already apply this fix to the PC? Why not apply this to the consoles the same way?
Probably because patching on consoles works very differently. ZOS can patch PC whenever they feel like it. With consoles they need to wait for Sony/Microsoft to approve the update and that takes quite a bit of time from what I have heard.
Seemed like they didn't need much time to fix the crafting survey dupe glitch with the banker.
ESOFanBoyz wrote: »@ZOS_GinaBruno The next patch?!? Didn't your already apply this fix to the PC? Why not apply this to the consoles the same way?
Probably because patching on consoles works very differently. ZOS can patch PC whenever they feel like it. With consoles they need to wait for Sony/Microsoft to approve the update and that takes quite a bit of time from what I have heard.
Seemed like they didn't need much time to fix the crafting survey dupe glitch with the banker.
That was likely doable with a server hotfix, anything the requires an actual patch is bound to the whims of Certification...
1. They have to fix the issue
2. A patch has more than one fix/feature
3. They have to test it out
4. The internal cert QA oes through it amd makes sure everything looks good and will pass
5. They have to book a slot to have the game go though cert
6. If they miss that slot because of issues they have to book a new one
7. MS/Sony cert go though the patch and run their checklist
8. If it fails the checklist for mostly dumb *** (Sony logo isnt 100% exact) they have to start over
9. If it passes a release date is set
10. On release date the patch is released
Thats how console cert works, PC doesnt have that so it could be fixed right away, consoles work differently.
ESOFanBoyz wrote: »@ZOS_GinaBruno The next patch?!? Didn't your already apply this fix to the PC? Why not apply this to the consoles the same way?
Probably because patching on consoles works very differently. ZOS can patch PC whenever they feel like it. With consoles they need to wait for Sony/Microsoft to approve the update and that takes quite a bit of time from what I have heard.
Seemed like they didn't need much time to fix the crafting survey dupe glitch with the banker.
That was likely doable with a server hotfix, anything the requires an actual patch is bound to the whims of Certification...
1. They have to fix the issue
2. A patch has more than one fix/feature
3. They have to test it out
4. The internal cert QA oes through it amd makes sure everything looks good and will pass
5. They have to book a slot to have the game go though cert
6. If they miss that slot because of issues they have to book a new one
7. MS/Sony cert go though the patch and run their checklist
8. If it fails the checklist for mostly dumb *** (Sony logo isnt 100% exact) they have to start over
9. If it passes a release date is set
10. On release date the patch is released
Thats how console cert works, PC doesnt have that so it could be fixed right away, consoles work differently.
Or test the *** they changed for this patch before letting it go live
ESOFanBoyz wrote: »@ZOS_GinaBruno The next patch?!? Didn't your already apply this fix to the PC? Why not apply this to the consoles the same way?
Probably because patching on consoles works very differently. ZOS can patch PC whenever they feel like it. With consoles they need to wait for Sony/Microsoft to approve the update and that takes quite a bit of time from what I have heard.
Seemed like they didn't need much time to fix the crafting survey dupe glitch with the banker.
That was likely doable with a server hotfix, anything the requires an actual patch is bound to the whims of Certification...
1. They have to fix the issue
2. A patch has more than one fix/feature
3. They have to test it out
4. The internal cert QA oes through it amd makes sure everything looks good and will pass
5. They have to book a slot to have the game go though cert
6. If they miss that slot because of issues they have to book a new one
7. MS/Sony cert go though the patch and run their checklist
8. If it fails the checklist for mostly dumb *** (Sony logo isnt 100% exact) they have to start over
9. If it passes a release date is set
10. On release date the patch is released
Thats how console cert works, PC doesnt have that so it could be fixed right away, consoles work differently.
Or test the *** they changed for this patch before letting it go live
Its tested, its tested extensively.But there are limits as to what a test team can do and what a billion people playing the game will find.
FYI, games break, no game is bug free, especially not MMOs. Stop bitching that games arent perfect because you want the impossible. Ive seen people like you cry that devs should die in a fire because a bug happened... Its absolutely not helping.
You're not entitled to the impossible because you paid something.
ZOS_GinaBruno wrote: »We're currently planning to have this fixed in the next console incremental patch.
The_Outsider wrote: »On PC Minor Slayer has been changed to effect all dungeon and trial mobs. Has that change even taken effect on console yet?
I'm not as much concerned about minor slayer fix as it affects all guilds and players across the board, but when is the VMOL disconnecting and crashing going to be fixed? 3+ guilds on Xbox1 spent weeks/months getting this trial perfected and a couple were finishing under an hour with lots of vitality. Now not even 1 guild has completed it since the patch and we can't get the gold jewelry we were excited for. Any time frame for that?
Which is when?ZOS_GinaBruno wrote: »We're currently planning to have this fixed in the next console incremental patch.