Fires of Heaven Guild Message Board - View Single Post

Nakilos · 08-20-2003, 05:43 AM

It isn't by guild, its an individual player who starts it. We discovered this when one evening we had someone who just got back from a week vacation being the first one to zone in to the tier 1 events, causing a new instance to be started, and resulting in delaying the raid 1 hour while we waited for that instance to stop. It also seems to temporarily flag all people who were in said instance for the following days raid days likely when you proceed to the next tier (this would explain why no one else was able to zone in when the just off vacation player zoned in first). I assume it was done this way to prevent cheese farming time - you could effectively just clear time in 1-2 days, start a new instance with another member and clear another set of spawns while the first instance respawns.

Regardless, that is a pretty ass problem especially for servers who are rediculously overcrowded. I can't wait til full instancing actually works and this pseudo instancing goes away. I would expect within the next 2-4 months most servers will have 3-6+ guilds in Time and without a working system, its just a big clog at the high end.

Oh wanted to add Furor is likely right about there only being 2 saved instances at a time, because we have yet to experience this problem with 1 other guild in Time, and they haven't ended up with assorted tiers up/down and vice versa. I would assume the "save" happens every time a part of a tier is completed (meaning if you kill 1 god, 3 will be up the next day, or kill 1 tier 2 boss, a shadow would be up if you left after killing just 1) rather than at just 1-2 specific points.

08-20-2003, 05:43 AM	#8 (permalink)
Nakilos Registered User Join Date: Jan 2003 Posts: 1,591 +0 Internets	It isn't by guild, its an individual player who starts it. We discovered this when one evening we had someone who just got back from a week vacation being the first one to zone in to the tier 1 events, causing a new instance to be started, and resulting in delaying the raid 1 hour while we waited for that instance to stop. It also seems to temporarily flag all people who were in said instance for the following days raid days likely when you proceed to the next tier (this would explain why no one else was able to zone in when the just off vacation player zoned in first). I assume it was done this way to prevent cheese farming time - you could effectively just clear time in 1-2 days, start a new instance with another member and clear another set of spawns while the first instance respawns. Regardless, that is a pretty ass problem especially for servers who are rediculously overcrowded. I can't wait til full instancing actually works and this pseudo instancing goes away. I would expect within the next 2-4 months most servers will have 3-6+ guilds in Time and without a working system, its just a big clog at the high end. Oh wanted to add Furor is likely right about there only being 2 saved instances at a time, because we have yet to experience this problem with 1 other guild in Time, and they haven't ended up with assorted tiers up/down and vice versa. I would assume the "save" happens every time a part of a tier is completed (meaning if you kill 1 god, 3 will be up the next day, or kill 1 tier 2 boss, a shadow would be up if you left after killing just 1) rather than at just 1-2 specific points. Last edited by Nakilos : 08-20-2003 at 05:47 AM.