Maintenance for the week of December 23:
· [COMPLETE] NA megaservers for maintenance – December 23, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
· [COMPLETE] EU megaservers for maintenance – December 23, 9:00 UTC (4:00AM EST) - 14:00 UTC (9:00AM EST)
· [COMPLETE] NA megaservers for maintenance – December 23, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
· [COMPLETE] EU megaservers for maintenance – December 23, 9:00 UTC (4:00AM EST) - 14:00 UTC (9:00AM EST)
Repair Kits [suggestion]
Solariken
✭✭✭✭✭
✭✭✭✭
✭✭✭✭
Buying and using keep repair kits is pretty tedious. I'm sure we all hate clicking the button 20+ times to get a wall to full health. I propose making the following change to all repair kits used in AvA: make it a channeled ability which would
1. consume only one repair kit per "cast"
2. continue to channel until the wall is at full health
3. provide incremental AP ticks as wall health is restored
4. be interrupted when the player is attacked
Of course if this were implemented, the cost of repair kits should be increased significantly. I also believe this may help improve Cyrodiil performance as it would greatly decrease the number of client input/commands received by the server.
Thoughts?
1. consume only one repair kit per "cast"
2. continue to channel until the wall is at full health
3. provide incremental AP ticks as wall health is restored
4. be interrupted when the player is attacked
Of course if this were implemented, the cost of repair kits should be increased significantly. I also believe this may help improve Cyrodiil performance as it would greatly decrease the number of client input/commands received by the server.
Thoughts?
0
-
chevalierknight✭✭✭I guess its done one at a time to help server load think if 10+ people started doing at as you said. keeping up with when the wall is being damaged sounds like a lag bug festEdited by chevalierknight on 18 July 2015 04:310 -
cjthibs✭✭✭✭✭
✭I actually don't think it would decrease the amount of client/server communications. And that it would make this difficult to track server-side.
If you have a one-time transaction that is a much simpler transaction than an ongoing channeled, tick every few seconds thing. Especially if 10 people are performing the same thing at once.
Also, I'm not sure why this would need to cost more.0 -
chevalierknight✭✭✭I actually don't think it would decrease the amount of client/server communications. And that it would make this difficult to track server-side.
If you have a one-time transaction that is a much simpler transaction than an ongoing channeled, tick every few seconds thing. Especially if 10 people are performing the same thing at once.
Also, I'm not sure why this would need to cost more.
He put it better lol0