No Trusted Required For Army Replacements
Please sign this petition if you agree that the need for Trusted Rights should be removed for replacing armies in GvG.
You can also give +1 to this in the Ideas Section of the Game Forum - under the same title - No Trusted Required For Army Replacements
This system, which requires trusted rights to replace an army, is anti-social, it creates divides within guilds and excludes newer members and inexperienced players from participating in a simple aspect of GvG. Such rights cannot be given to inexperience guild members as it creates the risk that they may unintentionally siege a sector and waste goods or worse, grant freedom to sectors. It also creates the risk of such actions being carried out maliciously. Additionally, it wrongly suggests that some members are considered to be trusted whilst others are not.
The notion that "Trusted Rights" should be required for Army Replacement is absurd mainly because;
1- You have no choice but to allow the majority of the guild to replace if you wish to protect your sectors. You cannot expect to rely on just a few members. The burden would be just too much.
2- Thus, almost the entire guild is required to have the rights to do everything - just so they can carry out a not so insecure action - replace an army.
3- Since the only security issue with replacing armies is that a member can replace all sectors with rogues there isn't really a security issue for 3 reasons;
(a) How many players are really going to be able to replace more than a few sectors since you need 64 Rogues a sector
(b) Even if the player had that many, who really wants to sacrafice that many rogues as they are then forever lost and if you replace on too many sectors - no fighting
(c) With not being able to delete armies anymore, the worst they can do is replace sector's armies with 8 rogues. This can be countered in many ways without jeopardising security if the guild is smart enough - however granting freedom or the use of goods cannot be countered - Once it's done it's done.
It is ridiculous that this problem is still on-going. All this and more was said in the discussion of the update that brought about this hindrance. Please fix this problem immediately.