왜 앞서 해보기를 하나요?

“We’re building a replayable, systems-driven defense game where a single tweak to XP, attack speed, or enemy composition can swing the whole run. Early Access lets us iterate in the open with real player data and feedback to tune balance, pacing, and build diversity across our three dragons (Fire/Water/Electric) and six enemy types. We want the core loop—protecting your castle/tower in an endless onslaught while drafting level-up perks and loot—to feel tight, fair, and rewarding from minute one to hour fifty. That kind of tuning is fastest with a live community.

Early Access also helps us prioritize content with you. We already have a solid foundation: three distinct dragons with unique passive level-up identities (e.g., Fire = attack speed scaling, Water = XP rate scaling, Electric = luck scaling), a growing enemy roster (goblin → elite/boss variants, splitters, titanoboa), draftable level-up choices (XP Rate, Attack Damage/Speed, Luck, Crit Chance/Damage, Projectile Multiplier, Difficulty), lootable modifiers from chests (e.g., castle HP, projectile bounce), and upgradable walls you can build around your keep. With your input, we’ll expand the best parts first—more dragons, more enemy families, more items, deeper wall upgrades, and additional synergies.

Finally, we want to ensure the game is accessible yet skillful: clear UI, meaningful choices every level, and difficulty options that scale from relaxed to ruthless. Early Access gives us the runway to test new builds, respond quickly, and ship frequent, transparent updates shaped by the community.”

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

“Approximately 6 months from the Early Access launch.”

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

“More content variety: additional dragon types, new enemy families (with fresh behaviors, elites, and bosses), and a broader pool of items/relics to deepen buildcraft.

Fortification depth: expanded wall tiers, more meaningful upgrade paths, and potential synergies between fortifications and your dragon/build.

Build diversity & balance: continued tuning of perks, difficulty options, and enemy compositions so different strategies (glass-cannon crit, projectile-multiplier, XP engines, etc.) all feel viable.

Progression & challenge: light meta-progression and optional challenge modifiers to support long-term goals and replayability.

Quality of life: clearer UI/UX, accessibility options, controller/rebind support, performance work, and additional localization.

Audio/visual polish: improved VFX/SFX, feedback clarity, and readability during high-intensity waves.”

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

“Core loop: Endless “defend the castle/tower” runs with decision-driven builds.

Playable dragons: Fire / Water / Electric, each with a distinct passive on level-up
(e.g., Fire = attack speed scaling, Water = XP rate scaling, Electric = luck scaling).

Enemies (6 types): goblin, elite goblin, boss goblin, splitter goblin, elite splitter goblin, boss titanaboa.

Level-up choices: XP Rate, Attack Damage, Attack Speed, Luck, Crit Chance, Crit Damage, Projectile Multiplier, Difficulty.

Loot & items: chest drops like castle/tower HP boosts and projectile bounce-type effects.

Fortifications: buildable, upgradable walls around your keep.”

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

“We’re not planning to change the base price between Early Access and the 1.0 release. ”

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

“Steam Community Hub & Discussions

Dedicated feedback threads for each major update (balance, perks, enemy behavior).

Upvoted ideas get a “On Our Radar” tag for visibility.

Discord Server

Channels like #feedback-balance, #bugs, #ideas.

Weekly community summaries highlighting key topics and actions we took.

Occasional polls (e.g., “Is Projectile Multiplier overtuned?”).

In-Game Feedback

A lightweight feedback form with optional logs so we can quickly reproduce balance/issues.

Transparent (Living) Roadmap

Public, lightweight board with states like “Testing Soon”, “Under Review”, “On Hold”—updated as priorities shift.

Test Branches / Betas

Big balance/content drops may hit an opt-in test branch first; we iterate based on feedback, then merge to main.

Dev Notes & Patch Notes

Every update includes “Why we changed it” blurbs—so you see not just what changed, but why.

Community Contributions

Regular calls for naming ideas, balance suggestions, and QoL tweaks; we’ll credit contributors in notes.”