This page has been translated automatically.
Programming
Fundamentals
Setting Up Development Environment
Usage Examples
UnigineScript
C++
C#
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine and Tools
GUI
Double Precision Coordinates
API
Containers
Common Functionality
Controls-Related Classes
Engine-Related Classes
Filesystem Functionality
GUI-Related Classes
Math Functionality
Node-Related Classes
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
CIGI Client Plugin
Rendering-Related Classes
Warning! This version of documentation is OUTDATED, as it describes an older SDK version! Please switch to the documentation for the latest SDK version.
Warning! This version of documentation describes an old SDK version which is no longer supported! Please upgrade to the latest SDK version.

Version Control

Version Control Systems (VCS) are used to manage changes to code and data, and enable teams to coordinate their development efforts. To make tracking of changes efficient and to reduce the amount of disk space required you should know which files should be tracked by the VCS and which of them can be ignored.

Ignore List

In any project there are files and folders that should not be subject to version control. These might include files created by the compiler, *.obj, *.tlog, or maybe an output folder used to store binary executables.

The following files and folders in you project's root can be ignored, as they are generated automatically on your disk:

  • .thumbnails
  • bin
  • launch_debug.bat
  • launch_editor.bat
  • launch_release.bat

Files and Folders to Add to Version Control

The following files and folders should be subject to version control:

  • assets folder
  • data folder.
  • source folder contents except for the elements mentioned above.
    Notice
    This folder is created only for projects that use C++ or C# API.
  • *.project file
Last update: 2017-12-21
Build: ()