Blitzkrieg I : Generation II

[Mascarenhas2]

It seems sound.

[tedi88]

It looks good as far as I am concerned and it certainly fits the balance of the game, though if you allow me: I disagree with generalisation that SS was elite, some units yes, others not (in fact majority was not).

Btw Major Pain of course been-there-done-that type of soldiers are veterans. What I meant under them is that they have less experience than "old veterans", but somewhat higher moral. Something like difference between combat engineers and elite. However as I said above, I like the system you laid out.

[Major Johnson]

MP, you wrote: Infantry could and did fire against aircraft. Tanks fought back against aircraft. In BK, we must trade off these things because of a code that forces a unit to be either ground attack or air attack. This requires a code change... "

Haven't I seen some AA pieces in the game that fire at both ground and air units?? Which brings me to another anomaly I've encountered. 20 mm AA guns I believe, will not fire on tanks because their ammo cannot pierce it?? I think in the heat of battle no matter what weapon you had you were using it against whatever was attacking you. And even 20 mm ammo would eventually have some sort of effect on armor, no??

[tedi88]

Mar 16, 2015 20:42:46 GMT 1 Major Johnson said:

Haven't I seen some AA pieces in the game that fire at both ground and air units?? Which brings me to another anomaly I've encountered. 20 mm AA guns I believe, will not fire on tanks because their ammo cannot pierce it?? I think in the heat of battle no matter what weapon you had you were using it against whatever was attacking you. And even 20 mm ammo would eventually have some sort of effect on armor, no??

I believe this was done to prevent the aircraft from being too weak. Make no mistake they were weak to begin with, but still....

