Why should I care?
Version control (also known as revision or source control) is a procedure for managing changes to files over time; essentially, an intelligent backup system, designed specifically for the management of source code. Version control provides a tidier and vastly more robust solution to saving multiple copies of files as changes are made, e.g. “readme.txt”, “readme.txt.bak”, “readme.txt.bak2″. Generally each project will have its own repository, storing all the code and assets for that project. For every file in the repository there is a full list of changes over time. Version control systems (VCSs) provide tools for interacting with these listings, allowing the user to revert some code to an older version or work on an experimental feature in an isolated environment. A large number of version control systems exist; popular examples include Bazaar, CVS, Mercurial and Subversion. However, this article focuses on using Git, due to its widespread adoption and the popularity of GitHub.
Over the last three days I’ve been working on an early prototype of the procedural island generation system for the Vertebrae project. It’s currently still very much a work in progress and focuses more on the simple aspects of land mass generation, future versions will expand on this early work, incorporating a much larger element of actual simulation, such as erosion, rainfall, humidity and so forth. With all this data I should hopefully be able to more accurately model a living world, with well placed biomes, aiding the intelligent placement of fauna and flora within the world.