jared96 wrote:There seems to be a readily solveable solution.
1. A guild which declares war on an outpost must be "committed" to that outpost. If Guild A declares war on Guild X at 2 pm whatever,then ALL OF ITS MEMBERS shall be rendered powerless if attacking any other guild outpost.
2. Attacking Guild's get 3 reschedules and they are knocked off the que.
3. Eliminate scheduling of war on nationalholidays.
4. The cost of a 1st attack shall be the QL x 10,000.....each subsequent attack by same guild increases cost by 50%.
1 does not work, guild declaring war, dont even have to be part of the battle.
3 does not work, for once, there is other countries than yours, for second, there is other timezones than yours
And maybe if an attacking guild is defeated, they should pay a recompense either to the guild that was attacked or just as a charge. Perhaps worked out as a lower fee, the more rounds the battle lasts - therefore, not turning up at all would be a very expensive thing to do.
There would have to be a set amount of money in guild funds to cover this before an attack could even be declared - and a freeze on funds past that point until the war is over.
Last edited by ruslan on Fri Jan 06, 2006 10:41 am, edited 1 time in total.
A patch is currently in pipe to modify and fix a few things related to Outposts and PvP. I can't give you the exact and complete content of the patch yet since it's not finished, however I can provide some hints. The main points:
- You shouldn't be able to cancel a war anymore; so before declaring it, you would have to think carefully.
- A war declaration will be more expensive.
We are also aware of several other issues, which are currently still in coding process. Thus, we can't confirm yet if they will be ready for that patch. Amongst these issues :
- Fixing the pick crafting action (which doesn't work right now).
- Adding a small safe area around the respawn points (no PvP allowed).
Marjo wrote:- Adding a small safe area around the respawn points (no PvP allowed).
Thank you! This was incredibly annoying to have happen to me. Spawn in, lag a bit as everything loads, and *boom* dead without even seeing who was attacking me
Morgaine
∞ Infinity ∞ "Stay smart. Stay cool. It's time to prove to your friends that you're worth a damn. Sometimes that means dying. Sometimes that means killing a whole lot of people." Avatar of Destruction ∞ Mind Lord ∞ Heavy Armorer Master ∞ Master Pikeman ∞ Master Desert Harvester
Expert Prime Roots Forager ∞ Master of Life ∞ Executioner ∞ Expert Light Armorer ∞ Master of Torment
I had an idea that may fix the problems of:
- false declarations
- declaring war and then cancelling
- not being commited to war
- attacking multiple outposts at the same time.
The price of declaring war should depend on how many declarations of war a guild has already made without winning a battle. The price increases every time you make a new declaration, using the multipliers 1, 2, 3, 5, 8, 13, 21... etc.
The base price for declaring war is currently 500K dapper. The first declaration costs 500K, the second 1M, the third 1.5M, the fourth 2.5M, the fifth 4 million, the 7th 10.5M and so on. As soon as you win an outpost the count of declarations is reset and the first declaration costs 500K dapper again. If you wish to declare war three times before a single battle is fought, it will cost 3 Million dapper.
A guild that had declared war eight times without winning would have spent 26.5 Million and the next declaration would cost 17 Million.
The count would be reduced by one every Atys week, so that if ther had been a genuine failure to gain an outpost the cost would go back down after an Atys week.
Secondly the cost of declaring war is much too low. High level foragers can earn 1 Million in half an hour and look at the money changing hands in the Bazaar. It should cost over 5 Million to declare war, not 500K dapper.
Using 5 million as the base cost, it would cost 30 Million to make three war declarations.
This would make it very expensive to declare continuous war on an outpost.
Guilds that declare war and cancel would find themselves paying more and more.
Guilds that had misjudged their strength would have to wait; it would make them think harder about their chances of success before declaring war.
Making multiple attack declarations would be more expensive.
*thinks* EDIT: With the cost going back down after a week, the multiplier could be much greater: 1, 4, 9, 16, 25...
increase the cost of declearing war, starting price 10million then people will start to think twice about doing it, 10million isnt alot, but they wont bother repeting it...
kgrieve wrote:The count would be reduced by one every Atys week, so that if ther had been a genuine failure to gain an outpost the cost would go back down after an Atys week.
Atys week is 6 atys days, which in RL is 7hours and 12 minutes
I agree about increasing costs, but it's important not to price out the lower level guilds. 5 million to a guild without high level diggers is a lot of money still.
Also the idea of spiralling costs for battle's not won would end up really hurting small/low level guilds who were bravely trying to get an op but losing against stronger opponents.
the only way i can see of making the cost structure a bit more equatable is to base it on the region level the op is in, so the lv50 and 100 ones remain afforable and the 200 & 250 get very expensive.
On a side note, it would be nice if the q50 op's were left for newer guilds to fight over - there is nothing gained if your guild is full of high level players by owning one.. just seems a shame that everything is being dominated by older established players/guilds
Marjo wrote:- A war declaration will be more expensive.
I do not think this point will fix the problem, it could make things worse for outposts. If this is set to high, you will limit outpost to only the richest guilds. Some of the bigger guilds have so much dapper that it dose not matter how high you set the price and then you exclude the smaller guilds from being able to afford an outpost battle.
The main points:
