

To use Git from the command line, see the Setting up Git and Fork a Repo articles. Install GitHub for Windows then fork and clone our repository. The steps below will take you through cloning your own private fork, then compiling and running the editor yourself: Windows Other short-lived branches may pop-up from time to time as we stabilize new releases or hotfixes. We aim to merge development branches to master every 3-4 weeks. Battle-hardened developers eager to test new features or work lock-step with us should head to one of these. These branches reflect the cutting edge of the engine and may be buggy - they may not even compile. Individual teams have their own development branches for day to day work ( dev-core, dev-mobile and dev-sequencer, for example). Our internal game teams typically take engine snapshots from here, but it isn't subject to as much testing as release branches. The master branch is the hub of changes from all our specialized engine development teams. We try to update with merges from the master branch daily (though we often catch things that prevent us from doing so) and it's a good balance between getting the latest cool stuff and knowing most things work. The promoted branch is updated with builds for our artists and designers to use.

We work hard to make releases stable and reliable, and aim to publish new releases every few months. The release branch is extensively tested by our QA team and makes a great starting point for learning the engine or We publish source for the engine in several branches: If you need more, just ask! A lot of Epic developers hang out on the forums or AnswerHub,Īnd we're proud to be part of a well-meaning, friendly and welcoming community of thousands.

