Please note though, that right now only the English language is correctly used. XML file for each language and are located in the scripts/ folder as ‘strings_.XML’. This also means you can make an airship, airplane, or rocket ship as you see fit. These scripts then make the vehicle what it is, so a 6 wheeled rover is made to act as such using these controller scripts. The afore-mentioned configs define individual parts of the vehicle, what model to use, their toughness, joints that bind them together and also which scripts to use. The controller scripts contain practically all functionality of individual vehicles. Vehicle controller scripts, which handle the functionality of each vehicle, are located in the scripts/entities/controllers/ folder as text-editable.

Vehicle configs are located in the scripts/entities/configs/vehicles/ folder, as text-editable. So to speak, this folder is the real ‘nuts-and-bolts’ of Take On Mars. For example, the ‘entities.h’ file contains definitions of basic entities used by the game, such as the base ‘GameEntity’ definition from which all Take On Mars entities are parented. Scripts for entities, the free fly camera and vehicle configs are all located within the scripts/ folder. This file is also loaded directly by the engine. In addition to this, the ‘entities.xml’ file is used by the Game Editor in the Workbench editing suite to define the editable parameters of each entity type. This is the first place to look when searching for all the functions that handle creating physics objects, dealing with them, and so on. The ‘proto.h’ script is also very important, containing the Script API function definitions from the engine. Modifying these two scripts allows you to change the entire game if desired, and can allow you to make a completely different type of game, be it Real-Time Strategy or First-Person Shooter, making Take On Mars a truly sandbox platform to build upon. The latter script, ‘CCGame.c’, is loaded when the game mechanics are initialized, and contains extended entity functions and most importantly, the campaign, also via includes. The first, ‘script.c’, is loaded on game engine start, including when you start up Workbench, and contains core functions and entity definitions via includes. These two files are the core files loaded directly from the internal game engine. Two script files are of particular interest, ‘script.c’ and ‘CCGame.c’. You can place any of this data into a mod or addon. Keep in mind that this only extracts the data and is not launch-able. The game’s pack files contain all game data including scripts and models. This will allow us to see exactly what is in Take On Mars. The following is a transcription of the video's audio track Scripts and Filesįirst off, let’s start up the loader and extract the game data to a directory of our choice.

Take on mars mods