Precisely, if the gun can't penetrate the armor it won't shoot. However I believe that (someone correct me if i'm wrong) some mods implemented or tried to implement "soft cap". Idea was that 20mm can still fire on the Tiger, and slowly cause damage or knocking out the tank treads. Still this produced very unbalanced results. Like Stuart tank knocking out the Tiger.  

I guess in this case gameplay reasons were more worth then realism. 

However you raised an interesting point. Major Pain would it be possible to introduce tank turret jaming?

[Major Pain]

Thank you for the comments.  Actually I made a mistake on the chart.

You will notice there are two levels of Regular and Veteran Squads.  The Second veteran Squad should be "2" not 1.  So this kind of lines up with what Tedi is saying.  

Green Squad has been in Theater for less than 1 month

Regular Squad 1 has seen limited action, in theater 2-4 months.

Regular Squad 2 has been in combat less between 4-6 months months.

Veteran Squad 1 has been in some Serious Engagements between 6 and 8 months.

Veteran Squad 2 has been in the theater and Combat for over 8 months

Elite Squad has been trained at higher level, comprised with units pulled from Veteran 2 Squads.   At least 1 year in theater.

You can see the Commanders rating is a little better at each level also.

The 2nd Chart Shows how Squad Decay or Decline occurs when Members or Command is lost.  The Moral declines based on all members, but Command still influences the Squad the most.  It is possible that a Commander might survive when all members are lost... and he could reform a new squad.

HQ Commands are also formed into a Squad, each with 100 to 150 Moral Points.  These would not designed for actual Combat Squads.  The idea is they can still defend themselves if the position is overum or provide Command and Moral on the front.

Squad  =  Sgt, Corporal and 7 to 10 Units - This is the Combat Element.

These are the Level Up Command Units (Squads)

Platoon Command = 1st or 2nd Lieutenant, Sgt and 4 SMG. = 6 members

Company Command = Captain, Sgt and 4 SMG = 6 members

Battalion Command = Lt Colonel, Sgt Major and 4 SMG = 6 members

Regimental/Brigade Command = Colonel, Sgt Major and 4 SMG = 6 members

Division Command = Major General, Sgt  Major and 4 SMG. = 6 members

The Combat Squads would benefit from only the HQ Commander, not the Command Squad (All Commanders = 35 points). 

I considered assigning Moral based on the Command level, but this did not work as I predicted, and adds to many command levels to the game.   So to keep it manageable, I made the Commander provide 35 moral points at every level.    Remember, the limit is 200 Moral Points, and it does not matter where the come from.     

It is doubtful that any mapper is going to include all of the Command levels into a map.  But we might find a Major General's HQ along with various Company and Platoon HQ.   Those would add 105 points to whatever the Squad already has.   The total Moral Points available if a 5 of the HQ levels were present is 175.

The theory behind the Moral Points system is to use Moral as the key condition as to the Combat Effectiveness of the Squads.    As long as the Moral stays above about 80, the Squad is combat effective.   As it declines due to casualties, the combat effectiveness starts to decay. This will especially begin to show up if Squads are outside the Zone of Influence of a HQ Commanders.   But as Squads are withdrawn to rebuild, as soon as they enter a HQ Zone of Influence, their Moral begins to increase once more.

Now several issues must be considered.  

1. How much time in a mission is there to actually reform Squads?

2. What are the map Objectives and can you complete mission with under-strength squads?


3. Has the Mapper actually provided a way to reform Squads?  

Remember, Squads can use individual soldiers from other units to reform.    But the question really pertains to whether the Mapper has made it possible for Replacements to come from a Truck or some other mechanism.  My thinking is replacements should not arrive in a truck to the trench or front line.   This is not realistic.   A Squad leader qould not be given fresh troops in this manner... he would draw them in the refit area.  So the best a Squad leader could do would be to absorb other units without a Commander or that are not attached to another Squad or team.   Hence, this is what led to the Option to add members to a Squad, Fill-Out Formation.


So there is much to consider, but I really don't think players will have trouble adjusting.

[Major Pain]

Mar 16, 2015 20:42:46 GMT 1 Major Johnson said:

MP, you wrote: Infantry could and did fire against aircraft. Tanks fought back against aircraft. In BK, we must trade off these things because of a code that forces a unit to be either ground attack or air attack. This requires a code change... "

Haven't I seen some AA pieces in the game that fire at both ground and air units?? Which brings me to another anomaly I've encountered. 20 mm AA guns I believe, will not fire on tanks because their ammo cannot pierce it?? I think in the heat of battle no matter what weapon you had you were using it against whatever was attacking you. And even 20 mm ammo would eventually have some sort of effect on armor, no??

AA Units can certainly attack Ground Units.

But the Units not defined with AA Guns cannot fire on Aircraft.

The issue is in the code.   You can add a .50 cal MG on the top of a Tank Turret, and give it a Ceiling to let it fire on Aircraft and it will work.  But the unit will not stay where you place it.   As soon as enemy Aircraft appear on the map, it starts to move toward it.

There are two Binary Codes in the Command Codes that AA units must have; Install (Code 18) and Uninstall (Code 19).   These two commands cause AA units to Install (set-up) the Platform before it can use the weapons.  The Uninstall occurs when you order the unit to move to a new location.   Once it arrives at any location, it begins the install (set up).

If we give every unit these two commands, then battles are going to be affected.   before a unit can attack, it has to stop, then set up. Combat units that need to the flexibility to move and fire, so clearly this will not work.   So in the new code, Units will have a new Command that allows then to fire on Aircraft once it comes into their range... but it will holds its position.

I hope this answers your question.

[tedi88]

Mar 16, 2015 22:14:47 GMT 1 Major Pain said:

These are the Level Up Command Units (Squads)

Platoon Command = 1st or 2nd Lieutenant, Sgt and 4 SMG. = 6 members

Company Command = Captain, Sgt and 4 SMG = 6 members

Battalion Command = Lt Colonel, Sgt Major and 4 SMG = 6 members

Regimental/Brigade Command = Colonel, Sgt Major and 4 SMG = 6 members

Division Command = Major General, Sgt  Major and 4 SMG. = 6 members

The Combat Squads would benefit from only the HQ Commander, not the Command Squad (All Commanders = 35 points). 

I considered assigning Moral based on the Command level, but this did not work as I predicted, and adds to many command levels to the game.   So to keep it manageable, I made the Commander provide 35 moral points at every level.    Remember, the limit is 200 Moral Points, and it does not matter where the come from.     

It is doubtful that any mapper is going to include all of the Command levels into a map.  But we might find a Major General's HQ along with various Company and Platoon HQ.   Those would add 105 points to whatever the Squad already has.   The total Moral Points available if a 5 of the HQ levels were present is 175.

The theory behind the Moral Points system is to use Moral as the key condition as to the Combat Effectiveness of the Squads.    As long as the Moral stays above about 80, the Squad is combat effective.   As it declines due to casualties, the combat effectiveness starts to decay. This will especially begin to show up if Squads are outside the Zone of Influence of a HQ Commanders.   But as Squads are withdrawn to rebuild, as soon as they enter a HQ Zone of Influence, their Moral begins to increase once more.

Now several issues must be considered.  

1. How much time in a mission is there to actually reform Squads?

2. What are the map Objectives and can you complete mission with under-strength squads?


3. Has the Mapper actually provided a way to reform Squads?  

Remember, Squads can use individual soldiers from other units to reform.    But the question really pertains to whether the Mapper has made it possible for Replacements to come from a Truck or some other mechanism.  My thinking is replacements should not arrive in a truck to the trench or front line.   This is not realistic.   A Squad leader qould not be given fresh troops in this manner... he would draw them in the refit area.  So the best a Squad leader could do would be to absorb other units without a Commander or that are not attached to another Squad or team.   Hence, this is what led to the Option to add members to a Squad, Fill-Out Formation.


So there is much to consider, but I really don't think players will have trouble adjusting.

I agree with the notion that trucks coming to the trenches to replenish loses is un-realistic. I also like the idea of a refit area and the combination of squads. However I would also note the following:

1. It depends on a mapper - yes, but I would add it also depends on a player. Unless we are talking about maps with limited time to complete them, then it's not really a problem. With timed maps, it can become a problem, but nothing that a player can't overcome. Mapper providing player means to resupply - again I agree fully with this statement. 

2. Objective completion - I strongly believe that this is more up to the player than to the mapper. Reason is simple everybody has his way of playing the game and that's normal. It's also normal to try new ways to tackle the objective or the map. For example Stanenberg likes to "break" the script sometimes, so he wouldn't have a problem with this type of changes. Besides, IMHO sometimes it's good to loose in SP. 

Finally MP, would it be possible to actually make warehouses supply men? Something like immobile unit, that has an appearance of a warehouse and a function to replenish squads? I believe this was discussed on BK Portal. Btw I know this would make maps tedious (if we are talking about large maps), but it would be a nice change. 

[Major Pain]

Mar 16, 2015 20:57:37 GMT 1 tedi88 said:

Mar 16, 2015 20:42:46 GMT 1 Major Johnson said:

Haven't I seen some AA pieces in the game that fire at both ground and air units?? Which brings me to another anomaly I've encountered. 20 mm AA guns I believe, will not fire on tanks because their ammo cannot pierce it?? I think in the heat of battle no matter what weapon you had you were using it against whatever was attacking you. And even 20 mm ammo would eventually have some sort of effect on armor, no??

I believe this was done to prevent the aircraft from being too weak. Make no mistake they were weak to begin with, but still....

Precisely, if the gun can't penetrate the armor it won't shoot. However I believe that (someone correct me if i'm wrong) some mods implemented or tried to implement "soft cap". Idea was that 20mm can still fire on the Tiger, and slowly cause damage or knocking out the tank treads. Still this produced very unbalanced results. Like Stuart tank knocking out the Tiger.  

I guess in this case gameplay reasons were more worth then realism. 

However you raised an interesting point. Major Pain would it be possible to introduce tank turret jaming?

I considered Turret Jamming actually.    The problem is getting into another level of the individual model Codes.   When the tracks are damaged, what is going on actually is the Speed and Rotate Values are Flagged to "0" (Zero)...   which means the unit cannot move, simulating the damaged tracks.   This can only happen on units with the "Arm" in their TYPE assignment; Example "arm_medium".

To force a situation to prevent a Turret from rotating would be a bit more difficult... you have to point to one of the "platforms" on the model and Flag two values "0".

Example of Platforms and Gun Relationship on a Tank - (From 1.xml).


In the Model's 1.xml file, there is a section called <Platforms>
.   A Platform is defined as any part that provides a base for other parts of the model.  The first Platform is almost always the wheels, tracks, and body or hull.   This is the base for the rest of the model parts.

The second and additional Platforms are where he weapons or other parts are positioned on the model.   These are also referred to as Platforms because they have the components for the weapons; Turret, GunCarriage and Weapon.  Also included are any other parts that might be a child of the Platform Parent; Gun Armor or Mantlet, Turret Model Parts, etc...

Another purpose that the Platform Section serves is it defines how the Platform can move or rotate.   So this is the area we would have to affect to Jam a Turret.  The two things we must Flag to "0", or in this case "-1" are the VerticalRotateSpeed="-1" HorizontalRotationSpeed="-1" .

To create this code would likely cause all platforms on a model to be affected since it must be subjective...  you simply cannot identify the actual Turret to shut down, so it looks for all statements that show a true condition as to VerticalRotateSpeed (Up and Down) and HorizontalRotationSpeed (Left and Right).  

And not Turrets are a Turret in actual the form of the part that sits on the hull with the gun and crew.  In BK, the Turret is the actual model part that turns.  In my Models, this is usually just a small square or circle part with the Rotate Parameters; -360/+360.  360 represents the Degrees of the Circle in relation to the center axis.  The parts that actually looks like the Turret in my models is usually called the TRT or TRN.   

Here is an Example of the how my Models are created:

Tracks     (Model Parent)
   |
   |- MajorPain Copyright
   |
   |- TRX  (The Track and Wheels parts)
   |
   |- Hull   (The Model HULL    and PLATFORM 1)
   |
   |- Turret_01  (This is the Turret base for Hull MG - this part rotates left/right:  -5/+5 Degrees - PLATFORM 2)
   |        |
   |        |- Gun Carriage_01    (This part provides the elevation/depression:  -5/+20)
   |                      |
   |                      |- MachineGun_01   (The Actual Weapon part)
   |                                  |
   |                                  |- LMachineGun_01   (This is the Weapon Fire Point LOCATOR for Weapon)
   |
   |- Turret_02  (This is the Model's Turret Platform with rotation of -360/+360   - PLATFORM 3)
         |
         |- TRT   (The Turret Part)
         |
         |- Guncarriage_02   (This is the part that provides elevation/depression:  -5/+30)
                    |
                    |- Mantlet_02   (This might include the coaxial MG)
                    |      |
                    |      |- LCoaxialMG_02      (This is the Weapon Fire Point LOCATOR for the MG)         
                    |
                    |- MainGun_02    (This is the Tank Gun)
                              |  
                              |- LCoaxialMG_02    (This is the Weapon Fire Point LOCATOR for the MG)


On the Platforms below, the first one is called HULL since it includes the Tracks, Wheels, Suspension, Axles, and the Hull.

The Second Platform on this Model is the Tank Turret

The Third Platform is the Auxiliary or Hull MG

<Platforms>

<item VerticalRotateSpeed="10" HorizontalRotationSpeed="60" ModelPart="3" GunCarriageParts="-1" FirstGun="0" NumGuns="0"><Constraint Min="0" Max="0"/><ConstraintVertical Min="0" Max="0"/></item>

<item VerticalRotateSpeed="0" HorizontalRotationSpeed="3.96" ModelPart="8" GunCarriageParts="-244" FirstGun="0" NumGuns="2"><Constraint Min="-6.28319" Max="6.28319"/><ConstraintVertical Min="-0.0872665" Max="0.261799"/></item>

<item VerticalRotateSpeed="1" HorizontalRotationSpeed="2" ModelPart="4" GunCarriageParts="-249" FirstGun="2" NumGuns="1"><Constraint Min="-0.942478" Max="2.00713"/><ConstraintVertical Min="-0.174533" Max="0.174533"/></item>

</Platforms>



The Gun Section of the 1.xml actually defines the Weapon parameters:  Weapon, Ammo, Shoot Point Locator #, and Recoil Distance (If it does).   You can see the Main Gun is the 40mm_2pdr_oqf in the first Weapon reference.


<Guns>

<item Priority="0" Ammo="130" Direction="49151" ReloadCost="1" ShootPoint="28" Recoil="1" RecoilLength="4.86472" RecoilTime="50" ModelPart="14" RecoilShakeTime="400" RecoilShakeAngle="0.0523599"><Weapon>40mm_2pdr_oqf</Weapon></item>

<item Priority="1" Ammo="5000" Direction="65534" ReloadCost="1" ShootPoint="27" Recoil="0" RecoilLength="0" RecoilTime="50" ModelPart="13" RecoilShakeTime="400" RecoilShakeAngle="0.0523599"><Weapon>7_92mm_besa</Weapon></item>

<item Priority="1" Ammo="5000" Direction="65534" ReloadCost="1" ShootPoint="26" Recoil="0" RecoilLength="0" RecoilTime="50" ModelPart="10" RecoilShakeTime="500" RecoilShakeAngle="0"><Weapon>7_92mm_besa</Weapon></item>

</Guns>



To answer the question... At this time I have to pass on the Turret Jamming.   I don't believe the the code required would simulate a correct result.

[tedi88]

Hm, pity. I hoped that could be implemented (no offense meant). Still disabling tank treads will have to do.

Thanks for such detailed answer.

[Major Pain]

Mar 16, 2015 22:54:39 GMT 1 tedi88 said:

I agree with the notion that trucks coming to the trenches to replenish loses is un-realistic. I also like the idea of a refit area and the combination of squads. However I would also note the following:

**


**

Finally MP, would it be possible to actually make warehouses supply men? Something like immobile unit, that has an appearance of a warehouse and a function to replenish squads? I believe this was discussed on BK Portal. Btw I know this would make maps tedious (if we are talking about large maps), but it would be a nice change. 

I'm kind of leaning toward a Staging Area or Refit Area of some kind.   I'm not thinking a Warehouse, but rather something like a Command Post or Recruit Center.  The problem will be getting Players Informed about what it is... so I'm going to have to provide a Manual that discusses the Changes and Updates.

In an earlier Post I was discussing the number Command Binary Codes.  I told you all that there were 64 possible Binary Codes in the * Octals:  Each Octal can store 8 values, and there are 8 Octals; 8 x 8 = 64.   

39 Binary Commands are Documented and Defined
5 Binary Commands are dedicated to AirCraft
7 Secret or Undocumented Codes used for various other things.

So 51 of the Codes are already in use.

I had planned to change the Binary Command Table around to move some of the Commands to a different Table, basically another Binary Octal Group.   Aircraft Commands could be moved out of the Command Binary for instance.   The other 7 I'm not sure of yet.   But at the moment i have 15 NEW Commands Planned, but not enough room to add of all them.  That puts me 2 over the maximum.   So unless i remove a couple, I have to rethink on this.   I could redefine a couple of Codes that are rarely used, or perhaps eliminate a couple that are never used to get to where i need to be.

Anyway, I have tested 7 Command Codes that are working very well.   Another three of the Current Codes have been Refined Slightly and received a new name; but the purpose remains mostly the same.   I changed some Button Graphics to bring some into the GEN II World.   Most of the new Commands and changes pertain to Infantry.


Here is a image of the Mission_Button.dds File that replaces the original.



Zoom in a little...




And here are the new Command Buttons...



Here is a description of the Buttons:

A)  Medic Truck (Heal):   Start Healing Soldiers.   This works like the Resupply Command.  Medic Teams not assigned to Trucks automatically start to heal.


B)  Reform Squad:   A Squad Leader can Reform/Rebuild his Squad by receiving new members.  At the moment, I am using a Vehicle (Truck) with the Resupply Human Command to rebuild the Squads... but I'm likely to remove this from the TRN Class and change this to a Static Building or Object... (Discussed above).


C)  Dig-In:   This only applies to Infantry.   This works like the Engineer Build Trench, but does not require Resources.   Only a Squad Leader can Order this Command.  The Assistant Squad Leader or other Up-Level Commanders do not have this option.   In order to maintain continuity, the Command has to Stay within the Squad Structure.   It can be used by Some Teams, based on the Structure and Leader.   The Command comes to the Squad with the Squad Leader Code.   Another form that this might permit is to allow Soldiers to look for natural cover rather than digging.


