Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Denova Bug: Trash Respawns

First BioWare Post First BioWare Post

Felthorn's Avatar


Felthorn
06.18.2012 , 08:57 PM | #1
Hello,

I just wanted to report what might be a bug. Tonight we were working on HM Kephess, and after two attempts, we zoned in and trash was back up. We noticed that we were in a new instance server and figured, ok we will just reclear. We did that, did about 4-5 more attempts (about an hour) and the trash respawned again. It looks like the trash resets every time we zone in and get a 'new' instance of Denova.

It wouldn't be so bad if there were some cool trash drops Hint hint BW!

Anyway, hope this helps get it fixed!

~F

bjbm's Avatar


bjbm
06.18.2012 , 09:42 PM | #2
Same with us...all adds respawn after a wipe...ftl

willigan's Avatar


willigan
06.19.2012 , 12:39 AM | #3
This happens when there are more than 1 server for Denova. If you search you will see Denova (1) and Denova (2). If you get moved from one to the other the trash respawns. It has happened to us every night we've done Denova since the server transfer. And it is getting super annoying. Please fix!

Fallerup's Avatar


Fallerup
06.19.2012 , 05:18 AM | #4
trash respawn should be tied to Ops ID, not instance. That said, in MMOs like WoW, they are on a timer. don't know exactly how long it is, 2 hours? After that, if you zone out, the trash will have respawned. BUT there, trash can drop loot.
Gagota Class: Arsenal Mercenary
Member Of
Dark Brotherhood
Server: Tomb Of Freedon nadd EU

Oggthebase's Avatar


Oggthebase
06.19.2012 , 05:24 AM | #5
this is a known issue since launch, for all operations / flashpoints even ilum or the fleet...
When there are too many people in one zone, a second instance of the zone is created (or a third etc..) and the people that come in are zoned into the additional instance.
The system considers it as a soft reset and all the trash from the last boss killed respawn.

This happens the other way too, at the end of the evening when your group is in the second zone and other groups are leaving the first instance, in order to save ressources, everyone is sent back to the first instance if you re-enter it and trash will also respawn.

In order to avoid being zoned into the new instance after a wipe, you must keep your current id by having one person not release their corpse and stay in the current instance until at least another person re-enters the instance and anchors it.

Utania's Avatar


Utania
06.19.2012 , 05:25 AM | #6
I wonder if you reported that the bh comms chest were respawning the issue would get looked at faster

Shinaa's Avatar


Shinaa
06.19.2012 , 07:23 AM | #7
As someone already said, the bug is old, workaround is to never leave the instance with everyone at once, always have at least one inside (even if he is dead).
This is just one of the other things BW seems to not care at all, since there is a workaround for it, maybe they think it's ok.

Tatile's Avatar


Tatile
06.19.2012 , 12:02 PM | #8
Quote: Originally Posted by Utania View Post
I wonder if you reported that the bh comms chest were respawning the issue would get looked at faster
They'd probably say the instancing system is working as intended, then just remove all loot drops and chests. Taa daa.

DyasAlue's Avatar


DyasAlue
06.19.2012 , 01:11 PM | #9
Quote: Originally Posted by Oggthebase View Post
this is a known issue since launch, for all operations / flashpoints even ilum or the fleet...
When there are too many people in one zone, a second instance of the zone is created (or a third etc..) and the people that come in are zoned into the additional instance.
The system considers it as a soft reset and all the trash from the last boss killed respawn.

This happens the other way too, at the end of the evening when your group is in the second zone and other groups are leaving the first instance, in order to save ressources, everyone is sent back to the first instance if you re-enter it and trash will also respawn.

In order to avoid being zoned into the new instance after a wipe, you must keep your current id by having one person not release their corpse and stay in the current instance until at least another person re-enters the instance and anchors it.
You just saved my guild a lot of headachs. Next HM EC we will do this.
Server: Kass City | Name: Bounty | Level: 50 |
Class: | Alignment: IV
Gear

AllisonBerryman's Avatar


AllisonBerryman
06.20.2012 , 08:59 AM | #10 This is the last staff post in this thread.  
Hey everyone, Amber recently posted this in another thread about this issue:

Quote:
Hello everyone. We just wanted to let you know that we are aware of this issue and are working to ensure a fix for an upcoming patch. Thanks a lot for your patience, and as always, we appreciate you reporting any problems both here and in-game via /bug.
We've got a fix for this on the way!