DeletedUser
Guest
Proposal:
The supporter gets only 1 report per attack on his support, instead of 1 by attack and by supporting city.
Have you Checked the DNS and PSI lists in the Archives? Is this idea similar to one that has been previously suggested?
Checked hundreds of threads, didn't see it
Reason:
When big players attack each other, it's often, let's say, 30 cities attacking vs 30 cities supporting (can be much more). Multiplicate the 2: you'll have the number of reports the supporter will receive. I and others have sometimes spent over an hour browsing through all this, trying to see what happened. Some prefer to erase them all without a look...
Details:
If a player is supporting a city with more than 1 city, and his support gets attacked, he receives a global report for all the support that was attacked at the same time.
Visual Aids:
Well, imagine coming back home and having 900 reports to read...
A scheme of what I imagine:
Balance:
The supporter gets a better view of what happened.
Abuse Prevention:
Not needed
Summary:
Instead of 30*30 useless reports, the supporter gets 30 grouped reports. Assets:
- It will avoid hours of useless browsing
- The supporter gets a better view of what he has sent and what happened to it
- Possible interest for Inno: sending 1 grouped report could make less work for their Internet connection than 30 reports thrown at the same second
The supporter gets only 1 report per attack on his support, instead of 1 by attack and by supporting city.
Have you Checked the DNS and PSI lists in the Archives? Is this idea similar to one that has been previously suggested?
Checked hundreds of threads, didn't see it
Reason:
When big players attack each other, it's often, let's say, 30 cities attacking vs 30 cities supporting (can be much more). Multiplicate the 2: you'll have the number of reports the supporter will receive. I and others have sometimes spent over an hour browsing through all this, trying to see what happened. Some prefer to erase them all without a look...
Details:
If a player is supporting a city with more than 1 city, and his support gets attacked, he receives a global report for all the support that was attacked at the same time.
Visual Aids:
Well, imagine coming back home and having 900 reports to read...
A scheme of what I imagine:
Header:
[Attacking city] (attacking player) is attacking your support in [Supported city] (day, time)
Icon Icon
Units Units ....... (like today, but global) [Publish]
Losses Losses
[Supporting city 1]
Icon Icon
Units Units ....... [Publish]
Losses Losses
[Supporting city 2]
Icon Icon
Units Units ....... [Publish]
Losses Losses
..............................
(Separate Publish icons, sometimes the defender wants to publish minimal details in the alliance forum, because of spying risks)
[Attacking city] (attacking player) is attacking your support in [Supported city] (day, time)
Icon Icon
Units Units ....... (like today, but global) [Publish]
Losses Losses
[Supporting city 1]
Icon Icon
Units Units ....... [Publish]
Losses Losses
[Supporting city 2]
Icon Icon
Units Units ....... [Publish]
Losses Losses
..............................
(Separate Publish icons, sometimes the defender wants to publish minimal details in the alliance forum, because of spying risks)
Balance:
The supporter gets a better view of what happened.
Abuse Prevention:
Not needed
Summary:
Instead of 30*30 useless reports, the supporter gets 30 grouped reports. Assets:
- It will avoid hours of useless browsing
- The supporter gets a better view of what he has sent and what happened to it
- Possible interest for Inno: sending 1 grouped report could make less work for their Internet connection than 30 reports thrown at the same second