D)  Detach from Unit:   The Crew can 'Detach' or leave the Gun or Vehicle he is assigned to.   This applies to the entire crew, and leave the Host Unit Neutral.   This functions on Artillery, Mortars, HMG, Trucks, SMG and Tanks.  This Code change was particularly difficult to change... based on the Neutral Artillery Gun Code, but applied to all 3-D Models.  The next Logical Step to make this a clean sweep is to add a crew to the Trains and Aircraft.     The name might be changed to DETACH CREW, since it is Selected from the vehicle or gun.

I have tested Aircraft Crews but I have had difficulty grabbing control from the AI Code.   I do have a new EFFECT that is in testing... where the Pilot parachutes from his plane...  but this is the only form of Detach that seems to work.   I have not applied it to the crew size yet, as in Bombers.    The Code runs through a Random Function to determine if the Pilot Survives; a 50/50 chance.   If the Flag is True, he jumps... False- he goes down with the plane.

Some time back I discussed how Crews could be Detached from their Vehicle.   This is an especially neat Command, since if the Crew leaves the vehicle, the Vehicle becomes Neutral.   However, it cannot be Captured by the enemy unless there are no Units from the Owner Forces within a Defined Radius of the Vehicle and Enemy units.  The Radius table has not been worked out yet... I am testing a couple of different factors before I do this.    I'm thinking the Radius has to be based on the MAP Size...   Smaller maps pull this Radius in, where larger maps will mostly remain at a Constant if the MAP is larger than 15 x 15.  

