Halloween: The Game Steam Version

What is the Steam app ID?

The Steam SKU is app 3219630, published by IllFonic with Gun Interactive, and lists Unreal Engine 5 plus Easy Anti-Cheat. Steam features include controller support, Cloud, Family Sharing, Trading Cards, and Achievements, but the checked schema also showed achievements None. Store-label date and regional price should be rechecked before purchase. This page is organized around store identity, feature wording, and the regional or hardware limit on the claim. It gives the source-backed answer first, then separates adjacent claims so a player can check one result without treating an unlisted detail as confirmed.

This is a source-led answer, not a prediction. It gives you a way to opening the correct app and tells you where the wording came from: steam, official, hotfix.

Who publishes it?

A player can act on technology without pretending the whole system is mapped. The checked wording is: Steam lists Unreal Engine 5 and Easy Anti-Cheat. The next useful comparison is feature flags, which has its own evidence trail.

A useful check is to note the technology alongside the map, chapter, role, store, or build where you saw it. Then checking the technical feature row. If the prompt or result differs, preserve the observation and the date instead of silently upgrading it to a universal rule. Keep the question tied to the evidence. To checking the technical feature row, compare the in-game result with the published record from steam, official, hotfix.

Which PC features are listed?

Treat Feature flags as the page’s working checkpoint. Steam lists controller support, Cloud, Family Sharing, Trading Cards, and Achievements. That is enough to separating a feature flag from a trophy list; it is not evidence for an unlisted cooldown, spawn rule, reward, or score calculation.

A useful check is to note the feature flags alongside the map, chapter, role, store, or build where you saw it. Then separating a feature flag from a trophy list. If the prompt or result differs, preserve the observation and the date instead of silently upgrading it to a universal rule. The checked sources (steam, official, hotfix) support the named checkpoint; they do not turn an unlisted mechanic into a confirmed rule.

Why does achievements metadata conflict?

The answer changes depending on what you are checking. For metadata conflict, the cited record says The checked schema snapshot showed achievements None despite the feature list and console trophy sources. Keep that beside the context for app before reporting a result.

A useful check is to note the metadata conflict alongside the map, chapter, role, store, or build where you saw it. Then recording the snapshot date. If the prompt or result differs, preserve the observation and the date instead of silently upgrading it to a universal rule. Read this as an updateable field guide: recording the snapshot date is actionable now, while anything outside the cited wording stays open.

A reproducible first check looks like this:

1. Open PC system requirements and choose the named context before starting.
2. Test Metadata conflict before drawing conclusions about the wider system.
3. Save the result with the build and the nearby App context.
4. Compare the result with the platforms hub before calling it a general rule.

Which date does Steam show?

Start with App. The Steam app ID is 3219630. The related source is Steam store and Web API snapshot. That distinction matters because technology is a neighboring checkpoint, not an automatic consequence of the first one.

A useful check is to note the app alongside the map, chapter, role, store, or build where you saw it. Then reading the system requirements. If the prompt or result differs, preserve the observation and the date instead of silently upgrading it to a universal rule. For reading the system requirements, use the named fact as the checkpoint and the source list (steam, official, hotfix) as the audit trail.

What should a PC buyer check?

The record separates Technology from Feature flags. It says Steam lists Unreal Engine 5 and Easy Anti-Cheat. It also names steam lists controller support, cloud, family sharing, trading cards, and achievements. Read those as two claims with two tests, rather than as a hidden formula.

A useful check is to note the technology alongside the map, chapter, role, store, or build where you saw it. Then comparing the edition page. If the prompt or result differs, preserve the observation and the date instead of silently upgrading it to a universal rule. The useful boundary here is practical: comparing the edition page can be checked against steam, official, hotfix, but no unsupported rate or timer is added.

Where does the evidence stop?

The evidence set for this page is steam, official, hotfix. It supports the rows above, but it does not publish every cooldown, spawn point, drop rate, score formula, cosmetic inventory, or farming route. Those omissions are deliberate. If a later official post or a reproducible in-game test adds one, update the row and its check date rather than backfilling the gap with a guess.

For the next step, open PC system requirements and the platforms hub. Those links carry the reader to a neighboring question instead of ending the session at a definition.

A practical next stop

Use the release date when you need the wider platforms context, then return to PC system requirements for the named checkpoint. the platforms hub provides the second angle: it helps you separate app from technology instead of combining them into one unsupported conclusion. The FAQ is a compact maintenance list; when a source changes, update the relevant row, wording, and last-modified date together.