Hey and thank you for the suggestion. I put the lines into init.sqf and fired up a mission. When I clicked on the "Enable Auto Generated tasks" I was shown the following error message:

So, heh.. certainly adding the lines into init.sqf disable the ability to create autogenerated tasks but there seems to be a slight downside.

Hey,

I've recently and actually for quite some time now been creating an Occupation vs Occupation scenario and from what experience I've been gathering one of the top nuisances is that the OPCOM(s) always "push all-in" leaving their initial occupied objectives be manned with a skeleton crew (basically leaving only one profile per objective). I have to say that I don't understand how the whole OPCOM process of attacking and defending works but how I understand reading from the ALiVE wiki that's not how (I at least) expect occupation mode to work.
You think what you're experiencing could have something to do with that?

How big is the map of Diyala? I've been using Iron Front's Staszow to do full scale occupation vs occupation scenario and there's still many profiles left after the first ½h of playing and more will come as reinforcements when setting the resupply rate to constant (or wasn't that what you were looking for? In that case I have to apologize for the misunderstanding).

Just tested: indeed if one wants to make the player to be the first soldier in the group one needs to make the AI soldiers to join the players group one by one via the Personnel screen. Not the most convenient way to achieve what needs to be achieved.

The thing is that with the mission I'm currently designing I can't just give a commanders tablet to every player* since it completely diminishes the need to have a human player acting as high command for the soldiers on the ground and diminishes the need for doing all the logistics etc. tasks for them.

*so that the players could then use military logistics to request AI groups for themselves

While the commanders tablet is implying that "Auto generated tasks are disabled" this actually isn't the case since there's a conveniently placed button to bypass that blockage (see the picture below).

Is there any way to actually disable auto generated tasks? So that not a single player with a commanders tablet would go on to create any random missions for the players and that they would create the missions themselves (which is very much needed in this case!).

ARjay is gone for sometime now or for good then?

What might be the probability that ALiVE team would take a look if something could be done about the matter at hand?

Is ALiVE team aware that when promoting a player character to be the leader of an AI squad via the commanders tablet the player is placed as last the last soldier of that group. This style of "commanding from the rear" has one undesired outcome: the group formations (column, wegde and so on) won't function as they should.
No matter if the player has a lower or higher rank than the current AI squad leader, he/she will still get placed as the last one of that group.

The player should be placed as the first soldier of the group that he/she is being promoted to as a leader, otherwise the whole "promotion" functionality is there to break immersion more than anything else.

Done!

Thank you Spyder for that short instruction. With that I was able to quickly create a pull request for the mapbag model. Took waaay less time than having to figure out on my own what I would need in the first place to reach the state to be able to make the pull request.

Since there already is a PNG-file for the original tablet I provided one for this 'optional' tablet version. Though I don't know what's with the filesize (5,65 MB vs the original version's 691 KB). I didn't see any quality or compression settings when I was using Photoshop to save the PSD to PNG *shrug*

Does anyone care to give a crash course in GitHub? :) Do I need to create a repository of my own for the PSD-file here and then somehow add a pull request to Alive.os or should I fork Alive.os and then something simsalabim?

Complete newbie with GitHub but for some reason I already had an account in there :D

@Tupolov well I can provide what I have ready now. It is up to ALiVE team to finish the interface area as they see fit. Since, they (you guys) got the best idea of how the layout can or should be done in the first place.

Anyways, the model I provided was received with mild interest but apparently there is no actual interest to include at least that version in the game.. so why offer an opportunity to create one in the first place?

Thus I can only urge ALiVE team to create a more contemporary version since, I at least have an urge to get one in use anytime now.

What about if you would be able to "flag" players by using their "Variable Name" or something the like to make ALiVE not take such flagged players into account (and simply ignore them)?

I understand that how it is now is meant to be for the better part but a little room to breath wouldn't do much harm.

If anything then here's a suggestion for future development of ALiVE that it could have such option available to make the mod ignore players at mission maker's decision.