Page 1 of 1

rag dropping 0 loot bug

PostPosted: Sun Nov 15, 2015 11:11 pm
by Imbaslap
seems like this is still around... and no fixes or anything..
happened again today for Blacklisted = hammer drops and only gold dropped.
no loot or anything. GG Nost. bug from 2nd week release still present. 8-)

Re: rag dropping 0 loot bug

PostPosted: Sun Nov 15, 2015 11:13 pm
by gangstanigga
private server provided free

Re: rag dropping 0 loot bug

PostPosted: Sun Nov 15, 2015 11:16 pm
by Imbaslap
bugged content since release.
10 yrs development.
25 developers.
must be EU based to get GM support.
loot policy doesn't cover their bugged raid content with bosses dropping 0 loot.
must be EU to get restored loot.
EU favored just like when BWL released and resetting bosses for EU guilds.

Re: rag dropping 0 loot bug

PostPosted: Sun Nov 15, 2015 11:23 pm
by Setup
Sucks to only get 4 hours of sleep so I can attend a raid where the only boss that matters doesn't drop loot.

It would sting less if it didn't happen to us so often. We've lost what, 12 drops in three or four weeks?

gangstanigga wrote:private server provided free


This comment would be worthwhile if it wasn't common practice among private servers to refund items in these instances, to respawn the boss, or otherwise provide aid. Really, what you should be saying is "go play elsewhere", which is, incidentally, exactly what we think about when this kind of thing happens.

I love Nost, but with the inevitable bugs and crashes involved in running a private realm, turning a blind eye to these kinds of issues is a real disappointment.

Re: rag dropping 0 loot bug

PostPosted: Mon Nov 16, 2015 12:19 am
by Guybrush
If GMs aren't willing to help with raid bugs what exactly is the point of having GMs?

Re: rag dropping 0 loot bug

PostPosted: Mon Nov 16, 2015 12:35 am
by Nano
You complain this has happened multiple times but I've seen no bug report from your guild describing your situation. If you wish for some bug to be fixed, you need to provide us with as much information as possible so we can try to replicate the issue and identify the bug.