| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Ari Chu
Perkone
   |
Posted - 2009.07.25 18:40:00 -
[1]
Corp setting Corp blue costs 1mil initially and 1 additional mil on the first of each month.
Corp setting Alliance bllue costs 10mil initially and 10 additional mil on the first.
Alliance setting Corp blue costs 10mil and 10mil, setting another alliance blue costs 100mil and 100mil.
Not hard to justify since the standing status has to be recorded by Concord as well as the system communications beacons, and the lists have to be updated and maintained. This would have a real impact upon coalitions which would lead to more alliances going NRDS as well as fewer coalitions acting on concert. BOTH results would be very beneficial for 0.0.
The "possible workaround" which alliances would go for is to require all of their pilots to have standings for corps ... so it isn't a 100% way to shrink the size of coalitions, but the added burden of 10k pilots having to each set standings for 100 corps would surely discourage such a tactic on a mass scale.
---
"The Galaxy is only as big as you make it." - presumably Eve Game Designers. |
Valandril
Caldari
Ex-Mortis
|
Posted - 2009.07.25 19:10:00 -
[2]
Edited by: Valandril on 25/07/2009 19:10:32
Great feature ! Implement right away!
/me goes to his cave
Can we have anti-idiot test upon creating account ?
Do not discuss moderation in your signature. Zymurgist |
Bibbleibble
|
Posted - 2009.07.25 20:18:00 -
[3]
 Originally by: Valandril
Edited by: Valandril on 25/07/2009 19:10:32
Great feature ! Implement right away!
/me goes to his cave
Can we have anti-idiot test upon creating account ?
As nice as this might be, it would be pretty bad for the subscription figures.
________________________________________________
For changes to Minmatar Battleships click here (also with a review of the Muninn!) |
Hesod Adee
Dark-Rising
|
Posted - 2009.07.25 21:12:00 -
[4]
Originally by: Ari Chu
Not hard to justify since the standing status has to be recorded by Concord as well as the system communications beacons, and the lists have to be updated and maintained.
Why do you assume that the list is maintained by Concord ?
First of all, why would concord care about the standings between two groups. All they care about is who had permission to attack who, which standings do not give.
Second, here is an alternitive way that the standing lists may be maintained:
- Each corp maintains the standing list on it's own servers somewhere. Possibly at their HQ.
- Each member keeps a copy of that list on their ship.
- When the list is changed, a message is sent out to update the ship lists. This data burst wouldn't use much more bandwidth than someone talking in corp.
- When someone is seen in chat the ships computer looks at each persons corp and alliance, then compares it with the standing list.
- This method has the advantage that a corrupt employee at a communication hub isn't in a position to steal or alter the list.
Quote:
The "possible workaround" which alliances would go for is to require all of their pilots to have standings for corps ... so it isn't a 100% way to shrink the size of coalitions, but the added burden of 10k pilots having to each set standings for 100 corps would surely discourage such a tactic on a mass scale.
Or the coalitions could just merge into one large alliance.
|
Zephyr Mallory
Starfire Oasis
Thalion Syndicate
|
Posted - 2009.07.25 22:48:00 -
[5]
Edited by: Zephyr Mallory on 25/07/2009 22:48:32
Originally by: Ari Chu
Not hard to justify since the standing status has to be recorded by Concord as well as the system communications beacons, and the lists have to be updated and maintained. This would have a real impact upon coalitions which would lead to more alliances going NRDS as well as fewer coalitions acting on concert. BOTH results would be very beneficial for 0.0.
Because we all know, Concord maintains such a strong presence in 0.0, and all 0.0 alliances strictly abide by Concord law.
Salvage Ninjas are Annoying and Lame, but within rights. |
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |