https://wiki.outpost2.net/wiki/ 2026-08-19T07:19:10+00:00 https://wiki.outpost2.net/wiki/ https://wiki.outpost2.net/wiki/_media/logo.png text/html 2018-10-07T15:27:20+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:create_msvczip?rev=1538926040&do=diff Create MSVC.zip These steps are for installing Build Tools for Visual Studio on Windows and then packaging them up to be use inside of a Wine install on Linux or MacOS. See Project Creation for more details. The first few steps for creating this are the same as installing Build Tools on Windows, text/html 2016-11-03T04:14:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:creating_tech_trees?rev=1478146482&do=diff Creating Tech Trees Outpost 2 Tech Trees can be highly customized for individual scenarios. Each tech tree is a a .txt file that is parsed by Outpost 2 and may be used by multiple scenarios. Outpost 2 shipped with several different tech trees. Each of these can be used on a new scenario instead of designing a new tech tree. Tech trees pre-included with Outpost 2 game distributions are often stored in .vol files. The text/html 2017-01-09T07:55:03+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:custom_scenario_checklist?rev=1483948503&do=diff Outpost 2 Custom Scenario Checklist Below is a checklist to review against new Outpost 2 scenarios. The checklist is designed to highlight most requirements involved in making a scenario DLL mesh with Outpost 2 programmatically and fulfill typical expectations of Outpost 2 players. This list is meant as a guide but not a rigid requirement. It is not meant to prevent someone from being creative or breaking the rules. text/html 2016-10-12T21:32:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:dayandnight?rev=1476307966&do=diff Day and Night Cycles Reviewed For: SDK 2.1 Scenario Day and Night Cycles can be manipulated through the SDK. Day and Night settings should be set in the InitProc() function and have three different basic settings. * Day/Night cycles over time * text/html 2021-01-09T04:00:00+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:debugging_scenarios?rev=1610164800&do=diff Debugging Custom Scenario DLLs Since we do not have access to the Outpost 2 source code or program debug database (PDB file), we cannot step through the Outpost 2 executable code or compare the stack trace with source code. However, we can still debug custom scenario DLLs. text/html 2016-12-29T17:55:05+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:disasters?rev=1483034105&do=diff Disasters Reviewed for SDK 2.1 All disasters in Outpost 2 are fully supported by the SDK. This section covers Meteors, Electrical Storms, Earthquakes, and Vortices. Volcanoes are handled in the Volcano Section here: Volcanoes. When setting a disaster, you are setting when the first warning that the disaster will occur. No disaster can occur at mark 0 (when a scenario first starts). Even if you set a disaster to immediately occur, it actually will not happen until about mark 10-15. The excepti… text/html 2017-06-25T05:27:50+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:editing_map_tilesets?rev=1498368470&do=diff Editing Map Tilesets Outpost 2 maps consist of a 2D grid of cells. Each cell contains a tile which is a texture pulled from a tileset image. Each tile is 32×32 pixels. Outpost 2 tilesets are 8bpp BMPs with indexed color palettes. The stock Outpost 2 BMPs are all named well00XX.bmp and stored in the maps.vol archive file. Each tileset is exactly 1 tile wide (32 pixels) and a varying number of tiles tall. text/html 2017-07-27T00:50:47+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:mapmaking?rev=1501116647&do=diff Outpost 2 Mapmaking Each Outpost 2 scenario (sometimes called a mission) requires a supporting .MAP file. The MAP file contains the tiles and associated metadata required to create a swath of New Terran Terrain. Typically, maps are created and edited with the OP2Mapper. Preexisting maps may be used for new scenarios with no modifications. For inspiration, see the current maps here: text/html 2016-10-12T21:32:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:morale?rev=1476307966&do=diff Morale Reviewed For: SDK 2.1 Colony morale can be set as either fixed or variable individually per colony. If creating a multiplayer scenario, check to see if the players' desire steady morale and set appropriately. For land rush games, consider setting morale as fixed until after the player establishes a base. text/html 2016-10-12T21:32:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:music?rev=1476307966&do=diff Music Reviewed For: SDK 2.1 Each scenario in Outpost 2 can be tailored to use a specific subset of the available in game music. All music tracks are represented in the enum SongIds. In order to customize the tracks, place an array of SongIds in the scenario. Then inform the game of the array via the function text/html 2016-10-12T21:32:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:placing_units?rev=1476307966&do=diff Placing Units Reviewed For: SDK 2.1 The Unit class represents all buildings and vehicles in Outpost 2. New units should be created using the function CreateUnit defined in TethysGame.h. Initial Units should be defined within the function InitProc() text/html 2016-12-17T17:34:34+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:playercolor?rev=1481996074&do=diff Player Color Player colors can be set using the SetPlayerColor function from TethysGame. Seven different colors are available and can be referenced through the PlayerColor enum. // Color of structures and units belonging to a given player enum PlayerColor { PlayerBlue = 0, //Standard Eden color PlayerRed, //Standard Plymouth color PlayerGreen, PlayerYellow, PlayerCyan, PlayerMagenta, PlayerBlack //Not selectable as a player color from the multiplayer game initialization scre… text/html 2021-01-05T07:51:58+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:programming_scenario_dlls?rev=1609833118&do=diff Programming a Scenario 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 text/html 2021-01-05T07:47:47+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:projectcreation_tempnew?rev=1609832867&do=diff Outpost 2 Scenario Project Creation Settings Reviewed For: SDK 2.1 using Visual Studio 2017 or Visual Studio Code Creating new Outpost 2 scenarios requires programming and compiling a new DLL (dynamic link library). This articles reviews specific instructions on preparing Visual Studio to program a scenario DLL. See the . text/html 2021-03-06T21:25:58+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:projectcreation?rev=1615065958&do=diff Outpost 2 Scenario Project Creation Settings Reviewed For: SDK 2.1 & Visual Studio 2015 Creating new Outpost 2 scenarios requires programming and compiling a new DLL (dynamic link library). This articles reviews specific instructions on preparing Visual Studio to program a scenario DLL. See the . text/html 2016-11-03T17:40:52+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:projectsettings?rev=1478194852&do=diff Development Environment Project Settings This page lists common development environment customizations when creating Outpost 2 scenario DLLs using Visual Studio. The customizations include changing the target file name, copying files to a new directory on post build, referencing Outpost 2 from Visual Studio, and debugging. You should have Visual Studio running and compiling basic scenario DLLs before proceeding............. text/html 2016-10-12T21:32:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:scenario_naming_conventions?rev=1476307966&do=diff Scenario Naming Conventions Each Outpost 2 scenario has an associated DLL. The scenario's DLL must follow the naming conventions below for Outpost 2 to register it. The max character count is 7, not including the file's extension. Scenario Naming Conventions text/html 2016-12-17T17:30:23+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:setting_alliances?rev=1481995823&do=diff Setting Alliances Reviewed For: SDK 2.1 Player Alliances can be set on game initialization for both multiplayer and colony scenarios. For a full alliance, remember to set both players as allied to each other. See sample below. Related Source Code text/html 2016-11-04T17:54:48+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:setting_resources?rev=1478282088&do=diff Setting Resources Reviewed For: SDK 2.1 Colony resources can be set or retrieved for any player whether they are human controlled or AI controlled. Typically, resources values are reduces or increased based on the difficulty selected by the player. text/html 2020-06-13T17:39:02+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:software_development_kit_sdk?rev=1592069942&do=diff Outpost 2 Software Development Kit (SDK) The Outpost Universe community has diligently maintained and extended Outpost 2 through modifying the original game and creating an API that allows adding new content. Notably, new maps can be designed, new scenarios created for new or old maps, new map tiles can be added, and technology trees can be manipulated. A listing of current maps for the game can be found in the text/html 2016-12-28T19:03:29+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:textdialogbox?rev=1482951809&do=diff In Game Text Dialog Box The Outpost 2 SDK supports adding custom dialog boxes during single player scenarios. Often dialog boxes are used to provide mission briefings or background story for colony missions. Sierra's odasl library can format dialog boxes to match the Outpost 2 UI theme. text/html 2016-10-12T21:32:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.outpost2.net/wiki/op2_sdk:victory_and_defeat_conditions?rev=1476307966&do=diff Victory and Defeat Conditions Reviewed For: SDK 2.1 Outpost 2 scenarios can contain multiple conditions to stipulate either victory or defeat. These conditions can be dynamically enabled or disabled as game play progresses to shift a scenario's focus.