1
Open the exact Steam app
Make sure the title is Scary Game 2: The Mad Shepherd and the app ID is 4479970. Similar search phrases can lead to unrelated horror games, browser titles, or list articles.
Entity matchDeveloper fact check
Who Made Scary Game 2? Developer and Publisher Source Check
The short answer is KanGames. This page explains why Steam and SteamDB are the strongest sources for the Scary Game 2 developer question, how to handle conflicting third-party snippets, and where to verify future publisher or studio changes before citing them.
Checked on 2026-06-18 against the official Steam listing and SteamDB app metadata. Store metadata can change, so use official sources before quoting developer details.
Quick Answer
Recent Search Console queries show players asking who made Scary Game 2. Keep the answer direct, then check the source path when a profile, video, or social post uses a different name.
Developer
KanGames
The official Steam listing names KanGames as the developer of Scary Game 2: The Mad Shepherd.
Publisher
KanGames
Steam and SteamDB currently show the same name for publisher metadata.
Game covered
Scary Game 2: The Mad Shepherd
This page is about the Steam app, not generic scary game lists or unrelated browser games.
Best source
Steam first
Use the live store page for the final developer, publisher, release date, languages, and requirements.
Cross-check
SteamDB
SteamDB mirrors public app metadata and is useful when you want App ID, update, and technology context.
Avoid
Unverified studio swaps
Do not cite social handles, reposted trailers, or scraped pages if they conflict with Steam metadata.
Source Priority for Developer Claims
A developer answer is only useful if readers can repeat the check. Use this hierarchy before you publish, quote, or correct a Scary Game 2 developer claim.
| Source | What it confirms | How to use it |
|---|---|---|
| Official Steam app page | Developer KanGames, publisher KanGames, release date, tags, languages, requirements, achievements | Treat Steam as the primary source because it controls the live store metadata and purchase context. |
| SteamDB app page | App ID 4479970, developer KanGames, publisher KanGames, supported systems, Unity technology, record update context | Use it as a transparent cross-check, especially when a snippet or search result is stale. |
| Official social links from Steam | Social destinations connected from the store page | Use them for context only. Do not override Steam developer metadata with a profile display name. |
| Trailers, wikis, database mirrors, and forum posts | Possible context, screenshots, or player discussion | Use cautiously. These sources can copy older metadata, shorten names, or mix Scary Game 2 with unrelated horror games. |
Why the Developer Name Gets Confusing
The Scary Game 2 developer question looks simple, but it often appears beside broader searches such as system requirements, Steam release date, walkthrough, ending, download, code, key, or password. Those searches can pull in generic horror-game results, store mirrors, and social snippets that are not trying to answer the same entity question. That is why this page keeps the answer narrow: for Scary Game 2: The Mad Shepherd on Steam, the developer shown by Steam is KanGames.
Steam matters because it is the transactional source. If a player wants to buy, wishlist, install, refund, review, or inspect achievements, the store page is where the developer and publisher labels sit next to those actions. A fan wiki can summarize the answer, but it should not replace the live store metadata. If Steam changes the studio label, publisher label, release wording, or supported language table, this page should be refreshed instead of defending an old cache.
SteamDB is useful because it exposes the same app identity in a database-style layout. It lists the app ID, supported system, technology notes, update timestamps, and developer/publisher fields in a way that is easier to scan than the store page. It is not the owner of the game listing, but it is a strong second check when you need to show that the KanGames attribution is not just one scraped card.
Social profiles and video pages need more caution. A creator may use a handle, a channel name, a team label, or a brand name that differs from the exact Steam developer field. That can be normal, but it should be described as social context rather than used to rewrite the developer line. When two names appear, cite Steam for the developer answer and mention the other label only if the official store links it or the developer directly explains the relationship.
How to Verify the Developer Yourself
Use this simple process when you are checking a new article, YouTube description, social post, or search result about Scary Game 2.
2
Read both metadata blocks
Steam shows developer and publisher near the top and again in the details area. If both say KanGames, that is the strongest answer for a normal reader.
Primary source3
Cross-check with SteamDB
SteamDB should show the same app ID and developer/publisher fields. If the store and database disagree, treat Steam as live authority and wait before publishing a correction.
Second source4
Label uncertainty clearly
If a trailer channel or social profile uses another label, write that it appears as a related social or creator label, not as the confirmed Steam developer unless the store confirms it.
No overclaimingVisual and Media Notes
Game-site pages should use real first-party media or clean editorial diagrams. This page reuses the existing official-source store visual and keeps the important developer answer in crawlable text.
Related Scary Game 2 Checks
Developer intent is different from walkthrough or requirements intent, but these pages help you continue the same official-source workflow.
Steam guide
Check release date, requirements, safe download guidance, platforms, and live store details.
Open Steam guideWalkthrough framework
Use the spoiler-aware route page when your question shifts from studio facts to gameplay help.
Open walkthroughSteamDB app page
Cross-check app ID, developer, publisher, supported systems, update records, and technology notes.
Open SteamDBScary Game 2 Developer FAQ
Short answers for readers checking the developer, publisher, studio name, and source reliability.
Who is the Scary Game 2 developer?
The official Steam listing identifies KanGames as the developer of Scary Game 2: The Mad Shepherd.
Who published Scary Game 2?
Steam and SteamDB currently show KanGames as the publisher as well as the developer.
Why do some snippets show a different name?
Search snippets, video channels, and social profiles can use handles or copied metadata. Treat Steam as the source for the developer field unless an official source explains a change.
Is this page an official KanGames page?
No. ScaryGame2.blog is an independent fan wiki. It summarizes official-source information and links to Steam rather than claiming affiliation.
Does the developer page provide downloads or keys?
No. Use Steam for official ownership, updates, achievements, reviews, and install controls. This site does not host installers, APKs, cracks, keygens, or mirrors.