ZOS_JessicaFolsom wrote: »What's the reason, technical or otherwise, that things like the aforementioned housing tours - a piece of content that has no urgency attached to it whatsoever - can be hotfixed, but not this? If the issue has been identified and is ready to be fixed, what caused it?
Pulling out these two questions, which we can answer now.
In simple terms, this particular bug was caused by a guild history permissions refresh issue in the client C++ code, which is why we need to do an incremental. Server code issues can be fixed with hotfixes, and some client issues (UI scripting related, for example) can be fixed via hotfix. But client C++ codes require a full patch and deploy to address.
DenverRalphy wrote: »ZOS_JessicaFolsom wrote: »What's the reason, technical or otherwise, that things like the aforementioned housing tours - a piece of content that has no urgency attached to it whatsoever - can be hotfixed, but not this? If the issue has been identified and is ready to be fixed, what caused it?
Pulling out these two questions, which we can answer now.
In simple terms, this particular bug was caused by a guild history permissions refresh issue in the client C++ code, which is why we need to do an incremental. Server code issues can be fixed with hotfixes, and some client issues (UI scripting related, for example) can be fixed via hotfix. But client C++ codes require a full patch and deploy to address.
I think the actual question is... Why does the patch have to be two weeks down the road? Why not just deploy the patch and force all players to log out and patch? Because that's what seemingly every other MMO out there is able to do when needed.
[edit] Not to mention that it's a bit worrying that it's a client side issue. Because that means that an altered/hacked game client could access data it shouldn't be able to.
Bobby_Digital81 wrote: »DenverRalphy wrote: »ZOS_JessicaFolsom wrote: »What's the reason, technical or otherwise, that things like the aforementioned housing tours - a piece of content that has no urgency attached to it whatsoever - can be hotfixed, but not this? If the issue has been identified and is ready to be fixed, what caused it?
Pulling out these two questions, which we can answer now.
In simple terms, this particular bug was caused by a guild history permissions refresh issue in the client C++ code, which is why we need to do an incremental. Server code issues can be fixed with hotfixes, and some client issues (UI scripting related, for example) can be fixed via hotfix. But client C++ codes require a full patch and deploy to address.
I think the actual question is... Why does the patch have to be two weeks down the road? Why not just deploy the patch and force all players to log out and patch? Because that's what seemingly every other MMO out there is able to do when needed.
[edit] Not to mention that it's a bit worrying that it's a client side issue. Because that means that an altered/hacked game client could access data it shouldn't be able to.
Because on console, Sony and Microsoft need to go through a verification process for the updates/patches for games.
DenverRalphy wrote: »Bobby_Digital81 wrote: »DenverRalphy wrote: »ZOS_JessicaFolsom wrote: »What's the reason, technical or otherwise, that things like the aforementioned housing tours - a piece of content that has no urgency attached to it whatsoever - can be hotfixed, but not this? If the issue has been identified and is ready to be fixed, what caused it?
Pulling out these two questions, which we can answer now.
In simple terms, this particular bug was caused by a guild history permissions refresh issue in the client C++ code, which is why we need to do an incremental. Server code issues can be fixed with hotfixes, and some client issues (UI scripting related, for example) can be fixed via hotfix. But client C++ codes require a full patch and deploy to address.
I think the actual question is... Why does the patch have to be two weeks down the road? Why not just deploy the patch and force all players to log out and patch? Because that's what seemingly every other MMO out there is able to do when needed.
[edit] Not to mention that it's a bit worrying that it's a client side issue. Because that means that an altered/hacked game client could access data it shouldn't be able to.
Because on console, Sony and Microsoft need to go through a verification process for the updates/patches for games.
That applies to normal/major patch updates. Playstation and XBox do have provisions for emergency/urgent patch deployment.
ZOS_JessicaFolsom wrote: »Hi everyone, thank you for raising questions here. We'd like to give a little more context around this issue, what our options are/were, and why we made the decision we did to address it. When we identified that guild trader bid history information was visible to everyone in the guild, regardless of permissions, we immediately jumped on it and looked into what our options are. We determined that this issue is not hotfixable. We also do not currently have the ability to single out and turn off a single element of the guild history log such as guild trader bid history.
Our options to address this issue are/were 1) leave the issue as-is until the next incremental patch on Sept. 15 for PC and Sept. 16 for consoles or 2) temporarily turn off guild history until the fix is live. We were also getting word that guild trader bid information was being circulated among the community, increasing the likelihood that information would be used to cause disruption and harm to trading guilds (such as trade guilds losing out on traders for a week). In weighing our options and considering the impact of both - and with the understanding that both options have some degree of undesirable impact - we chose to go with option 2. Please know we did not make this decision lightly.
We did make an additional adjustment this morning to account for some errant activity log info that was still coming through. Also, guild history info is stored on the back-end for 30 days, so the information will be there for you when we turn guild history back on Sept. 15/ Sept. 16.
ZOS_JessicaFolsom wrote: »Also, guild history info is stored on the back-end for 30 days, so the information will be there for you when we turn guild history back on Sept. 15/ Sept. 16.
Bobby_Digital81 wrote: »DenverRalphy wrote: »Bobby_Digital81 wrote: »DenverRalphy wrote: »ZOS_JessicaFolsom wrote: »What's the reason, technical or otherwise, that things like the aforementioned housing tours - a piece of content that has no urgency attached to it whatsoever - can be hotfixed, but not this? If the issue has been identified and is ready to be fixed, what caused it?
Pulling out these two questions, which we can answer now.
In simple terms, this particular bug was caused by a guild history permissions refresh issue in the client C++ code, which is why we need to do an incremental. Server code issues can be fixed with hotfixes, and some client issues (UI scripting related, for example) can be fixed via hotfix. But client C++ codes require a full patch and deploy to address.
I think the actual question is... Why does the patch have to be two weeks down the road? Why not just deploy the patch and force all players to log out and patch? Because that's what seemingly every other MMO out there is able to do when needed.
[edit] Not to mention that it's a bit worrying that it's a client side issue. Because that means that an altered/hacked game client could access data it shouldn't be able to.
Because on console, Sony and Microsoft need to go through a verification process for the updates/patches for games.
That applies to normal/major patch updates. Playstation and XBox do have provisions for emergency/urgent patch deployment.
To ZOS this isn't an emergency/urgent matter. They turned off the data so no one can see it the trader bids, etc. They don't realize how this impacts trading guilds, so they won't bother to make it an emergency to push it out quicker.
I agree with you, they need to push this out a lot sooner, but they don't think it affects guilds that much that use the guild history data to properly run guilds, especially trading guilds.
Mathius_Mordred wrote: »
Why are you banning people for informing their members of this issue? I have received a social ban and can no longer use any guild bank...
Mathius_Mordred wrote: »
@ZOS_JessicaFolsom
Why are you banning people for informing their members of this issue? I have received a social ban and can no longer use any guild bank or store because I sent out a GodSend mass mail informing folks why we are revoking bank access until this issue is resolved. This is utterly ridiculous and a completely atrocious way to treat your customers who are doing their best and spending a lot of real-world money on keeping people interested in your game. If I had treated my customers like this, I would have lost my business 20 years ago. I'm really getting tired of your AI bans, it's not helpful, and it's driving people away!
DragonRacer wrote: »Bobby_Digital81 wrote: »DenverRalphy wrote: »Bobby_Digital81 wrote: »DenverRalphy wrote: »ZOS_JessicaFolsom wrote: »What's the reason, technical or otherwise, that things like the aforementioned housing tours - a piece of content that has no urgency attached to it whatsoever - can be hotfixed, but not this? If the issue has been identified and is ready to be fixed, what caused it?
Pulling out these two questions, which we can answer now.
In simple terms, this particular bug was caused by a guild history permissions refresh issue in the client C++ code, which is why we need to do an incremental. Server code issues can be fixed with hotfixes, and some client issues (UI scripting related, for example) can be fixed via hotfix. But client C++ codes require a full patch and deploy to address.
I think the actual question is... Why does the patch have to be two weeks down the road? Why not just deploy the patch and force all players to log out and patch? Because that's what seemingly every other MMO out there is able to do when needed.
[edit] Not to mention that it's a bit worrying that it's a client side issue. Because that means that an altered/hacked game client could access data it shouldn't be able to.
Because on console, Sony and Microsoft need to go through a verification process for the updates/patches for games.
That applies to normal/major patch updates. Playstation and XBox do have provisions for emergency/urgent patch deployment.
To ZOS this isn't an emergency/urgent matter. They turned off the data so no one can see it the trader bids, etc. They don't realize how this impacts trading guilds, so they won't bother to make it an emergency to push it out quicker.
I agree with you, they need to push this out a lot sooner, but they don't think it affects guilds that much that use the guild history data to properly run guilds, especially trading guilds.
The exact same mindset that saw absolutely no big deal about removing console's ability to sort trader listings by time left two weeks before the largest trader guild event of the year.
And then was all Surprise Pikachu Face about it when we all started wailing and ripping our hair out on the forum thread about it.
The absolute disconnect is honestly hurtful and insulting.
Bobby_Digital81 wrote: »I agree with you, they need to push this out a lot sooner, but they don't think it affects guilds that much that use the guild history data to properly run guilds, especially trading guilds.
spartaxoxo wrote: »Bobby_Digital81 wrote: »I agree with you, they need to push this out a lot sooner, but they don't think it affects guilds that much that use the guild history data to properly run guilds, especially trading guilds.
Realistically, it's probably moreso a numbers thing. The number of people for whom this is a major issue is far smaller than the number of people for who this is not an issue or a minor one. It's unfortunate situation but they are weighing the needs of the entire playerbase vs the scale of the issue when making those kinds of decisions.
spartaxoxo wrote: »Bobby_Digital81 wrote: »I agree with you, they need to push this out a lot sooner, but they don't think it affects guilds that much that use the guild history data to properly run guilds, especially trading guilds.
Realistically, it's probably moreso a numbers thing. The number of people for whom this is a major issue is far smaller than the number of people for who this is not an issue or a minor one. It's unfortunate situation but they are weighing the needs of the entire playerbase vs the scale of the issue when making those kinds of decisions.
Mathius_Mordred wrote: »Why are you banning people for informing their members of this issue? I have received a social ban and can no longer use any guild bank or store because I sent out a GodSend mass mail informing folks why we are revoking bank access until this issue is resolved. This is utterly ridiculous and a completely atrocious way to treat your customers who are doing their best and spending a lot of real-world money on keeping people interested in your game. If I had treated my customers like this, I would have lost my business 20 years ago. I'm really getting tired of your AI bans, it's not helpful, and it's driving people away!
spartaxoxo wrote: »Bobby_Digital81 wrote: »I agree with you, they need to push this out a lot sooner, but they don't think it affects guilds that much that use the guild history data to properly run guilds, especially trading guilds.
Realistically, it's probably moreso a numbers thing. The number of people for whom this is a major issue is far smaller than the number of people for who this is not an issue or a minor one. It's unfortunate situation but they are weighing the needs of the entire playerbase vs the scale of the issue when making those kinds of decisions.
Has there ever been an instance where they weighed those two things and decided it was worth it to use the tools available for emergency client-side hotfixes?
I hope that this problem and the fuss that has been raised about it will finally give the zos a reason to still work and improve the guild system in the game.
After 10 years, it would be nice to give the guild leadership more tools that do not require a bunch of addons and other things. Not to mention some guild content.
katanagirl1 wrote: »I don’t know anything about running a guild but I have a crazy idea. How about just let the guild traders stay where they are without charging a fee for bidding until this crisis is over? Is that reasonable or possible? Then we can proceed as normal when things are working again.
I understand there may be a process that cannot be circumvented but I thought I would throw that out there anyway.
wolfie1.0. wrote: »katanagirl1 wrote: »I don’t know anything about running a guild but I have a crazy idea. How about just let the guild traders stay where they are without charging a fee for bidding until this crisis is over? Is that reasonable or possible? Then we can proceed as normal when things are working again.
I understand there may be a process that cannot be circumvented but I thought I would throw that out there anyway.
I mean i would object because it rewards those that abused the bug/exploit to outbid other guilds. I would rather they terminate all trading until its fixed before rewarding those that abused the system.
ZOS_JessicaFolsom wrote: »We'd like to help expedite lifting any social bans that triggered due to sending an mass mail to your guild members about this. Please reply (or DM) with your affected UserID, PSN ID, or Xbox GamerTag.
katanagirl1 wrote: »wolfie1.0. wrote: »katanagirl1 wrote: »I don’t know anything about running a guild but I have a crazy idea. How about just let the guild traders stay where they are without charging a fee for bidding until this crisis is over? Is that reasonable or possible? Then we can proceed as normal when things are working again.
I understand there may be a process that cannot be circumvented but I thought I would throw that out there anyway.
I mean i would object because it rewards those that abused the bug/exploit to outbid other guilds. I would rather they terminate all trading until its fixed before rewarding those that abused the system.
I don’t make a lot of gold off trading anymore, but I would be willing to bet that would kill a big chunk of the playerbase before it is fixed.
I realize that those in prime locations would benefit, but I don’t think it’s fair to assume all of them were cheating. It would be better to sell in a slightly less desirable location in the meantime than sell nothing at all.
katanagirl1 wrote: »I don’t know anything about running a guild but I have a crazy idea. How about just let the guild traders stay where they are without charging a fee for bidding until this crisis is over? Is that reasonable or possible? Then we can proceed as normal when things are working again.
I understand there may be a process that cannot be circumvented but I thought I would throw that out there anyway.
katanagirl1 wrote: »I don’t know anything about running a guild but I have a crazy idea. How about just let the guild traders stay where they are without charging a fee for bidding until this crisis is over? Is that reasonable or possible? Then we can proceed as normal when things are working again.
I understand there may be a process that cannot be circumvented but I thought I would throw that out there anyway.
This is a very good idea and has been done in the past. We could keep our vendors until the problem is resolved.
@ZOS_JessicaFolsom Hello, can we safely hold auctions for next week or should we not hold them? We would like an answer on this point.
*Google translate* sry
freespirit wrote: »
As someone who has been involved in running Auctions a lot I think your biggest issue will be tracking payments for items.
A simple fix would be to have the gold mailed to the organiser rather than deposited in the Guild Bank because ofc atm you will not see those deposits and that is open to abuse.
My only slight worry would be large amounts of gold being mailed because in the past that has triggered bans for possible gold selling!!
Edit:- To add, you could pass the items and collect the gold by in game trades which makes more work for sure but also makes for easy screenshots in case of any issues