Page 1 of 2
Is it safe to say...?
Posted:
Mon Mar 14, 2016 8:07 pm
by Keftenk
viewtopic.php?f=6&t=38023&start=10#p267012Now that someone actually responded to the issue. Moving forward. Is it safe to say that this "exploit" has been "corrected" and now not Blizzlike? Or at least being addressed? Or is this like Nost's version of the "trust dollar" and it'll remain in the game?
Re: Is it safe to say...?
Posted:
Mon Mar 14, 2016 8:12 pm
by Judgeandjuried
Yeah seems like simultaniously looting a felwood plant is major bug abuse. GG bros.
Not to mention only Moo had a previous warning on his account. Slip's one was on a different account and Ranalape had none.
And of course the fact that literally hundreds of people have done this but only these guys got permanently banned for it because one salty nerd reported them.
Re: Is it safe to say...?
Posted:
Mon Mar 14, 2016 8:13 pm
by Keftenk
Regardless, I'm just curious if this "bug" has been fixed on Nost or if it's still on live. Or if there is any intention on "fixing" it.
Re: Is it safe to say...?
Posted:
Mon Mar 14, 2016 8:20 pm
by Harm
Keftenk wrote:Regardless, I'm just curious if this "bug" has been fixed on Nost or if it's still on live. Or if there is any intention on "fixing" it.
It is still live
Re: Is it safe to say...?
Posted:
Mon Mar 14, 2016 8:22 pm
by Judgeandjuried
Re: Is it safe to say...?
Posted:
Mon Mar 14, 2016 9:48 pm
by Sethzer
Judgeandjuried wrote:
Sad but true
Re: Is it safe to say...?
Posted:
Mon Mar 14, 2016 9:53 pm
by Robotron
I lost.
Re: Is it safe to say...?
Posted:
Tue Mar 15, 2016 4:26 am
by Keftenk
Harm wrote:Keftenk wrote:Regardless, I'm just curious if this "bug" has been fixed on Nost or if it's still on live. Or if there is any intention on "fixing" it.
It is still live
Amazing
Nost keeps on impressing.
If this "bug" is such a dire importance to ban over it should be hot fixed immediately, unless of course it actually has a low priority. Which then begs the question why people are even being banned for something with such low importance...
Re: Is it safe to say...?
Posted:
Tue Mar 15, 2016 5:27 am
by Snautz
What is the point of this thread?
I don't see anything inherently bad with fixing blizzlike bugs, like nost have done before btw.
I'm sure costum fixes can be a bit trickier to pull off, especially with nosts limited time and resources, so I think it's reasonable to have a "Bug abuse at your own risk untill we fix it" policy in order to discourage people from even thinking about breaking the rules.
If you want to change the staffs view on things, hammer home the key points instead of dabbling around in these passive-aggressive lockbait threads.
I think some valid points can be made about:
The lack of communication
The classification of the bug (major vs minor)
The harshness of the bans when you take the fact that it was a blizzlike bug into account, and when you put it up against another blizzlike bug that got fixed (AV group queue) which arguably had a bigger server wide impact, but still only triggered a temp ban.
PS. Before anyone wants to fite me irl over whether or not this actually is bugs, I'm just going by what the nost staff consider to be bugs, I'm really not that eager to fight this cause since one of the people who got thrown under the bus was slipry.
Re: Is it safe to say...?
Posted:
Tue Mar 15, 2016 5:35 am
by Keftenk
Not sure how this is a lock-bait thread since it's really just a general question of understanding the next steps of this ridiculous ban process with the "bug". Which by the way isn't a Blizzlike bug. Never was bannable in retail, never was shamed in retail.
The "duplication" literally has no harmful effects on the server whatsoever. It makes you question why things like Onyxia Head, Nef Head, and Heart of Hakkar buffs aren't considered bannable. But what's even more concerning is how many people in the community think this is absurd, but Nost is being as stubborn as a mule with their actions and logic.