Lmao than you really don't know ZOS If you believe that.Mor Ethan likely they have already sent this build to Microsoft and Sony.So t be fixed by the update.
No way they will let it go live like that now that they know... i mean come on its like the devs encouraging exploiters.
Needs to be fixed ASAP. It is already public all over the game and guild chats etc, posting on forums about something like this doesn't change anything. Since it is a set and pretty easy to obtain and it is BoE. I do not think posting it on the forums will cause a lot of harm, it will however cause a fast fix.why you went public with this?? Seems a prety dumb move, really.
You should have taken this to them, and only went public if no response / unwilling to fix it on a reasonable time frame.
SienneYviete wrote: »AzraelKrieg wrote: »why you went public with this?? Seems a prety dumb move, really.
You should have taken this to them, and only went public if no response / unwilling to fix it on a reasonable time frame.
Chances are Nifty has submitted it to ZOS privately but also wanted to show everyone else what is going on
What's the point of showing this to everybody else?
This can only mean an extended downtime to find a fix at best, or broke leaderboards and huge amount of sets being farmed at worse
Much like the rearming trap exploit upon IC release the more people know about this and as sad as it is to say the more people exploit the hell out of it the quicker it will get fixed. IMO once a gamebreaking bug like this is released for general consumption the damage has already been done to the leaderboards and pvp, we just have to hope that ZOS acknowledges it and fixes it as soon as possible.
It is extremely well known in game.SienneYviete wrote: »AzraelKrieg wrote: »why you went public with this?? Seems a prety dumb move, really.
You should have taken this to them, and only went public if no response / unwilling to fix it on a reasonable time frame.
Chances are Nifty has submitted it to ZOS privately but also wanted to show everyone else what is going on
What's the point of showing this to everybody else?
This can only mean an extended downtime to find a fix at best, or broke leaderboards and huge amount of sets being farmed at worse
Much like the rearming trap exploit upon IC release the more people know about this and as sad as it is to say the more people exploit the hell out of it the quicker it will get fixed. IMO once a gamebreaking bug like this is released for general consumption the damage has already been done to the leaderboards and pvp, we just have to hope that ZOS acknowledges it and fixes it as soon as possible.
Pretty sure this bug was fairly unknown since the patch is very recent. He should have waited a private response from zos first, this is a too rushed. Quite irresponsable really.
@Funkopotamus you got to give them at least a chance to react first.
SienneYviete wrote: »AzraelKrieg wrote: »why you went public with this?? Seems a prety dumb move, really.
You should have taken this to them, and only went public if no response / unwilling to fix it on a reasonable time frame.
Chances are Nifty has submitted it to ZOS privately but also wanted to show everyone else what is going on
What's the point of showing this to everybody else?
This can only mean an extended downtime to find a fix at best, or broke leaderboards and huge amount of sets being farmed at worse
Much like the rearming trap exploit upon IC release the more people know about this and as sad as it is to say the more people exploit the hell out of it the quicker it will get fixed. IMO once a gamebreaking bug like this is released for general consumption the damage has already been done to the leaderboards and pvp, we just have to hope that ZOS acknowledges it and fixes it as soon as possible.
Pretty sure this bug was fairly unknown since the patch is very recent. He should have waited a private response from zos first, this is a too rushed. Quite irresponsable really.
@Funkopotamus you got to give them at least a chance to react first.
Needs to be fixed ASAP. It is already public all over the game and guild chats etc, posting on forums about something like this doesn't change anything. Since it is a set and pretty easy to obtain and it is BoE. I do not think posting it on the forums will cause a lot of harm, it will however cause a fast fix.why you went public with this?? Seems a prety dumb move, really.
You should have taken this to them, and only went public if no response / unwilling to fix it on a reasonable time frame.
Needs to be fixed ASAP. It is already public all over the game and guild chats etc, posting on forums about something like this doesn't change anything. Since it is a set and pretty easy to obtain and it is BoE. I do not think posting it on the forums will cause a lot of harm, it will however cause a fast fix.why you went public with this?? Seems a prety dumb move, really.
You should have taken this to them, and only went public if no response / unwilling to fix it on a reasonable time frame.
This will not be fixed on console for at least 1-2 months after release. PC sure it is gonna be fixed "soon".
I still do not understand tho, I made a WW build last week on PTS and it was fixed there.......................................
DRXHarbinger wrote: »Needs to be fixed ASAP. It is already public all over the game and guild chats etc, posting on forums about something like this doesn't change anything. Since it is a set and pretty easy to obtain and it is BoE. I do not think posting it on the forums will cause a lot of harm, it will however cause a fast fix.why you went public with this?? Seems a prety dumb move, really.
You should have taken this to them, and only went public if no response / unwilling to fix it on a reasonable time frame.
This will not be fixed on console for at least 1-2 months after release. PC sure it is gonna be fixed "soon".
I still do not understand tho, I made a WW build last week on PTS and it was fixed there.......................................
16th August. The farm begins...scaled to level 45 of course if it works...17th August. ..dro m'artha destroyers everywhere. ZOS need to delete it before everyone gets what they don't deserve if they can't fix it. Add it later in. Resetting leaderboards will only do so much.
Love to see some malubeth scum try and outheal that.
updegramub17_ESO wrote: »How does the OP have 749 champion points...
updegramub17_ESO wrote: »How does the OP have 749 champion points...
whiteshadow711jppreub18_ESO wrote: »Holy *****BEEP***** My friend Crim is gonna flip on this..
DRXHarbinger wrote: »Needs to be fixed ASAP. It is already public all over the game and guild chats etc, posting on forums about something like this doesn't change anything. Since it is a set and pretty easy to obtain and it is BoE. I do not think posting it on the forums will cause a lot of harm, it will however cause a fast fix.why you went public with this?? Seems a prety dumb move, really.
You should have taken this to them, and only went public if no response / unwilling to fix it on a reasonable time frame.
This will not be fixed on console for at least 1-2 months after release. PC sure it is gonna be fixed "soon".
I still do not understand tho, I made a WW build last week on PTS and it was fixed there.......................................
16th August. The farm begins...scaled to level 45 of course if it works...17th August. ..dro m'artha destroyers everywhere. ZOS need to delete it before everyone gets what they don't deserve if they can't fix it. Add it later in. Resetting leaderboards will only do so much.
Love to see some malubeth scum try and outheal that.