Two chests in the 'Sand Reef' quest, and two chests in the 'Barrow' quest seem to be bugged. Basically, if anybody opens the chests in question after a reset, they will stay open and no loot will spawn in them until the next reset. This means that unless you're in the party that first completes the quest after a reset, you're going to get jibbed on loot!
Its not 100% but it's high probability. My suggestion would be have chests break and respawn when the quest is taken that way it won't matter if chests are bugged!
I'm not sure what causes chest to remain 'open'. It's not a bugged chest, it can potentially happen to every chest. :/
It does. I can tell you why this happens
Instead of pressing that CLOSE button, you click away from it. Apparently the CLOSE script on the chest doesn't FIRE. Thus, the Chest remains OPEN.
Thank you.
Thomas is very wrong on this one, it can occur even when you click close. It is due to lag between client and server when the person closes/clicks away from the chest. I've had chests bug after pressing the close button.
Do some research before speaking as if things are matter of fact Thomas!
Edit: To simplify when you or the server are experiencing lag sometimes a small spike as you hit the close button or click away locks the chests in the open position.
It's from lagg and it can happen on anything, but it happens more when you have a bunch of containers grouped together. This is because of people clicking on one, then moving directly to the next without pressing the close button (like the three chests in the Dock Barrow quest, many people click one>loot>click the second>loot>click the third>loot>walk away, instead of click one>loot>close>click the second>loot>close>click the third>loot>close>walk away), the containers that appear open are bugged and there will be no loot in them the next time someone takes the quest. I would agree that after a new group takes the quest having all containers being destroyed then respawning would be a good solution. I would not recomend having them be destroyed then respawning as soon as a quest is ended, as it is an easilly exploitable way of gaining 2x the treasure per quest.
Nightshadow summarized it quite well. Please note that, while it can happen on any container at any time, MOST of the time it is due to players not clicking to close the container, and instead doing another action (like opening the next container).
I think, as LP said, a script to destroy+respawn the chests when the quest is taken would be one way of avoiding this.
Depending on the EFUQS, it might just be easier to add a couple lines to close every chest in the area, before it fires the part that generates treasure.
I am not 100% on this, but I think it will work.
I that has been tried on other servers in the past, it basically makes the chest appear closed though its still bugged. Though that was a patch or two ago.
Moving the containers further apart should reduce the likelihood of it occurring, as moving away from a container while the inventory window is still open doesn't seem as lag-susceptible as opening another container in close proximity.
The evidence that supports my claim is that it happens on certain quests more than others, and the quests where it happens more frequently have containers in close proximity.
I think you should just hit the Close Button more often, <3, Lag isn't a real problem on this server anymore, at least, server wide lag isn't.
Quote from: Thomas_Not_very_wise;94223I think you should just hit the Close Button more often, <3, Lag isn't a real problem on this server anymore, at least, server wide lag isn't.
Quote from: Lupine Grace;94054Edit: To simplify when you or the server are experiencing lag sometimes a small spike as you hit the close button or click away locks the chests in the open position.
:p
Lag spikes will still occur, regardless of how fast the server is, due to the player's PC, the internet route, etc, etc
With me, it happens more when I hit the close button, also, it seems to happen more when I am looting a dead body of something I killed. I just click away and move to the next one, and I haven't bugged a chest in quite a few days going by this.