Because of testing the simplest bare bones ALiVE mission I've so far had to restart the dedicated server/mission multiple times (about 8 or 9 times). While doing this restart cycle I've noticed that ALiVE too often "forgets" that there actually is force pool declared in the military logistics module and available for the mission.

First ALiVE checks what there is set for the mission

10:36:19 ALiVE [m_12|190] Module ALiVE_mil_logistics INIT
10:36:19 ----------------------------------------------------------------------------------------
10:36:19 ALIVE ML - Init
10:36:19 ALIVE ML - Type: DYNAMIC
10:36:19 ALIVE ML - Force pool type: 50 limit: FIXED
10:36:19 ALIVE ML - Allow infantry requests: true
10:36:19 ALIVE ML - Allow mechanised requests: true
10:36:19 ALIVE ML - Allow motorised requests: true
10:36:19 ALIVE ML - Allow armour requests: false
10:36:19 ALIVE ML - Allow heli requests: false
10:36:19 ALIVE ML - Allow plane requests: false
10:36:19 ----------------------------------------------------------------------------------------
10:36:19 ALIVE ML - Startup
10:36:19 ALIVE ML - Startup completed
10:36:19 ----------------------------------------------------------------------------------------
10:36:19 ALiVE [m_13|190] Module ALiVE_mil_logistics INIT
10:36:19 ----------------------------------------------------------------------------------------
10:36:19 ALIVE ML - Init
10:36:19 ALIVE ML - Type: DYNAMIC
10:36:19 ALIVE ML - Force pool type: 50 limit: FIXED
10:36:19 ALIVE ML - Allow infantry requests: true
10:36:19 ALIVE ML - Allow mechanised requests: true
10:36:19 ALIVE ML - Allow motorised requests: true
10:36:19 ALIVE ML - Allow armour requests: false
10:36:19 ALIVE ML - Allow heli requests: false
10:36:19 ALIVE ML - Allow plane requests: false
10:36:19 ----------------------------------------------------------------------------------------
10:36:19 ALIVE ML - Startup
10:36:19 ALIVE ML - Startup completed

and then TOO OFTEN gives this

10:36:38 ML Global register module: module_0
10:36:38 ML Global register module: module_0
10:36:38 ML Global force pool updated:
10:36:38  ------------------ Inspecting Hash --------------------
10:36:38    k [0]: OPF_F v: 0
10:36:38    k [1]: IND_F v: 50
10:36:38  ------------------ Inspection Complete --------------------
10:36:38 ML Global force pool updated:
10:36:38  ------------------ Inspecting Hash --------------------
10:36:38    k [0]: OPF_F v: 0
10:36:38    k [1]: IND_F v: 50
10:36:38  ------------------ Inspection Complete --------------------
10:36:38 ALiVE [m_12|190] Module ALiVE_mil_logistics INIT COMPLETE TIME:  19.332
10:36:38 ALiVE [m_13|190] Module ALiVE_mil_logistics INIT COMPLETE TIME:  18.443
10:36:38 ALIVE ML - Monitoring loop started
10:36:38 ALIVE ML - Monitoring loop started

so during the hash inspect it tells us that all of a sudden there is no (in this case) starting force pool for OFP and neither the players nor OPCOM is able to draw groups from the pool.

As a dedicated server provider when starting/restarting the mission you can never tell if every faction has the set amount of force pool available right from the start. Unless of course that server provider connects to the game and tests all available factions and if it's possible to receive assets from the global force pool..

I took notes of the occurrences when I was testing for the Losing control of grouped AI as per your request.

I had to restart the mission 8 times because of either faction not getting force pool, or if the faction I was testing with happened to get a force pool there was other things that messed up the testing so badly that I had to restart the mission:

• 2 tests in a row, no force pool for OPF_F
• 1 test, no force pool for IND_F
• 1 test, force pool available for both factions
• 2 tests in a row, no force pool for OPF_F
• 2 tests, force pool available for both factions

so 5 out of 8 mission starts there was no force pool available for one faction forcing the mission to be restarted again.