Ok...  here is an overriding factor about the vehicle crews.   Whatever you define as the Crew Size in the 1.xml is what the crew will be.   So if you define a 2 for a tank, that is what you get.  When you try to repopulate the tank, only two will climb in.  I mention this because improper Crew Sizes can Screw you up.

While I was looking for a way to program the Detach Command, I found the Function in the Master Code.   It is used to Detach a crew from a gun that has been destroyed.     All I had to do was bring it to the Binary Table and link it to the new Code.    The function is likely the same as used in Desert Law, but I have not checked that Code.  

I need to add that you cannot populate a Vehicle with a partial crew...  it requires the whole crew to move the unit or for it to function.

If a Vehicle begins to take damage under fire, the Crew will try to Detach automatically.   At a predefined HP, the Code runs through a Random Function to determine the Survival Status of the crew.      The Flag will return a number between ZERO and the Number of Members in the Crew.   If the Flag returns a Zero, then the whole Crew is dead.  Any other number is how many crewman will detach.   During Battle, the Player will have to pay attention to Crews detaching so they can be moved to safety.


E) Attack Aircraft:   This solves the wandering units that follow planes.   Units will only fire at Aircraft under two conditions:   The Unit has a MG or other Weapon capable of AA Attack, and The Aircraft comes into the Unit's Field of Sight and Weapon Range.  The Unit will not reposition to facilitate a better aim.  Turrets will move on Tanks.    To Apply a AA capable MG, the weapon must have a Ceiling Value of at least 500 and not more than 1200.  

