ZOS_GinaBruno wrote: »Which platform are you attempting to purchase crowns for?
ZOS_GinaBruno wrote: »Sorry one more question, could you confirm if you all are attempting to purchase on our website, Steam, Epic or some other storefront? Feel free to just post a screenshot if that would be easier.
Edit: This may actually be resolved. When you have time, could you confirm? Thank you!
ZOS_GinaBruno wrote: »Thanks, looking into this now!
Freilauftomate wrote: »This is what people want when they ask for communication. If we could get this kind of support for the game, and not just the crown store it would be awesome.
Photosniper89 wrote: »ZOS_GinaBruno wrote: »Thanks, looking into this now!
How about we get the 24+ hour entire PvP server roll back issue up on the dev tracker? I know $ is important to you all so that is why you jumped on the crown store issue from this morning but PvP is literally unplayable and your lack of communication the issue, though not surprising, is disappointing at best.
Hi All, we are aware of this issue currently and investigating. We'll update once we have more. Thanks all.
Hi all, just following up after chatting with the team. As some of you have mentioned, holding block first still works to replace the prop with a weapon. So that should work for the time being. We are looking into what caused the other method to stop working as we did not intentionally do anything to change this.
If you could, it would be great to know what platform everyone is using. This may help narrow down any specific issues if this is only impacting PC or console.
Freilauftomate wrote: »This is what people want when they ask for communication. If we could get this kind of support for the game, and not just the crown store it would be awesome.
Photosniper89 wrote: »ZOS_GinaBruno wrote: »Thanks, looking into this now!
How about we get the 24+ hour entire PvP server roll back issue up on the dev tracker? I know $ is important to you all so that is why you jumped on the crown store issue from this morning but PvP is literally unplayable and your lack of communication the issue, though not surprising, is disappointing at best.
Hi all, providing a brief update here. As noted before, the team is aware of this issue and is working to resolve this. The team is still investigating and testing a possible fix. Once we can verify that the fix works and is safe to deploy, we will follow up. We know this is an inconvenience and we appreciate your patience as we work through this.
We have added this to the Dev Tracker for visibility.