-
Notifications
You must be signed in to change notification settings - Fork 11
Home
Welcome to the Reactor 3 wiki! Included in this wiki is enough information to both play and develop/mod Reactor 3. For players, I highly recommend reading Getting Started - The Beginner's Guide to Surviving the Zone. It's an all-inclusive guide to learning the various ins and outs of Reactor 3. Developers should dive right in to Developing for Reactor 3.
Reactor 3 is an "action roguelike" played in semi-real-time with a focus on realistic gun-based combat and damage modeling. It's also a spiritual successor to STALKER - Shadow of Chernobyl and IVAN - A Violent Road to Death.
Location: The Zone, an irradiated area surrounding the Chernobyl Nuclear Power Plant, where a devastating incident caused the fourth reactor to completely self-destruct in 1986. In an alternate timeline, the third reactor caught fire shortly after the initial destruction, sending another wave of radiation through the Zone, corrupting all surrounding life. The city of Pripyat was abandoned immediately following the first incident, forever freezing the city in time.
Fast-forward: It's 2016. Rumors of invaluable goods retrieved from the Zone start to fill the darker corners of society, and a curiosity builds inside of those looking for fame and fortune. Enter you, down on your luck and looking for a way back to the top, you head to the Zone with the intention of doing whatever it takes to make a living from selling the artifacts.
I highly recommend running Reactor 3 from source. In addition to running a bit quicker, updating will also be fairly seamless since there is no longer a need to download the entirety of a bloated executable for a bugfix or other small change.
The source can be grabbed right off of GitHub using git clone <URL HERE>. After everything is fetched you'll need to install the libtcod dependency. This is done by .
TAKE NOTE: When installing libtcod, make sure to not overwrite the included libtcodpy.py file, as it contains a fix for 64bit systems that has yet to be adopted into the official release.
Two branches exist for Reactor 3: master and experimental. master provides the most stable and well-tested experience, while experimental leaves you on the bleeding edge with newer features\changes that might not be as stable. The two branches are merged once the bugs are worked out of experimental.
It is relatively safe to play using the experimental branch, as it is a rare event that broken code is pushed to the repo without being disabled first or marked in a commit message as broken. That said, I'm not able to test absolutely every new addition in every possible way, so in the event of a crash, please do not hesitate to check the issue tracker for an existing entry. If one does not exist, please create one. If you do not want to make an account, you can email me directly about it (subject: "Reactor 3 bug").
Saves are only guaranteed to work on whatever branch they were created on. When a merge between the branches occurs, there will be a way to update saves.