Skip to content
This repository has been archived by the owner on Jun 22, 2024. It is now read-only.

Dev Environment

Silence edited this page Dec 20, 2022 · 5 revisions

Introduction!

This page hopes to successfully explain how you can set up a simple dev environment (Not P: drive, but if you want to go ahead).

it's not that complicated as all you will need is a bit of common sense and a .pbo packer (We personally use addon builder with a python script to pack multiple folders).

/-- This step is optional, if you have a .pbo packer already --
Download Arma 3 Tools from steam. Once downloaded, navigate to the directory, open the addon builder folder (and associated program inside). Complete setup if it asks you to. Once done, you should see a program like this. (Yours may look different, but you get the gist of it)

If you correctly opened addon builder, click on options.

In the "List of files to copy directly" box, paste this:

*.pbo,*.p3d;*.paa,*.jpg,*.sqf,*.rtm,*.cpp,*.ogg,*.txt,*.cfg,*.hpp,*.xcf,*.sqm,*.h,*.lst,*.wav,*.wss,*.rvmat,*.ext

That should cover most if not all commonly used files. Without it, nothing would end up in your packed .pbo file.

Setting up folders

  1. Create a new folder in your area of choice. We'll call this new_folder. Name it whatever you want but preferably something you will understand for the future. Inside new_folder create another folder called @[new_folder]. Now you want to create an "addons" and "keys" folder. In this example we'll be using USCG_Mod_Example. It should look like this:

image

  1. This step depends on what you're doing. If you plan on adding support for another helicopter, move here

/-- To Be Finished --\

Clone this wiki locally