mirror of
https://github.com/acemod/ACE3.git
synced 2024-08-30 18:23:18 +00:00
Merge pull request #1378 from BullHorn7/docs-optional
Docs: Installation - add optionals
This commit is contained in:
commit
8810fc981a
@ -7,13 +7,13 @@ parent: wiki
|
||||
order: 4
|
||||
---
|
||||
|
||||
### Modularity
|
||||
## 1. Modularity
|
||||
|
||||
Main principles:
|
||||
- As much stuff as possible should be modular
|
||||
- Strive to make as much stuff as possible run-time togglable. Adding/removing PBOS would still be requiring to toggle any feature relying on config changes.
|
||||
|
||||
### PBO Structure
|
||||
## 2. PBO Structure
|
||||
|
||||
Main principles:
|
||||
|
||||
@ -29,3 +29,14 @@ Main -> Common -> Config things
|
||||
Main -> Common -> 3D Models |
|
||||
Interaction | -> Feature
|
||||
```
|
||||
|
||||
## 3. Optional .PBOs for 3rd Party Mods
|
||||
|
||||
- ACE3 policy is to NOT take care of compatibility with third party addons single handely. The current compatible .PBOs were kickstarted by the ACE3 team as an example to mod creators so it's clear which entries are needed for compatibility. The authors of those addons have been contacted and many of those pbos are due to be included in their respective mods eventually.
|
||||
|
||||
<div class="panel callout">
|
||||
<h5>Notice for 3rd party mod creators:</h5>
|
||||
<p>Most of the config entries are inert if ACE3 is not present, so addons can be made ACE3 compatible without explicitly requiring ACE3. However, for addons that are not inert (for example, scope configs), it is best to create and distribute compatibility .PBOs along with the original mod content; feel free to consult with ACE3 devs about how to correctly implement this. All existing compatibility .PBOs are examples and thus no further compatibility .PBOs will be provided by the ACE3 team.</p>
|
||||
</div>
|
||||
|
||||
|
||||
|
@ -21,18 +21,38 @@ This guide will explain how to get ACE3 up and running faster than you can say b
|
||||
64-Bit - `C:/Program Files (x86)/Steam/Steamapps/Common/Arma 3/`
|
||||
- After extraction you should have the `@ace` and `@CBA_A3` folders inside your Arma 3 folder.
|
||||
|
||||
## 4. Launch Arma 3 with ACE3
|
||||
## 4. Install ACE3 Optional components
|
||||
<div class="panel callout">
|
||||
<h5>Note:</h5>
|
||||
<p>Skip this step if you're not using additional mods. If you are, consult with your mission maker before installing any of these components. If you are a Mod creator, please visit the [Modularity and PBO Structure](http://ace3mod.com/wiki/development/modularity-and-pbo-structure.html) page for more information.</p>
|
||||
</div>
|
||||
|
||||
### 4.1 What do they do?
|
||||
Optional components supplement 3rd party mods with ACE3 features, for example:
|
||||
- Optional weapon components make Advanced Ballistics possible, as well as the ability to use ACE3 weapon attachments with 3rd party weapons like RHS, HLC, etc.
|
||||
- Optional tracers component brings back ACE2 ball tracers.
|
||||
- Optional server component is used to load the userconfig files.
|
||||
|
||||
### 4.2 Which optionals should I use?
|
||||
Only use the optional components that correspond with your mod-pack.
|
||||
|
||||
### 4.3 How to install these components?
|
||||
- Inside your `Arma 3/@ace/` folder, you'll find the `optionals` and `addons` folders.
|
||||
- Copy and paste the relevant `.pbo` and `.bisign` files from the `optionals` folder into the `addons` folder.
|
||||
- Copy and paste the `userconfig` folder from the `optionals` folder into root `Arma 3` folder.
|
||||
|
||||
## 5. Launch Arma 3 with ACE3
|
||||
- Launch Arma 3 to start the official game Launcher.
|
||||
- Click `Mods` and make sure the checkboxes next to `ace` and `CBA_A3` are ticked.
|
||||
<img src="{{ site.baseurl }}/img/wiki/user/installation1-launcher.jpg" width="869" height="665" alt="Arma 3 Vanilla Launcher" />
|
||||
- Click `Play`
|
||||
|
||||
## 5. Alternative launch methods
|
||||
## 6. Alternative launch methods
|
||||
|
||||
### 5.1 Steam Launch Parameters
|
||||
### 6.1 Steam Launch Parameters
|
||||
- Not supported with the new Arma 3 Launcher
|
||||
|
||||
### 5.2 ArmA3Sync
|
||||
### 6.2 ArmA3Sync
|
||||
- Inspect `Addon Options` and verify the `Addon Search Directories` are leading to your Arma 3 folder.
|
||||
- Return to the `Addons` tab and click `Refresh`.
|
||||
- Right-click inside `Addon Groups`, click `Create Group` and give it a name.
|
||||
|
Loading…
Reference in New Issue
Block a user