HoH Chest Bug at Isle of the Nameless (outside Temple of Balthazar)

Someone told me that there had been an HoH chest spawned in Isle of nameless, outside of temple of balthazar for an hour, and that people had quote: "spammed the shit out of it" before it got removed.

Anyone else knows anything about this bug? Anyone have screenshots? Is abusing this grounds for punishment?

Confirmed and, can we get a rep from ANET to confirm whether there will be punishments for abusing this knowingly?

I think someone may have pulled your leg.

yeh yeh, HoH Chest there.. then he woke up ^^

Well, the reason why I'm posting this on forums is because the person who did tell me is not normally one to 'pull my leg', and is normally a serious guy. *shrug* the reason why I posted on Riverside was to see if anyone else beyond his guildies had also found out.

its in the official wiki...they removed it unfortunately for me xD

its true..anet where quick to remove it aswell..the whole reason that 1 area was shut down and u froze when u tried to get in...was a zaishen chest..im guilty of exploiting it :P

If A-Net finds out that anyone exploited it, those people will be banned undoubtedly. Not smart admitting that Pupu.

Wonder if anyone got good stuff, though.

Will anyone be punished? Isn't this like exploiting the duping bug?

Can Gaile Gray confirm or deny anything here?

Doesn't sound like a bannable offense.

It's not like they went hacking or duping.

admittedly, I don't see a large difference between the two. Unless everyone who started opening the chest as many times as possible seriously believed ANET put it there as a kind gesture for us all.

what can i say im honest , being banned from using a chest that they put there is not justice, bug or not, it was an error on thier side.

Damn, I allways miss things. Even if r8 gold items were falling down from the sky in GW, I would prolly miss it...

People weren't banned when you could use duped skills in PvE/PvP, I highly doubt people will be banned for opening a chest.

Anyways this bug was fixed, no point in having a thread about it now.