Pages: << prev 1 next >>

'Late' CR deployment

*sam* The Salthill Sluggerz Darkwind Guru Renegade Group: Lead Developer Posts: 16,784 Joined: Jan 19, 2006 I have completed and tested the 'late' CR deployment code. Let me know of any bugs etc. Just to remind you how this works: - Up to 10% (total) of the camp's original CR may be deployed late, i.e. deployed to scheduled battles in which you are the incumbent defender. - The CR must be at camp in order to be deployed late - You can choose how much is deployed as Slow and how much as Fast: the normal reductions are applied based on travel speeds of intervening tiles - if the combat had CR capping applied, then the same capping fraction is applied to the late CR as was applied to the whole battle ......................... marshal vet deathrce1 paintladder combat1 wv ped1 cont slay2013 Posted Jun 26, 2020, 10:00 am Last edited Jun 26, 2020, 11:50 am by *sam*

*goat starer* Special Circumstances Darkwind Guru Evan Reds Faction Group: Contributors Posts: 10,908 Joined: Oct 29, 2007 I thought we had agreed the following things: 1. a cap - 10% of CR is huge for someone like us... we could redeploy 1200CR and completely turn a battle on its head. 2. Additional deployment penalties in CR degradation to reflect fast deployment. ......................... vet wv zom pvp4 cont community deathrceL1 marshal pvp3 pvp2 Posted Jun 26, 2020, 11:12 am

*Longo* Longos Merry Men Darkwind Guru Mutants Faction Group: Marshals Posts: 6,682 Joined: Dec 15, 2007 Also this can only be used to defend a hex already owned by you correct, not an attack? And in order to do this, you obviously needed to initially send the minimum 100? As for what goat questioned, 1- I thought we had talked this % down to 10%. I thought the idea was to better allow defenses. I get the number can be large , but if you are being attacked on several fronts, this could be divided amongst several attacks, and with travel degradation, will still make this number lower? We can surely discuss this later today though? 2- I wasn’t aware fast CR deployment changes were discussed ? ......................... vet combatL1 ped1 paintladder semiprocombat ped2 wv pvp4 pvp1 gwped paintball pvp3 pvp5 slay2013 marshal circuit2 combat1 e2g raceL1 gwextrav gateautumn pvp2 triangle1 circuit1 Posted Jun 26, 2020, 11:42 am

*sam* The Salthill Sluggerz Darkwind Guru Renegade Group: Lead Developer Posts: 16,784 Joined: Jan 19, 2006 *goat starer* said: I thought we had agreed the following things: 1. a cap - 10% of CR is huge for someone like us... we could redeploy 1200CR and completely turn a battle on its head. We didn't discuss a per-combat cap. It was 10% overall, shared between whatever combats you want. *goat starer* said: 2. Additional deployment penalties in CR degradation to reflect fast deployment. Hmm, I don't quite recall. This may have been mentioned, yes.  I don't see it in my notes. What's your recollection? ......................... marshal vet deathrce1 paintladder combat1 wv ped1 cont slay2013 Posted Jun 26, 2020, 11:50 am

*sam* The Salthill Sluggerz Darkwind Guru Renegade Group: Lead Developer Posts: 16,784 Joined: Jan 19, 2006 *Longo* said: Also this can only be used to defend a hex already owned by you correct, not an attack? And in order to do this, you obviously needed to initially send the minimum 100? Correct. I've updated that above. *Longo* said: As for what goat questioned, 1- I thought we had talked this % down to 10%. I thought the idea was to better allow defenses. I get the number can be large , but if you are being attacked on several fronts, this could be divided amongst several attacks, and with travel degradation, will still make this number lower? We can surely discuss this later today though? Yes, we can discuss it some more.  10% was the agreed number from the previous meeting, with no per-combat cap. *Longo* said: 2- I wasn’t aware fast CR deployment changes were discussed ? I think he's right that they were mentioned, at least in passing.  I would have written into my notes if anything was agreed, though. ......................... marshal vet deathrce1 paintladder combat1 wv ped1 cont slay2013 Posted Jun 26, 2020, 11:52 am

*goat starer* Special Circumstances Darkwind Guru Evan Reds Faction Group: Contributors Posts: 10,908 Joined: Oct 29, 2007 *sam* said: *goat starer* said: I thought we had agreed the following things: 1. a cap - 10% of CR is huge for someone like us... we could redeploy 1200CR and completely turn a battle on its head. We didn't discuss a per-combat cap. It was 10% overall, shared between whatever combats you want. *goat starer* said: 2. Additional deployment penalties in CR degradation to reflect fast deployment. Hmm, I don't quite recall. This may have been mentioned, yes.  I don't see it in my notes. What's your recollection? my recollection is just that we said it should be a bit more fierce to reflect the rapidity of deployment and to make reserves less attractive than your original CR. But i'm not wedded to the idea. I get Longos point about the cap but it still seems pretty significant that i can deploy such a lot of CR a long way away from camp at short notice... implementing increased degradation at range might resolve that. You have to remember that most 'defences' are actually tit for tat border skirmishes and i cant see much reason why one camp should get any great bonus over another in these. What it will let me do is deploy little CR to a hex i own.. strike ahead of that hex and back up the one i own when i need to. That increases the speed of advance for large camps. and forces the camps they are attacking to be increasingly defensive. maybe a maximum hex range to deploy to? lets see how it plays out and revisit it later. ......................... vet wv zom pvp4 cont community deathrceL1 marshal pvp3 pvp2 Posted Jun 26, 2020, 12:27 pm Last edited Jun 26, 2020, 12:38 pm by *goat starer*

Pages: << prev 1 next >>

Powered by MercuryBoard [v1.1.4]
© 2001-2005 The Mercury Development Team

0.2007 seconds - 16 queries - 125.62 load