Enhance the permission system

[Mike2306]

It would be good to have some more options in the permissions menu.

For example allow others to recruit only infantry instead of disabling the whole build menu for them.

[Wyqer]

I'll have look to split it a little bit for the next version. Will need some deeper changes from depending things, so it wouldn't be a "one hour" thing. But it's a good idea, yeah.

[SondreBakken]

I will just add on here that it would be really great if the permission menu had the option to allow other players to have the crew option (where they can build non squad infantry and predefined squads)

[Wyqer]

Why basicly should players be able to build crewed vehicles or whole AI squads? Only the commander can command them, because atm only he can build things which are only "usable" by himself.

[SondreBakken]

Well, maybe expand the permission menu to let others have the commander role aswell. Some might want to share that role. We are few people playing so it would be nice for me to share that role so I am not the only one that can send support or crewed vehicles / helis

When we use the advanced Command AI you can color code the squads and waypoints. We use that to show who is using what and controlling what. It works really well and expand the gameplay a lot.

Situations where this would be ideal is: I am far from the FOB (I am the commander) and I need a heli transport. Then I could hear if someone is in the fob, ask them to place a crewed heli which I could just ask to come pick me up.

Another example is during a attack on a bigger city. Our tank support is gone. I am in the middle of some close quarter battle. My friend respawns back in the FOB. Would be nice if he had the possibility to put out some squads and crewed vehicles and send into the battle instead of me force respawning because I am the only on that can do it.

[doodzio]

I suggest to take UNFLIP out from others where it's grouped with e.g. side missions menu.

[Wyqer]

I'm thinking about altering the permission screen to something like a "player manager" screen. With a list on the left and on the right many information (last online, killed people and other statistics) and a much deeper permission control for each player. But it's still under the "no priority". First I've to finish the civrep and enemy behaviour.

[chrisleaptrott]

My group was looking into trying to get the permissions to manage down to the type, and also split the build on unarmed vehicles and armed down further. We'd be okay with some people building light vehicles, but not tanks, littlebirds, but not jets. Etc etc.

Additionally, the possibility of adding in by role would be stellar as well. Such as having armor be open to a specific role. That would be like on the outside of the whole thing though.

Looking into the code as well myself, will report back if I or my fellow code-monkeys make any headway.

[Wyqer]

Any contributions concerning this suggestion are always appreciated. I would look at this and implement are more detailed permission system later on, of course. But currently I don't give it a high priority in relation to the other things I want to implement. So if you have a good working code and would like to contribute it, it would speed things up and after I've reviewed/tested it, I would merge it.

[madpat3]

just leave the commanderslot as it is, but make it possible to give certain permissions to people inside the whitelist, by default not only by the commander ingame (entries in the script/kp_liberation_config.sqf/mission_parameter.hpp/whatever)

[ZwinkaDink]

me and a buddy are looking into adding ExtDB to this and store permissions and other info on a DB to make it easier to give permissions in the mission. after writing this i forgot to add we made it where you had to be white listed to play medic marksman and so on and we are building the mission to use EXTDB we are testing it now and will return the results