While this Command uses the same Code as AA Units, the Install/Uninstall Commands are not included.   When the weapon fires at Aircraft, another code is activated to force the unit to activate a Modified 'Stand Ground' Command (HOLD POSITION) until the Plane is out of range.  The 'Hold Position' command does not appear in the Binary Octals... it is an Auto-Command which runs in the same environment as units that automatically attack enemy units within sight.   The Attack Aircraft Command must be Included in the 1.xml Binary File and the Player must press/select the Command on the Console.  So the Command itself is not an Auto-Command.

One of the issues that made this a two-phase Command was caused by the Chase Plane condition.  Ground Units do not detect Aircraft correctly... Aircraft are detected anywhere on the map.   So there is an issue with the perceived Sight of Ground Units.   I'm looking for a way to make that code less sensitive, but I'm sure the NIVAL ran into the same issue and added the Install/Uninstall Commands to solve it.   Well it really does not solve it, for that purpose.   I'm kind of thinking that AA Units are granted a method of warning, like radar to alert them of aircraft on the map.   That is the only thing that i can think of that might explain the 'Chase Plane' issue.    

This is still in testing, mostly based on Ceiling Ranges and Weapon parameters.


F)  Create Squad:   This replaces Form Formation.   I do not understand why the code writers used this phrase as the Command Name. It has never made sense.   While a Squad does use Formations, a Squad in itself is not a Formation.   What is interesting is the Code Writers actually use the Create Squad in the Command Table, but it crosslinks to Form Formation in the Look-up Index.   This does not work the same way as Reform Squad.   A Reformed Squad can have a number of members already in it.   A Created Squad starts with the Squad Leader only.


