Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
op2_sdk:programming_scenario_dlls [2016/11/02 22:00] – vagabond | op2_sdk:programming_scenario_dlls [2016/11/03 17:37] – Added link to debugging scenario page. vagabond | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Programming a Scenario ====== | ====== Programming a Scenario ====== | ||
- | A complete Outpost 2 scenario (sometimes called | + | A complete Outpost 2 scenario (or mission) requires 3 files to work: a DLL, a MAP file, and a tech tree file. This page focuses on programming the DLL file. Outpost 2 scenarios are coded in C++ and require using legacy features of the language. See the [[op2_sdk: |
- | ===== Scenario | + | ===== Scenario |
- | Each scenarios is stored in .DLL (Dynamic Link Library) file. A DLL file contains code that can be linked into from other applications, | + | **Develop |
- | + | * [[op2_sdk: | |
- | Code is usually written in special text editors that have knowledge of the programming language. Notepad++ is a good example. After writing the code, you have to find a compiler to compile the code into a DLL (or other file type). | + | * [[op2_sdk: |
- | + | | |
- | Text editors designed for coding are also included in an Integrated Development | + | * [[op2_sdk: |
- | + | * [[opu: | |
- | The Outpost 2 SDK comes packaged in a Microsoft | + | |
- | + | ||
- | The filename of a scenario DLL must follow strict naming conventions to be recognized by Outpost 2. See the [[op2_sdk: | + | |
- | + | ||
- | ===== Scenario Programming Index ===== | + | |
- | **Initial Game Setup** | + | **Scenario |
* [[op2_sdk: | * [[op2_sdk: | ||
* [[op2_sdk: | * [[op2_sdk: | ||
Line 44: | Line 39: | ||
* Yes/No Dialog Box | * Yes/No Dialog Box | ||
- | ===== Technology Tree File Overview ===== | + | ---- |
- | Each scenario requires a tech tree. Scenarios can use an already created tech tree, such as the one used by the Outpost 2 campaigns, or customize a tech tree. Tech trees are created in .TXT files and are human readable. Syntax must be followed closely to ensure Outpost 2 can properly parse the tech tree. | + | ===== Scenario DLL overview ===== |
- | **WARNING: | + | The required code for a scenario is stored in its own DLL (Dynamic Link Library) |
+ | |||
+ | Code is usually written in special text editors that have knowledge of the programming language. Notepad++ is a good example. After writing the code, you have to find a compiler to compile | ||
- | ---- | + | Text editors designed for coding are also included in an Integrated Development Environment (IDE). IDEs are software packages that usually contain both a special text editor and a compiler. This allows you to write the code and compile the program in the same application. A good example of an IDE is Microsoft Visual Studio. |
+ | |||
+ | The Outpost 2 SDK comes packaged in a Microsoft Visual Studio 2015 C++ solution. Unless you are already knowledgeable enough to transfer the SDK to another IDE, it is recommended that you use Visual Studio since it will be easier to start coding without worrying about compiler setup requirements. Microsoft Visual Studio is free to use. | ||
+ | |||
+ | The filename of a scenario DLL must follow strict naming conventions to be recognized by Outpost 2. See the [[op2_sdk: | ||
- | ====== Scenario Administration | + | ===== Scenario Administration ===== |
Programming Outpost 2 scenarios requires detailed knowledge of Integrated Development Environment (IDE) setup. The best way to share your scenario source code and access other Outpost Universe source code is through the Outpost Universe Repository. | Programming Outpost 2 scenarios requires detailed knowledge of Integrated Development Environment (IDE) setup. The best way to share your scenario source code and access other Outpost Universe source code is through the Outpost Universe Repository. |