Finalflash wrote:Finalflash wrote:--edited--
(edited by monkeynews friend)
>inb4 second edit
|
![]() |
|
![]() |
Ana wrote:Wow. I'm impressed.
I reckon it would serve Nost well to avoid the potential for such shit storms in the future, though, no? Just tweak the procedure to be sensible... like, server-wide announcement several times over a span of 2-3 days when you make a decision that X is in fact a bannable exploit, prior to banning anyone for it... seems like common sense tbh.
|
![]() |
Sharax wrote:Ana wrote:Wow. I'm impressed.
I reckon it would serve Nost well to avoid the potential for such shit storms in the future, though, no? Just tweak the procedure to be sensible... like, server-wide announcement several times over a span of 2-3 days when you make a decision that X is in fact a bannable exploit, prior to banning anyone for it... seems like common sense tbh.
Common sense would be not to exploit questionable game mechanics in the first place or discuss it with a GM first.
|
![]() |
Darkwinjax wrote:Sharax wrote:Ana wrote:Wow. I'm impressed.
I reckon it would serve Nost well to avoid the potential for such shit storms in the future, though, no? Just tweak the procedure to be sensible... like, server-wide announcement several times over a span of 2-3 days when you make a decision that X is in fact a bannable exploit, prior to banning anyone for it... seems like common sense tbh.
Common sense would be not to exploit questionable game mechanics in the first place or discuss it with a GM first.
Common sense dictates that this behaviour which goes on for 1 year since server release, is working according to blizzlike scripts, and as such, is an unavoidable thing that will happen to you eventually while gathering a felwood node, is not an exploit.
But you must be special so I take it you also ticketed the GM to ask if reseting DM:N and keeping the key is a game exploit.
Mongoloid.
|
![]() |