Lockets of Escape

[Sithel1988]

i know

[Daldolma]

Originally Posted by GuisedShaman [You must be logged in to view images. Log in or Register.]

Im not blowing it out of proportion, I know these Lockets aren't going to cause a huge fluctuation in the market and ruin everyone's day. I know they are rare so its not like 100's of them dropped. This situation isn't what I'm concerned about.

Im concerned that people were abusing a known bug. This isn't up to debate to say it was intended for these to drop. Divinity/whoever knew this wasn't supposed to drop, and they stayed there knowing that. This is a direct violation of the rule I posted.

I don't see how this isn't against the rules.

Yes this may be similar to the Gem Encrusted Rings, but as you said this wasn't a high priority item. But if Pre Nerf Fungi's were dropping again you know everyone would have their panties in a bunch.

Just because it didn't cause a huge problem in the market then it's apparently ok to do this? Any bug that doesn't cause a huge problem in the market is now ok to abuse for a little because it's not that big of a deal? Thats a pretty bad stance on cheating/exploiting

You're just making a lot of assumptions is all. If they sat there for a week racking up loot before making this known, then I agree -- punishment is in order. But if it was petitioned immediately and they were in contact with GMs, then what are you punishing them for? Camping Chief? They're playing the ball as it lays. It all comes down to their openness with GMs. And obviously I'm assuming they didn't disobey any orders from GMs.

It comes down to information we don't have and will never know for sure. If they petitioned immediately and GMs said cool, thanks, we'll fix it soon, then it's the same as any other non-classic error pending correction. If they were sneaky about it and camped it for awhile before petitioning, or didn't petition at all, then they should be punished. By the way, they might have been punished for all we know. That kind of information isn't released. I imagine it all depends on how they went about petitioning, and whether or not they disobeyed orders from the GMs.

[GuisedShaman]

Originally Posted by Daldolma [You must be logged in to view images. Log in or Register.]

You're just making a lot of assumptions is all. If they sat there for a week racking up loot before making this known, then I agree -- punishment is in order. But if it was petitioned immediately and they were in contact with GMs, then what are you punishing them for? Camping Chief? They're playing the ball as it lays. It all comes down to their openness with GMs. And obviously I'm assuming they didn't disobey any orders from GMs.

It comes down to information we don't have and will never know for sure. If they petitioned immediately and GMs said cool, thanks, we'll fix it soon, then it's the same as any other non-classic error pending correction. If they were sneaky about it and camped it for awhile before petitioning, or didn't petition at all, then they should be punished. By the way, they might have been punished for all we know. That kind of information isn't released. I imagine it all depends on how they went about petitioning, and whether or not they disobeyed orders from the GMs.

Sure if a GM said alright go camp it for 2 weeks while we fix it then don't punish them because they asked and its all good.

But to think they asked and the GM/Guide/Rogean/Whoever's in charge of this sort of situation and they responded with "ya its a known bug but go ahead and farm it while we fix it" is pretty messed up.

If they announced to everyone on the server "oh by the way we messed up and lockets are dropping again, farm them while you can" right after Divinity petitioned then I could see it maybe being ok. But they didn't, no one was even really aware till it was already a week into the bug when Eccezan posted the thread in RnF.

I'm not looking to out Divinity for this, I'm not even really pressed on them getting banned or anything like that.
Im pressed to see why a GM would let this go on.

When VP dragons were being pulled to some spot that was not allowed, Amelinda went and put mobs up there that had the names "Don't pull things here" or something to that extent. It would be incredibly easy for a gm to say oh ok they are dropping and do the same thing. Name them "destroy your lockets that drop or face the banhammer".

Either way its done and over with and for all I know they were banned or reprimanded in some way
This thread will get lost by tomorrow and we all go back to not caring.

[Rhambuk]

One of members was camping chief for a normal drop, after the patch he got a locket drop. He petitioned, nilbog responded with a thank you our member asked if it was okay to continue camping it or if it should be left alone. Nilbog did not respond. He continued camping it for the drop that he originally wanted and sent a /petition everytime there was a bugged drop, not just the lockets as he was dropping 2 loot items instead of one.

[Daldolma]

Originally Posted by GuisedShaman [You must be logged in to view images. Log in or Register.]

Sure if a GM said alright go camp it for 2 weeks while we fix it then don't punish them because they asked and its all good.

But to think they asked and the GM/Guide/Rogean/Whoever's in charge of this sort of situation and they responded with "ya its a known bug but go ahead and farm it while we fix it" is pretty messed up.

If they announced to everyone on the server "oh by the way we messed up and lockets are dropping again, farm them while you can" right after Divinity petitioned then I could see it maybe being ok. But they didn't, no one was even really aware till it was already a week into the bug when Eccezan posted the thread in RnF.

So then your problem isn't that there was an error, or whether or not it was correctly petitioned. You're upset that it wasn't common knowledge until it was too late. Which is really another matter entirely.

[Rhambuk]

Originally Posted by Daldolma [You must be logged in to view images. Log in or Register.]

So then your problem isn't that there was an error, or whether or not it was correctly petitioned. You're upset that it wasn't common knowledge until it was too late. Which is really another matter entirely.

Which it is also against the rules to announce an exploit/bug to the community.

[Autotune]

Originally Posted by Daldolma [You must be logged in to view images. Log in or Register.]

^ Probably right. Price will be high immediately, then dip low, then rise again in Velious. Just gotta hope the market doesn't get picked bare by less discerning buyers.

Velious is ages away, plenty of time to grab a locket for cheap. (protip, get 2 and not both at the same time from the same person)

Not that it really matters, everyone will be selling binds in PoM which means it will be super cheap to just get it done or the more preferable method will be joining a guild who will bind their members for free.

[GuisedShaman]

I mean I could have gone and camped it myself If I wanted to after it was common knowledge.

And it was common knowledge for at least a week. But I didn't

Honestly it's not a big deal like you said

I'm not upset it wasn't common knowledge, I'm more upset it was allowed to happen for so long. As I said before if it was a different situation and it was 2 weeks before, say it was pre nerf fungi's, they fixed pre nerfs dropping no one would be argueing with me.

If Nilbog did say thanks for reporting the bug, why didn't he take the time to respond and say stop farming them when he knows more then anyone that it shouldn't be farmed. Im upset at this happening more then some people making 150k from one dropping(which is whatever, lame, but whatever)

I'm not looking for anyone really to answer this question besides Nilbog himself or whoever responded to the petition. It just seems weird they would let it happen.

[nilbog]

Fixed it immediately and waited for update.

Specifics regarding disciplinary decisions isn't going to be public knowledge from me. What I said or didn't say to anyone shouldn't be public knowledge either.

Thanks.