Thousand Hells: The Underworld Heists Release Date Guide

When does Thousand Hells release?

Thousand Hells: The Underworld Heists is scheduled to release on Steam on September 8, 2026. The date comes from the official store listing, which currently marks the game as not yet available. Because this page was prepared before launch, treat the date as planned until the Steam release button and public build are live.

Source: official Thousand Hells: The Underworld Heists Steam page.

Release detail	Confirmed information	Status
Planned release date	September 8, 2026	Listed by Steam before launch
Storefront	Steam	Official listing available
Current availability	Not yet released	Recheck on launch day
Developer	A Sharp	Listed by Steam
Publisher	Kitfox Games	Listed by Steam
Windows support	Windows 10 or later; 2 GB RAM listed	Final compatibility testing not yet confirmed
macOS support	macOS 13 or later; Apple M1 or Intel; 2 GB RAM listed	Final compatibility testing not yet confirmed

For a fuller introduction to the systems, read the beginner guide. The 29-minute gameplay walkthrough shows how a pre-release mission moves from character creation and recruitment into travel and infiltration.

What will you do in Thousand Hells?

You form a four-hero party, accept a changing contract from the mysterious Ambassador, and descend into a distinct underworld. The core challenge is narrative and tactical: choose paths, assign appropriate party skills, and decide when a larger payoff justifies physical or mental risk. Your successes and failures can alter the crew beyond one encounter.

Gameplay layer	Player responsibility	Main uncertainty
Contract	Understand the mission objective	The contract changes between missions
Party formation	Recruit professions, skills, and personalities	Not every hero gets along
Narrative encounter	Select a path and use a fitting party strength	Outcomes can depend on context and consequences
Risk management	Balance rewards against body and mind	Harm may affect later parts of the run
Underworld route	Adapt to a setting’s particular threats	Each hell is designed to feel different
Replay	Retry failure or create another quest	Available helpers can change each time

Is this a conventional combat RPG?

The supplied material emphasizes tactical narrative encounters rather than a combat-first loop. Examples include calming bandits with a bard or communicating with a possessed book through a demonologist. Combat may occur, but its frequency, structure, and importance in the launch build are not yet confirmed.

How should you form a launch-day party?

Build for variety rather than choosing several heroes with overlapping strengths. Every recruit brings a profession, skills, traits, and a personality, while interpersonal compatibility may affect how well the crew functions. A flexible first party should cover social problems, specialist knowledge, physical trials, and supernatural threats without depending on one character for every difficult situation.

Party check	Useful question before departure
Profession coverage	Does each recruit solve a different category of problem?
Skill variety	Can the crew answer social, physical, mental, and supernatural trials?
Personality mix	Are there known conflicts or conditions between recruits?
Risk tolerance	Which hero can absorb a consequence without breaking the plan?
Contract fit	Does at least one specialist directly support the mission objective?

Once verified character entries exist, compare recruits through the character index and use the trait reference to understand what each quality actually enables.

Why do choices matter during a mission?

Choices can redirect the story, expose the crew to harm, and change party capabilities. The supplied examples contrast safer paths with riskier options that promise larger rewards, while noncombat specialists can sometimes avoid a direct confrontation. The important decision is not simply which option sounds strongest, but whether the party is equipped to survive its consequences.

Decision factor	Safer approach	Higher-risk approach
Skill match	Use a hero whose profession clearly fits	Attempt with an indirect or uncertain action
Party condition	Protect an injured or stressed specialist	Expose that hero for a valuable result
Reward value	Preserve resources for the contract	Pursue an optional payoff
Future uncertainty	Keep flexible skills available	Spend a strong action immediately
Alternate route	Avoid confrontation when possible	Accept conflict for speed or reward

The tactical narrative encounter guide explains the pre-release hero, action, situation, win, and loss structure in more detail. Its numerical rules remain provisional until they can be reproduced after launch.

What makes the game replayable?

Replayability is built around changing quests, retryable failures, variable helpers, distinct underworlds, and choices that alter the party. The supplied material estimates about one hour per run and says automatic saving plus a story synopsis supports shorter sessions. Those timing and save-system claims still need testing in the public release build.

Replay feature	Pre-release claim	What to verify after launch
Quest structure	A new unique quest can be created	Which elements are procedural or recombined
Failed mission	A failed mission can be retried	What carries over between attempts
Helper cast	Available helpers differ each time	Selection rules and pool size
Run duration	About one hour	Range across contracts and play styles
Automatic saving	Supports stopping during a run	Save timing, slots, and rollback behavior
Story synopsis	Recaps the journey so far	When it updates and what it records

How should you use a failed first run?

Write down the contract, destination, available helpers, major choices, injuries, and the obstacle that ended the attempt. On a retry, change the weakest coverage instead of rebuilding the same party by habit. This is a planning recommendation; persistence and carryover rules remain not yet confirmed.

What underworlds and stories should you expect?

The game takes place in a stand-alone fantasy world centered on the Byzantine-flavored Eternal City, with multiple underworlds below it. Each hell has its own visual palette and threats. Story examples include an Orpheus-inspired rescue and an insect plague threatening the city, but the full mission and underworld lists have not been published here.

Setting detail	Information currently available
Home setting	The Eternal City
Employer	The mysterious Ambassador
World structure	Multiple distinct, myth-inspired underworlds
Narrative example	Follow in Orpheus’s footsteps to rescue a loved one
Narrative example	Attempt to save the Eternal City from an insect plague
Creative structure	An anthology credited to eight writers
Named writers	Robin D. Laws and Aaron A. Reed

Browse the underworld index for destination-specific planning and the ending section for verified route consequences once those pages are populated.

What should you do before launch?

Wishlist the game on Steam if you want a storefront notification, then use the remaining pre-launch time to understand party coverage and encounter logic rather than memorizing an unverified build. On release day, confirm availability, review the current options menu and save behavior, and test early mechanics before relying on any fixed route or recommended composition.

1. Open the official Steam page and confirm the release status.
2. Review the beginner guide for the party-planning framework.
3. Watch the sourced gameplay overview without assuming every pre-release detail survived unchanged.
4. Start with varied professions and record which traits create useful encounter actions.
5. Verify injuries, saving, quest generation, and retry behavior before publishing firm recommendations.

Which details need launch-day verification?

The September 8 date is planned rather than a completed launch. Availability, exact launch time, build identifier, party behavior, skill changes, run duration, autosave, quest generation, injuries, and combat frequency all need to be checked against the public build. Until then, treat those mechanics as preparation guidance rather than final documentation.