Arma3_Epoch/ACE3
1
0
Fork 0
mirror of https://github.com/acemod/ACE3.git synced 2024-08-30 18:23:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix Fortify Framework documentation (#7151)

Browse Source
This commit is contained in:
jonpas 2019-08-28 16:30:53 +02:00 committed by PabstMirror
parent 4204205908
commit d7800c084f
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/wiki/frameworkx/fortify-framework.md
View File

@ -33,7 +33,7 @@ There are two ways of adding custom presets to your mission, either via code or
To add a preset via code you use the function `call acex_fortify_fnc_registerObjects`. Also enables Fortify.
```
```cpp
* Registers the given objects in the given side's player interaction menu.
* Players on that side must have the `Fortify Tool` item in their inventory to access the menu.
* Classnames must be in the format [<classname>, <cost>]
@ -53,7 +53,7 @@ To add a preset via code you use the function `call acex_fortify_fnc_registerObj
Adding it through `description.ext` you use:
```c++
```cpp
class ACEX_Fortify_Presets {
class myMissionObjects {
objects[] = {
@ -69,9 +69,9 @@ class ACEX_Fortify_Presets {
A custom deploy handler allows missions makers to decide if an object can be placed or not.
To verify that an object isn't above a certain terrain height we can check the heigt of the object before it is confirmed as placed. Returning `false` from the code block means that placement is not allowed.
To verify that an object isn't above a certain terrain height we can check the height of the object before it is confirmed as placed. Returning `false` from the code block means that placement is not allowed.
```sqf
```cpp
[{
params ["_unit", "_object", "_cost"];
private _return = (getPosATL _object) select 2 < 1;