Fortify Feature Request: Allow custom conditions for "canFortify"

[BojanOro]

It would be nice to accept a code block so that people can specify additional requirements to be able to fortify; things like presence to a supply vehicle, being in a certain squad, etc.

[Cuel]

https://ace3mod.com/wiki/frameworkx/fortify-framework.html#13-adding-custom-deploy-handlers

[BojanOro]

While that will accomplish the end goal of not allowing a player to place until conditions are met, it is not intuitive for the self interaction option to show up if the player cannot use it.

The deploy handlers execute while the user is placing an object, my suggestion would execute while the player is opening their self interaction. This way if you see the fortify option you know you can use it, and if you cannot use it you will not see the option.

[PabstMirror]

You can restrict to a only certian locations

acex_fortify_locations pushBack X
where X is anything that inArea would accept - https://community.bistudio.com/wiki/inArea

[myCar, 50, 50, 0, false] would be 50 meters within your car

[BojanOro]

Yes, but things like checking if a player is slotted in as a member of the logistics unit, or if a team has captured a certain objective, or any other complex set of conditions would be nice to have as well.

[PabstMirror]

can set
acex_fortify_fortifyAllowed = false/true

[BojanOro]

This would enable/disable for the entire team, wouldnt it? I'm thinking of something that can be set for each player.

Edit:
Let me be more verbose. Lets say I'd like to implement the following conditions:

• Cannot fortify in the base (on a runway, etc)
• Player must be slotted in as a logistics squad
• Player must have one other person with him in order to build
• Player must not have a weapon on them in order to build

Some of those restrictions don't really make sense (namely the last two), but I include them to highlight the wide array of restrictions you may want to implement.

All of these can be done with the event handler, yes, but hiding the ACE interaction option would be an even better solution.

[Cuel]

The global variable will be set initially for the entire team but can then be toggled on/off for each client (e.g in initPlayerLocal.sqf, where you can which squad)

The rest of the conditions can be covered with deploy handlers or the acex_fortify_onDeployStart event.
Optionally you can hide the whole menu when player picks up a weapon with CBA player events https://github.com/CBATeam/CBA_A3/wiki/Player-Events

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation.

[Drofseh]

I'd still like to see this.