G)  Disband Squad:   The reverse of above...   All of the Squads members are detached from the Squad Leader.  Same situation as above...  the Command Table uses 'Disband Squad' but the Crosslink has Disband Formation.

The Purpose the two Changes above is to clarify the Commands.


H)  Add To Squad:   If the Squad Leader needs more soldiers or the Player wants to assign single Soldiers to a Squad, this Command Collects any Individual Soldiers within the Sight Area of the Squad and adds them to the Squad.   I was actually going to call this Compliment Squad, but the phrase was too long for the preset number of Characters.

The maximum number of Squad Members is limited to 14 at the moment.   One issue that I ran into is a conflict with the Squads original 1.xml file and its defined Formations.   If the number of members is below or equal to the maximum defined in the 1.xml file... then the Squad uses its own Formation data.  

But...  and this is a big but...   if the Squad exceeds the defined number of members, a Default Code is used to define the Squad Formations based on its number of members.  WARNING:  It may not provide the best Formation Options for that Squad.  

Example:  A Squad is defined as having 10 members.   The Player adds one more members to a full Squad.   The Squad can no longer access it's own 1.xml file data, and a default code is used that defines Formations for a 11-man Squad.   This can be problematic for Squads that have Scouts in the wrong place, or Leaders on the Front line.  

So if you expand a Squad, test it as soon as possible.  If you do not like what you see...  Disband the Squad, then Create a Squad.  The Leader will only collect the correct number of members with their weapons.

