Roo Stercogburn
Resident Freddy
- Joined
- Dec 22, 2003
- Messages
- 4,486
Kills near warcamps should not contribute to victory point gain or loss for either side.
-----
Today we had people suiciding at the Order warcamp and undermining us in the late afternoon, despite people who had been fighting for hours for control of Reikland screaming and pleading with them to stop. There were no Order anywhere in the zone of note at the time and we still could not cap it despite everyone working their nuts off.
I have never seen the like of this before.
This is a level of griefing that is way beyond what should be allowed in any game. The VP loss from a few people running repeatedly from our warcamp into the Order warcamp more than offset anything we could earn.
As a result, VPs should not be affected near any warcamps. It allows people to deliberately undermine what is already an extremely difficult task.
With little to no Order resistance in the zone by this time after many hours of hard fighting, and people farming PQs and such we still could not cap it because of these lamers.
This is wrong.
Fix it.
-----
Today we had people suiciding at the Order warcamp and undermining us in the late afternoon, despite people who had been fighting for hours for control of Reikland screaming and pleading with them to stop. There were no Order anywhere in the zone of note at the time and we still could not cap it despite everyone working their nuts off.
I have never seen the like of this before.
This is a level of griefing that is way beyond what should be allowed in any game. The VP loss from a few people running repeatedly from our warcamp into the Order warcamp more than offset anything we could earn.
As a result, VPs should not be affected near any warcamps. It allows people to deliberately undermine what is already an extremely difficult task.
With little to no Order resistance in the zone by this time after many hours of hard fighting, and people farming PQs and such we still could not cap it because of these lamers.
This is wrong.
Fix it.