op2_sdk:programming_scenario_dlls

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
op2_sdk:programming_scenario_dlls [2016/11/02 22:00] vagabondop2_sdk:programming_scenario_dlls [2021/01/05 07:51] (current) – [Outpost Universe Repository] blackbox222
Line 1: Line 1:
 ====== Programming a Scenario ====== ====== Programming a Scenario ======
  
-A complete Outpost 2 scenario (sometimes called mission requires 3 files: a DLLs, 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:Software_Development_Kit_SDK|Software Development Kit Page]] for an overview of the MAP file and Tech tree file.+A complete Outpost 2 scenario (or missionrequires 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:Software_Development_Kit_SDK|Software Development Kit Page]] for an overview of the MAP file and Tech tree file.
  
-===== Scenario DLL overview =====+===== Scenario Programming Index =====
  
-Each scenarios is stored in .DLL (Dynamic Link Library) file. A DLL file contains code that can be linked into from other applications, like Outpost2.exe. DLLs are created by compilers that take code files and compiles them into and intermediate language or directly into assembly language. While many different programming languages can be compiled into DLLs, Outpost 2 scenarios are coded in C++. +**Develop Environment Setup** 
 +  * [[op2_sdk:ProjectCreation|Visual Studio Project Creation]] 
 +  * [[op2_sdk:ProjectSettings|Advanced Visual Studio Project Settings]] 
 +  * [[op2_sdk:Scenario Naming Conventions|Scenario Naming Conventions]] 
 +  * [[op2_sdk:Debugging Scenarios]] 
 +  * [[opu:repository|Outpost Universe Repository]] 
 +  * [[outpost_2:technical_review:operating_system_compatibility|Operating System Compatibility]]
  
-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).  +**Scenario Setup** 
- +  [[op2_SDK:PlayerColor|Player Color]] 
-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.  +  [[op2_SDK:Setting Alliances|Setting Alliances]]
- +
-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 Naming Conventions|Scenario Naming Conventions Page]] for details. +
- +
-===== Scenario Programming Index ===== +
- +
-**Initial Game Setup**+
   * [[op2_sdk:Setting Resources|Setting Resources]]   * [[op2_sdk:Setting Resources|Setting Resources]]
 +  * [[op2_sdk:TubesAndWalls|Placing Tubes and Walls]]
   * [[op2_sdk:Placing Units|Placing Units]]   * [[op2_sdk:Placing Units|Placing Units]]
-  * [[op2_SDK:PlayerColor|Player Color]] 
-  * [[op2_sdk:TubesAndWalls|Placing Tubes and Walls]] 
  
 **Environmentals** **Environmentals**
Line 44: Line 41:
   * 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:** If you wish to modify an existing tech tree file, ensure you change the name firstOtherwise, when you modify the tech tree file, it will modify all scenarios already linked to the tech tree.+The required code for a scenario is stored in its own DLL (Dynamic Link Library) file. A DLL file contains code that can be linked into from other applicationslike Outpost2.exe. DLLs are created by compilers that take code files and compiles them into and intermediate language or directly into assembly language. While many different programming languages can be compiled into DLLs, Outpost 2 scenarios are coded in C++
  
-----+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). 
  
-====== Scenario Administration ======+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 Naming Conventions|Scenario Naming Conventions Page]] for details. 
 + 
 +===== 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.
Line 65: Line 68:
  
 Source code meant for public access should be stored on the Outpost Universe Repository under the Outpost2 folder. For more information on how to use the repository, go to the [[opu:repository|Outpost Universe Repository Wiki Page]]. Source code meant for public access should be stored on the Outpost Universe Repository under the Outpost2 folder. For more information on how to use the repository, go to the [[opu:repository|Outpost Universe Repository Wiki Page]].
- 
-Outpost2 Repository Location: [[https://svn.outpostuniverse.org:8443/!/#outpost2]] 
- 
 ==== Project Management ==== ==== Project Management ====
  
  • op2_sdk/programming_scenario_dlls.1478124017.txt.gz
  • Last modified: 2016/11/02 22:00
  • by vagabond