Expand IsInfra Functionality
-
@redrum The other half of the equation is how something like a "munition" is handled when it is on defense.
Currently if you try to use a munition and set it up as a "suicide" unit... it will die immediately after the territory is attacked... so there is nothing to stop a player from attacking your position with 1 INF and destroying all the munitions you have in the territory. Even though you potentially did not need to use any of your "Heavy Guns" to repulse an attack... thus depriving you of having any ammunition on your turn to launch an attack.
I realize this may warrant its own issue. Just wanted to get it down while it was rattling around my spacious noggin.
-
@Hepps Yeah, its related so we can track it here for now. My thought is making a attribute to allow units to be regular units on attack but IsInfra on defense ('isMunition' or 'isInfraForDefense'). Might also need an attribute for 'IsSuicideForAttack' so that they are only exploding when attacking.
That would drive at the following behavior for munition type units:
- Are suicide units on attack with 1 HP so they can attack alone without other units
- Don't do anything on defense. Act as IsInfra (factory, etc) and would be captured/destroyed if territory was captured.
-
@redrum But a munition should really be "suicidal" on both attack and defense... the real issue is that a defender should have the ability to decide whether they are going to be part of the battle or not.
If you really look at the way @CrazyG has his Hvy Artillery set up it is actually a very inconsistent model (though I give him total props for making it work as well as it does).
The Hvy Art cannot participate in attacks... ergo the ammunition is the actual "weapon" however on defense the unit somehow can defend at 5 for all rounds of combat. So if you really think about it... the ammunition for the Hvy Artillery IS the weapon. Now if we are saying that it the unit can only be used for a limited ammount of time during an engagement on the offensive... would it not mean the same should be true while on the defensive? IE. You could unleash your heavy guns at the beginning of a defensive fight as the enemy initially comes towards you... but once in close quarters you could not utilize them for fear of hitting your own troops.
Right now what we have is a system where a unit designed to use munitions is (subjectively by design) omnipotent on defense during normal combat and limited use on offense.
Wouldn't it make more sense if "what is good for the goose is good for the gander"? Or should I say would it not make more sense to include that option in the design rather than pigeon toeing designers into a very limited spectrum of options?
"A joyous heart sours with the burden of expectation"
Hepster -
@Hepps I can see what you are thinking and that is another alternative. You are treating the Hvy Art as more of just a barrage generation/firing unit and it wouldn't really have any combat value itself.
I guess for Hvy Artillery on CG WW1, I was thinking that the barrage unit represented more of a long range bombard type attack (kind of like battleship bombard) and its attack/defense is used if directly in the battle (again like a battleship works). So its barrage unit wouldn't ever be used on defense if you take that approach. It treats the Hvy Art as more of the actual unit with att/def values and the barrage unit as more of a special ability.
I think you could argue for either system and not sure which most map makers and players would prefer.
One other thing I'd add is another approach is having the 'munition' or barrage unit in this case not generate until the start of the unit owners turn rather than the end of their turn. This ends up with pretty similar functionality as the approach I described but then you don't even need to worry about the barrage unit on defense at all.
-
@redrum Yes and I agree that a mixed system could also be used but that omitting the flexibility while tackling the issue might not be the ideal approach. That is, if you are already building increased flexibility into the system... would it not be better to create broader possibilities while you already have your dirty little fingers in the dirty little pie of code?
-
@Hepps said in Expand IsInfra Functionality:
If you really look at the way @CrazyG has his Hvy Artillery set up it is actually a very inconsistent model (though I give him total props for making it work as well as it does).
Just FYI, I totally copied this from Frostion's Age of Tribes.
And heavy artillery operates without problems if you move the end of turn phase to the start of the turn, which I plan to do.
-
@CrazyG So this eliminates the one unit suicide strike destroying the stockpile?
-
@prastle
Correct. -
One of the current effects of IsInfra that I really don't like is the swing. If you add cannons as an isInfra unit, you do end up with extremely swingy situations. If I get this hit kill the last infantry, I the kill 5 or 6 units for free. Now, swings have a role, but if they are too common, its bad.
So I'm going to put out something I'd like to see. I want a unit with the current isInfra status, where it cannot be chosen as a casualty. But I don't want it to be captured, ever. Not when attacking, not when defending.
So what happens if all the normal combat units (the units with hitpoints) die? You should put the newer hits on those isInfra cannons.
Situation 1 (1 round of combat)
I roll 4 hits. My opponent has 3 infantry, 3 cannons.
I should kill the 3 inf, then 1 cannon.Situation 2 (2 rounds of combat)
Round 1
I roll 3 hits. My opponent has 3 infantry, 3 cannons.
His 3 infantry die.
Round 2
I roll 2 hits. I kill 2 cannons.Situation 3
Round 1
I roll 4 units. My opponent has 3 infantry, 1 light cannon, 1 medium cannon, 1 heavy cannon.
First, my opponent's infantry are dieing. Those leftover hits, the defender would decide which of his cannons die. -
@CrazyG What is the point of making them Infrastructure in the first place if you are going to make them be taken as casualties during battle? What am I missing from this?
-
@Hepps
Well to start, infrastructure is a confusing term.There are a lot of reasons a person might want a unit to not be able to be taken as a casualty. TWW's air transports is one example. We want that unit to not be selectable as a casualty, but that doesn't mean its captured.
Here is a theoretical situation. I attack a territory with 2 air transports, 2 paratroopers. You defend with 3 infantry. Let's look at two situations.
Situation A
You get lucky, you score 3 hits. What should I lose? 2 paratroopers is obvious, but what about that 3rd hit? I think I should lose an air transport too.Situation B
You score 2 hits. I lose 2 paratroopers. What should happen to the air transports? Are they captured by the enemy, or destroyed?Another case would be if I attack a territory but cannot capture it. Let's say I have 100 fighters, I attack a space with 1 infantry, and 1 cannon (the cannon without hitpoints from before).
I actually can't kill your artillery if its infrasture. If we change this situation so that you have 10 artillery, I would have to sacrifice a ton of planes just to get that one infantry.
-
@CrazyG I think what you are getting at is 'enforced' or 'required' casualty selection ordering. Essentially having some way to say these unit types must die first or last or somewhere in between. You could even take this to the extremes and have a set casualty selection order so that the defender never has any input into their casualty selection (and even attacker for that matter). An example would be for say revised that the 'enforced' OOL is inf, art, tank, fighter, bomber. This would eliminate the funkiness around players trying to decide whether to take say their bombers as early casualties in a large, close battle. There is also the concept of just full/partial random casualty selection where the player would have no casualty selection input at all the casualties are determined randomly (this is already an available property for targeted attacks).
That concept has been discussed before and is something that could be potentially added. Though its somewhat tangential to how IsInfra works. IsInfra currently essentially indicates a unit has 0 HP and can be either captured/destroyed.
-
@redrum said in Expand IsInfra Functionality:
That concept has been discussed before and is something that could be potentially added. Though its somewhat tangential to how IsInfra works. IsInfra currently essentially indicates a unit has 0 HP and can be either captured/destroyed.
I see that.
But just to consider for isInfra and ideas like air units that have it. Fighters will be able to attack anything they want for free if the capturing behavior is changed.
So the answer is yes to question #3
-
@CrazyG Good point. Which is why I generally lean towards even air infra units being captured/destroyed if they are the only ones left. I believe that avoids being able to say have 1 fighter that has HP and 100 bombers that are IsInfra then flying that stack around to essentially strafe large unit stacks while only losing 1 fighter. Ends up being a very similar problem to having lots of multi-HP units that heal every turn which can just strafe with their extra HP.
And yeah, I don't really see any downside of allowing targeted attacks to target IsInfra units.
-
-
I've done some brainstorming, and I'm confident that allowing isInfra units to be targeted by targeted attacks is the most useful feature suggested so far. This ought to be the priority for this thread. I could immediately use it for something, the idea of a map that uses only targeted attacks would really benefit from this feature.
On attacking isInfra units being captured/destroyed or retreating, there are cases for both making sense (tribes wants them to be captured, HoH wants them to retreat). So would it be possible to make a global property that determines this?
-
I've also noticed that if a unit is isInfrastructure, it cannot have an targeted attack. You won't get an error, the targeted attack just won't fire.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login