A What If?    Let's think a little deeper about this, and testing revealed this.   If you have reconstituted a Squad from several individual Soldiers who were not original members of the Squad... the members retain their original weapons.   The original Squad 1.xml is used as much as possible, unless there is a higher number of a soldier definition...    then the default 1.xml code is again inserted.

Example:   A Squad requires 4 Rifleman, but the Squad now has 5 from one that was picked up.   Since the original 1.xml cannot define a 5th Rifleman in the Formations, the default 1.xml code is used.   The default 1.xml calls for Undefined_Soldier in each members slot and it makes no attempt to re-sort the order or determine which is the Squad leader.  This only applies to the Formations and not the Squads ability to perform its Functions.  This can locate the members into very poor Formations.   I am trying to improve this code but this might be the best option.   

An Option:  If the Squad is about to withdraw for a Re-fit/Rebuild, the Leader can Disband his Squad, then Create a new Squad.    The Squad will reform with original members only.  Then the Leader can Re-from the Squad if there is an Area where new troops are Staged.    The Squad will only add the required/defined Soldiers with weapons.     At this point, the Squad is back to its original Status.


I)  Suppressive Fire:  This only applies to Light and Heavy Machine Guns.   The Gunners lay down Suppressive Fire into an area, rather than directly at targets.   It is possible that 1 in 10 rounds will hit a target once if it is a soldier.   The ratio is reduced on larger targets based on the size.   The size is based on the targets AABB Size... which is the invisible screen around the model.    Dispersion in this mode is around 12, so accuracy is very poor.   This works pretty much like the Bombard Code that Artillery uses.  Both are called Indirect Fire in some cases.   You cannot necessarily see the target, so you are hoping to hit it.


J)  Recover Vehicle:   This is my favorite.   This only applies to a new Vehicle Type, the ARV or Armored Recovery Vehicle.   The way this works is you Select the ARV, then Right Click on the Disabled Vehicle, and the ARV moves to the Disabled vehicle and Hooks on so it can be towed.    The Player must still move the ARV where he wants it to go.   Once the ARV has arrived at the specified location, you simply Unhook the Disabled Vehicle just like you would a Gun.   Then the Engineers can go to work.

One Note about ARVs.   They do not resupply or carry soldiers.  They only have two Commands, Hook and Unhook.    The Unhook Button has not been finished yet.. I'm borrowing the Artillery Code in testing... but it looks for Gunners.  So there will be an Update on this.



And now a image of the Command Calculator so you can see where the New Commands are placed into the Binary Octals.   There are going to be some new and very strange Code Definitions in the Future.



The Commands in Red are the New Commands.

The Commands in Light Orange are Re-defined Commands

The Commands in Medium Blue are Aircraft Commands - are not accessible in the 1.xml Binary Codes.


Image Shows the New and Redefined Commands Activated.


More to Come...

[Herr Kodax]

This is so amazing, multiplayer can be so much nore fun to play with the right changes, since there will be so much more stuff to think about/tinker with. Pure awesomesause awaiting.

On the single player aspect now, it may be even easier to take advantage of the AI I speculate. I'm not much of a scripter, but can only imagine. Will there be a 

-if morale < x
  -then GTFO

Or will we be able to abuse the AI by taking out the chain of command only, then mopping the floor with the stragglers?

Sorry to be the bummer again here, but, man, so many questions...

[Major Pain]

You raise an interesting question.

But I am already way ahead of you.    The short answer is "YES", the Player could 'TRY' to take advantage of the AI, but I'm looking at preventing that.


Remember, one of my goals is to not just a make the game better, but also make the AI much smarter.   So there will be a couple of codes that look at Player Actions and Behavior.

If the AI determines the Player is deliberately trying to take out the Command with extra-ordinary effort...   it will make some adjustments.  I will not disclose exactly what at this time, because some of this has not been worked out.  But you can bet it includes everything that the AI can do, like a launching a huge counterstrike or moving units around.  At the same time, the AI is going to exploit the same tactic.  So Players should be aware of this and be ready to adjust.   

What is good for the Goose.... is good for the Gander.    No, I was not calling Players a Goose.  I would not dare...

Something else the AI will do on its own as a matter of Business... is protect the Command Structure.   Its own Moral is on the table as well.  So the AI will analyze the Command Structure and look at where Strong versus Weak units are.   Strong units will be moved to the forward positions or Objectives if they are not properly located.  Weak units will be strengthened, including adding a Command Level or withdrawing the unit until it has enough moral to be Strong.  Remember:  Strong = 100 Moral Points.  The AI will reconstitute Squads, exactly the same Commands are available.

