What You Need to Know Before Starting
I keep seeing people ask about this because it pops up in search results with zero actual guides attached to it. The honest answer is that "City Of Broken Dreams Guide" doesn't map to any single well-documented product, game, or system I can confirm exists as of my last update. There are indie projects with similar-sounding names — a tabletop RPG supplement, a few small Steam titles, and some ambient music collections — but none of them share an authoritative guide that circulates widely enough for me to vouch for a specific one. If you're looking for one, start by pinning down exactly which project you mean. The title alone covers at least three different things depending on whether you're talking about a board game, a visual novel, or a PC indie title. Once you know the developer or publisher, check these sources in this order: Board game or tabletop product — BoardGameGeek wiki pages and the designer's official website or Discord. PDF rulebooks live there, usually under a "Resources" or "Downloads" tab. Forfan shops sometimes host player aids.
Steam or itch.io game — the official Steam Discussions thread, the game's subreddit, or the developer's Itch page. Most indie devs post patch notes and FAQ links directly on the store page under "Community Hub." Music or audio project — Bandcamp, Spotify artist pages, and YouTube descriptions. These rarely have formal guides, but lyric sheets and behind-the-scenes write-ups show up in the merch section or creator notes. I ran into this exact problem last year when someone linked me a "City Of Broken Dreams Guide" PDF that turned out to be for a completely different game with a nearly identical name. The workaround was straightforward: cross-reference the ISBN or the app ID number printed in the document header with the official store listing. Three seconds and you avoid ordering the wrong thing entirely.
What Usually Goes Wrong When People Can't Find It
Most of the time the issue is one of three things. The first is capitalization and spacing. Developers don't always format their titles consistently, so searching "City of Broken Dreams guide" versus "City of Broken Dreams Guide" versus "city of broken dreams" pulls different results depending on how the store page or PDF was indexed. The second is that indie projects frequently rename themselves during early access, and old forum threads keep pointing to URLs that no longer resolve. The third is that some of these projects never had a formal guide published at all — they rely on community wikis that may be scattered across Fandom, Obsidian, or private Discord servers. Here's a counter-intuitive one that beginners miss: the most useful guide is often not the official one. Community walkthroughs and video playthroughs from the first week of launch capture mechanics as they actually shipped, before patch notes reworded everything. I've seen official PDFs get updated so aggressively that a rule explained in version 1.2 contradicts version 1.5, and nobody notices until someone publishes a comparison post with timestamps. Check the revision history on whatever document you download. If it doesn't list dates or version numbers, treat it as unofficial speculation rather than authoritative rules.
Get the Full Details
Setting expectations realistically
This isn't a flaw in your search — it's a structural problem with small-scale releases. When a project launches without a dedicated wiki, a developer handbook, or a community manager, there simply isn't a centralized guide to find. The workaround is to compile information yourself. Screenshot the key screens, log the patch notes in a single document, and join the project's Discord or subreddit to ask the developer directly. Most indie teams are responsive if you frame your question around a specific mechanic rather than a vague "how does this work?" request. If you tell me which exact product you're referring to — the developer name, platform, or a link to where you saw the title — I can point you at the right resource instead of making you chase dead links.
