Why Early Access?

“We believe that Chernobylite 2, similarly like first Chernobylite, will be a much better game thanks to developing it in Early Access. We saw already that constant feedback from our community allows to adapt our vision to players needs, and for big RPG game number of adjustments we can make this way is huge.”

Approximately how long will this game be in Early Access?

“We estimate about 6-10 months. This is the time required to let your feedback influence a project of this scale and to validate together changes made during Early Access.”

How is the full version planned to differ from the Early Access version?

“We plan for the game's final release to be about two to three times bigger in scope (world size, number of quests, number of characters). Also, the main hero's full story and finishing quests are subject to be delivered in the final release. Early Access is more about finalizing crafting the gameplay loop and connecting it to narratives, assuming that both gameplay and story may evolve because of that. The final version will be better optimized, balanced, and polished overall.”

What is the current state of the Early Access version?

“Our goal was to deliver the Early Access version, which is very advanced and polished in most parts. According to many closed playtests, most of the gameplay mechanics and big chunks of the content are already polished. Early Access contains about 30-40% of the final scope of the world and story. Most of the weapons and players' equipment parts are already present in the game as lootable elements.”

Will the game be priced differently during and after Early Access?

“Most likely, we’ll increase the game's price after Early Access.”

How are you planning on involving the Community in your development process?

“Like with Early Access of the first Chernobylite, we plan to gather feedback from Steam forums, our Discord server and other social media channels. We want to invite our community to let us shape the best game we can make, discuss and present our current activities within project updates, and have players involved in delivering suggestions, reporting design problems, and helping us make development decisions.”