This will present mappers with some tough issues at times.  He must think a little differently about these issues.

One hint:   The AI will be able to detect sounds.... yes it will hear your units.   This is fair since the Player can hear the AI units.   Come on... you know I telling you the truth.  

Despite the Fog of War, you can hear Armor and Trucks moving just beyond your sight.    These are referred to as Ambient Noise or Sounds.  Just like the buildings that include a Ambient Sound File... Units have their Sound Files.   These Sound Files produce a sound a defined area around each unit based on the Sound File and Type of Unit.  So a unit that is outside of your sight, produces only Ambient Noise.

If you move around on a map, you can quickly determine where the AI has units moving, because of their Ambient Sounds.   I'm attaching the Fog of War to this Sound and tightening the radius or proximity to the Player's Units.  So those little hints will be gone forever...   The AI on the other hand will be able to hear the Player's units in the same Radius from his own units. 

So this is an equalizing thing...   No more Player advantages whenever possible.   

So why is this important?   Do you really have to ask that question?

Obviously, if a Tiger Tank can hear your tanks moving into his hearing range, he is tipped off that something is going on.  The AI will then run through a couple of options:

1) Dig In and get ready for contact.  That is a good idea...

2) Withdraw for fear of superior force....   Chicken!

3) Go out and welcome them to the Battle that is about to begin.    Uh-oh...   

Another thing may or may not happen...

4)  Call for additional Units to come to the location.    This could be real bad... 

 ...And it could turn into a Counter-Attack of Significant Size.

So this is a new Tactic and set of Rules for the AI.   The AI Rules of engagement will also be Adjusted... it will no longer attack a Superior Force unless it has other Units moving in for back-up.   Once the AI determines the Player has a significant advantage, it will withdraw or call in whatever units it has within a Radius or Area of Command.  It will not make it easy for you to walk all over it.

So again, the Mapper needs to base battles on some benchmarks and conditions.     Balance will be a larger factor than before.  

About Balance:   Balance does not mean how many Player and AI units are on the map.  Balance means how many Units from both sides are likely to engage in a battle.   Certainly, lopsided battles did occur.   Armies did strike with overwhelming force.   That situation is fine... and should be applied based on historical events, or perhaps fiction if the Objectives are still not a cakewalk.


** 

End Discussion:   You guys need to continue to ask these questions.   It is quite possible that I have not thought about everything.   So this is very important for this project.  

It just so happened that I was waiting for someone to propose the Situation that Herr Kodax brought up.   If you read back into the previous Posts, you will find some of this has been discussed before, but conclusions may not have been made about the code or solutions.



Final Comment:  While I was reading some code earlier this morning, I ran across something that caught my attention.   We all know that NIVAL disabled the Moral Function in BK 1.   Well they only Disabled one section of code to accomplish this; basically about 3 lines.  This is the Missing Link!.   I need to look this over more to see where it connects and calls the functions, but now I think I can locate the issues they ran into.   I had thought that some of the Code had actually been removed, but it appears that was not the case.  The Moral Code and References are all over the place... they didn't even remove the Moral Icons and Binaries.   If you look hard, you can see a lot of them in the Graphics and Open Codes.   The Buried Code is a different Story of course...  

Would it surprise anyone to know that about half of the game engine code is written in LUA?  All of the Menu and Options Code is written in LUA and XML.    

I thought I should mention it.


More to Come...

[Mascarenhas2]

[Herr Kodax]

Daaaamn, what a fine afulfilling answer Major. Can't even begin to imagine what you are up to.

I just wish I could be of some help, but I have no idea what you are fiddling with.

[tedi88]

Mar 17, 2015 12:15:15 GMT 1 Herr Kodax said:

This is so amazing, multiplayer can be so much nore fun to play with the right changes, since there will be so much more stuff to think about/tinker with. Pure awesomesause awaiting.

On the single player aspect now, it may be even easier to take advantage of the AI I speculate. I'm not much of a scripter, but can only imagine. Will there be a 

-if morale < x
  -then GTFO

Or will we be able to abuse the AI by taking out the chain of command only, then mopping the floor with the stragglers?

Sorry to be the bummer again here, but, man, so many questions...

Actually if moral is implemented it will make life easier for some mappers despite requiring more balance.  

Major can confirm issue I had, when I tried to script a flexible withdraw function as opposed to fixed fixed one. 

All in all nice changes and ideas Major Pain.