Nealio
01-29-2011, 08:02 PM
Location: Paw Spires, SK
On Rodcet Nife live server each spire was considered it's own camp. On live groups would camp each spire just out of aggro range of the spawns. No spire group would pull another spires spawns. The hills behind were free game for any spire group if the hills themselves were not camped. These spawns are static spawns, they are not roamers. They spawn and remain in place until pulled.
Previously on this server, I have seen this camping style respected. Yet today I come to Paw, and pull the northern most Spire. The group at the middle spire (one druid and one sk) kill their mob. The sk then walks over to my spire and stands at the exact spot where the mob spawns. He tells me "GL on getting aggro, I was here first".
I get up and pull a mob from the hills. While I'm doing this, the middle spire spawns, and the ogre/sk duo engage it. As I am kiting my hill spawn, the southern-most spawn pops. I snare it and begin kiting it. I turn around to drop another dot, and notice the ogre and druid have tagged my mob after I snared it and run off with it and their middle spawn.
I petition this griefing. A GM responds. He tells me that if I am not on the spawn point it is not claimed. I tell him that I am a druid, I cannot stand on a spawn point. No response. I tell GM that the offending party also grabbed a mob I had snared first. No response.
An hour later the sk/druid duo were still at Paw spires, apparently with no accounting for their actions.
1st part of my question; how the hell is a druid or any caster for that matter expected to claim a camp if we have to sit right on top of the spawn point?
2nd part; how are the Paw spires not protected as bona fide camps that must be sat atop of?
3rd part; how is it acceptable to aggro a mob, WHILE currently engaged with a prior pull, that has been snared by another party first .
On Rodcet Nife live server each spire was considered it's own camp. On live groups would camp each spire just out of aggro range of the spawns. No spire group would pull another spires spawns. The hills behind were free game for any spire group if the hills themselves were not camped. These spawns are static spawns, they are not roamers. They spawn and remain in place until pulled.
Previously on this server, I have seen this camping style respected. Yet today I come to Paw, and pull the northern most Spire. The group at the middle spire (one druid and one sk) kill their mob. The sk then walks over to my spire and stands at the exact spot where the mob spawns. He tells me "GL on getting aggro, I was here first".
I get up and pull a mob from the hills. While I'm doing this, the middle spire spawns, and the ogre/sk duo engage it. As I am kiting my hill spawn, the southern-most spawn pops. I snare it and begin kiting it. I turn around to drop another dot, and notice the ogre and druid have tagged my mob after I snared it and run off with it and their middle spawn.
I petition this griefing. A GM responds. He tells me that if I am not on the spawn point it is not claimed. I tell him that I am a druid, I cannot stand on a spawn point. No response. I tell GM that the offending party also grabbed a mob I had snared first. No response.
An hour later the sk/druid duo were still at Paw spires, apparently with no accounting for their actions.
1st part of my question; how the hell is a druid or any caster for that matter expected to claim a camp if we have to sit right on top of the spawn point?
2nd part; how are the Paw spires not protected as bona fide camps that must be sat atop of?
3rd part; how is it acceptable to aggro a mob, WHILE currently engaged with a prior pull, that has been snared by another party first .