Please fill in as much as you can :
Date and Time : Happening since launch
Game Control Mode (Keyboard/Joypad/Mouse) : Keyboard
Where it happened (which map, which quest, which npc, etc) : All maps
Bug Description : Guild War limitations extending to the cooldown period.
Steps to reproduce the issue :
- Declare war on guilds
- Wait for the duration to expire, so that the war ends and the war cooldown begins
- Try to declare war on other guilds, or invite members of the guilds you were previously at war with. You can’t.
Not sure whether it’s bugged or it’s simply stupid design, but the restrictions for being at war with guilds are persisting during the war cooldown period.
The “benefit” of being at war is the ability to kill enemy guild members and towers for 7 days. The “drawback” or “cost” of being at war is being unable to join parties that have at least 1 member belonging to enemy guilds.
The 7 day cooldown period after a war means you cannot declare war again during this period. The benefits of being at war are gone(killing people/tower), but the restrictions are still in place. You cannot kill them anymore, but you still CANNOT JOIN THEIR PARTIES.
Furthermore, since the latest patch, the cooldown period is also counting towards the 3 war limit. My guild has 2 active wars right now, and about 5 or 6 on cooldown. When I tried to wardec a guild earlier today, it gave me an error that I am over the guild wars limit. This shouldn’t be happening, either.
The 3 wars limit is beyond stupid and pointless, but for the cooldowns to count towards the limit is unforgivable. The PvP guilds want to fight each other but can’t. Even if we wait, we’ll only be able to war one guild, while our current two will be on cooldown by then.
Please give us some clarification: Is this intended? And if so, could we have it changed? Not being able to party with people you’re not at war with, and having to sit out a whole week without fighting is restricting our gameplay, for no reason at all.