왜 앞서 해보기를 하나요?

“I am using Early Access to tune the core loop, find → stabilize → deliver, with real player feedback. My focus is on hoverbike handling feel, timer pressure, fail conditions, enemy pressure, and the clarity of bearings from Sola.

Sola is optional, so the game plays fine with Sola on or off, and I am shaping guidance and UX for both styles.

I am refining the outpost economy so choices around ammo, oxygen, fuel, and BitCredits feel meaningful. I am also strengthening stability and performance across a wide range of PCs, and I document settings that help on lower end hardware. The goal is to reach a state where the core loop feels consistently fun, fair, and stable for solo play on common hardware.”

이 게임의 앞서 해보기 기간은 얼마인가요?

“Several months (roughly 6–12), subject to change based on feedback and scope.”

정식 버전은 앞서 해보기 버전과 어떻게 달라지나요?

“Aiming for more detailed zones/sectors, additional relay/event types, deeper outpost systems, expanded Sola dialogue, QoL/accessibility options, achievements, and broader performance/controller support. Plans may change.”

지금 앞서 해보기 버전은 어떤 상태인가요?

“Playable now with Easy/Hard modes, three relays to power, hoverbike traversal, resource management (fuel/oxygen/health/stamina/ammo), outposts and BitCredits, optional local-only Sola dialogue, save/load, and basic settings. Balance, performance, and content are in progress.”

앞서 해보기 동안과 앞서 해보기 이후의 게임 가격이 다르게 매겨지나요?

“I plan to launch EA at a lower price and raise it for 1.0 as new content and features land.”

개발 과정에 어떻게 커뮤니티를 참여시킬 계획이신가요?

“Steam Discussions will be the main hub, with clear categories for Bug Reports, Balance, Quality of Life, and Suggestions. I read and check threads regularly and tag them so issues and ideas are easy to track.

Patch notes accompany updates. Notes are labeled by version and date, with sections for New, Balance, Fixes, Technical, and Known Issues. I also maintain a known issues list and an FAQ for clarity.

I invite frequent players who provide clear reports to help validate changes and catch regressions. I keep updates small when a quick fix is needed, and group larger changes when they benefit from more testing.

Bug reports work best with steps to reproduce, the expected and actual result, a save file if requested, and basic hardware information.

I stay active in discussions. I ask follow up questions when needed. When a change ships, I explain why it happened, and I credit especially helpful reports in notes or credits.”