James Graham operates Dungeon Crawler Carl Wiki. Email: [admin@dungeoncrawlercarlwiki.com](mailto:admin@dungeoncrawlercarlwiki.com).
> Page type: Site information and reader support > Series scope: Questions and corrections concerning the published Dungeon Crawler Carl novels, related editions, and clearly labeled adaptations > Primary contact: admin@dungeoncrawlercarlwiki.com
The Dungeon Crawler Carl Wiki is an unofficial reader reference built to help people follow a deliberately complicated series. The books move from neighborhood survival to floor-wide puzzles, divine politics, corporate law, former-crawler history, and open war. Names are reused, the dungeon changes the meaning of familiar labels, and characters often act on incomplete information. A useful correction therefore needs more than a verdict that a sentence is “wrong.” It needs enough context to show which book, scene, speaker, or edition changes the answer.
The fastest correction requests identify the exact page and the exact claim. Include the full page URL, copy the sentence or table row that needs attention, and describe the proposed change in your own words. If the point comes from a novel, name the book and chapter when possible. Page numbers are useful only when paired with an edition because ebook, paperback, hardcover, and audiobook locations do not always align.
A short source locator is enough. For example, a report might say that the Station 101 page places a rescue before Hekla joins Carl’s train, but Book 3 shows the meeting with Hekla before the run toward the station. Another report might note that a character page treats a sponsor-driven divine shell as the permanent death of the underlying god. Those are reviewable claims. Sending several pages of copied book text is neither necessary nor helpful.
The novels regularly distinguish between what the interface displays and what is ultimately true. If a correction depends on that distinction, say so. A crawler may read a nameplate correctly while misunderstanding the person behind it. Mordecai may offer a well-informed rule that later proves to have an exception. A quest description may be technically accurate while omitting the political consequence that matters most. The wiki records these layers instead of treating every line of dialogue as omniscient narration.
Please specify the continuity you mean. The main novel sequence is the default for character, floor, item, and event pages. Audio dramatizations, promotional material, comics, television development, interviews, and bonus pieces belong to separate adaptation or publication records unless a page explicitly combines them. A visual choice in an adaptation does not retroactively settle a physical detail the novels leave open.
Edition differences deserve their own note. Revised print releases may include bonus material or presentation changes, while an earlier independently published edition may use a different location marker. Audiobook performance can clarify how a name is pronounced without changing the spelling used in prose. When two legitimate editions differ, the editorial goal is to identify the difference and preserve both contexts, not declare one reader’s copy invalid.
Name collisions are especially common in this series. A deity, a sponsor-driven shell, a card totem, a dungeon caricature, and an outside political entity may share a label without being the same consciousness. The Krakaren bosses are not a simple photograph of the real distributed entity called the Apothecary. Grull’s Fourth Floor appearance involves divine identity and sponsor control at the same time. Shi Maria can be discussed as a character, a card, and a possession threat, but those uses should not be merged into one undifferentiated status line. If the problem is identity rather than spelling, explain which version the page confuses.
The archive uses spoiler scope as navigation, not decoration. A Book 3 rail guide should not reveal a Book 7 political reversal in its opening paragraph merely because both events involve the same organization. A full-series biography may discuss later consequences, but its lead should tell the reader how far the spoilers extend before naming the consequence.
Contact the site if a title, summary card, search excerpt, table of contents, or first screen of a page reveals material beyond the stated scope. Include where the spoiler appears and the earliest book needed to understand it. A practical report might say, “The meta description names the Ninth Floor allegiance before the Book 7 warning becomes visible.” That lets the editor repair both the text and its search presentation.
The site does not label every premise-level detail as a spoiler. Carl entering the crawl with Princess Donut, the existence of the dungeon interface, and the broad identity of a book’s featured floor are treated as basic orientation on relevant landing pages. Deaths, betrayals, hidden identities, late-book alliances, and solutions to floor puzzles receive stricter handling. Readers may disagree at the boundary, and thoughtful reports help refine it.
Dungeon Crawler Carl Wiki is not an official project of Matt Dinniman, the publishers, audiobook producers, adaptation partners, or other rights holders. If you own or represent rights in text, art, photography, audio, branding, or another asset that appears on the site, identify yourself, link the affected page, describe the material, and state the remedy you are requesting. Removal, revised attribution, replacement, and additional context are different remedies, so naming the desired outcome prevents delay.
The editorial standard favors original summary and analysis over reproduced prose. A correction may use a short quotation when exact wording is the issue, but visitors should not email complete chapters, screenshots of long passages, copied ebooks, audiobook recordings, leaked scripts, private production documents, or paywalled files. The books themselves should remain the place where readers experience the narrative voice, scene construction, jokes, and reveals.
Image concerns need the image URL or a screenshot of its placement, plus the page where it appears. Explain whether the problem involves ownership, credit, license terms, misleading context, or use of an unofficial fan creation. If you are reporting someone else’s work, provide a public portfolio or original post when available. The team will not guess at ownership from a repost chain.
For a broken page, include the URL, what you expected, what happened instead, and the device or browser family if it seems relevant. Useful details include a link that loops back to the same page, a table that cannot be read on a phone, headings that appear out of order, search results that point to a retired slug, or a spoiler notice that a screen reader encounters after the spoiler.
You do not need to diagnose the code. A simple sequence such as “open the Iron Tangle Rail System page, choose Station 101 under Related Pages, and receive a 404” is better than a theory without reproduction steps. If the issue occurs only at a certain text size or with keyboard navigation, mention that. Accessibility fixes are treated as editorial fixes because a reference that cannot be navigated is not complete.
Reports about factual search snippets are also welcome. Search engines and site cards may keep an older summary after the article changes. Pointing to the stale wording helps the team update descriptions and check whether the problem is internal or the result of an external cache.
Requests are prioritized by reader usefulness, source availability, spoiler risk, and how well the subject connects existing pages. A narrow page can be more valuable than a broad one when it resolves a common confusion. Station 101, for example, deserves its own entry because it ties Hekla’s proposal, the trapped crawler population, the stalled Vermillion trains, the ghoul pressure, and the later defense of Station 36 into one chain of decisions.
Please do not submit automated filler, spun summaries, or batches that repeat the same paragraphs under different headings. The series rewards close attention to mechanics and consequence. An article about the Desperado Club should explain access, conduct, commerce, security, and narrative use. It should not be a generic “important location” essay with the name swapped in.
An editor first confirms that the URL and claim match the current public page. Canon questions are checked against the relevant book scene and, when needed, nearby chapters. Cross-series claims are traced forward to determine whether a later reveal clarifies or overturns the earlier understanding. Adaptation status is checked against public, attributable announcements rather than reposted rumors.
The resulting change may be larger or smaller than the submitted wording. A single correction can expose a timeline problem in several related pages. Conversely, a confident report may become an uncertainty note if the source characters themselves do not know the answer. The wiki aims to state what the books establish, distinguish strong inference from fact, and keep unresolved questions unresolved.
Not every message receives a long individual response. Clear reports may be fixed directly. Complicated continuity questions may take longer because the surrounding chapters need review. Duplicate requests can be grouped, and abusive or promotional mail may be ignored. Sending the same report repeatedly does not improve its priority.
Send only the personal information needed for a reply. Do not include passwords, account credentials, payment information, private addresses, unpublished manuscripts, or confidential employment material. The site does not need proof of purchase to consider a correction. If you are writing in a professional rights capacity, provide a business contact method and enough information to verify that role without sending sensitive identity documents by ordinary email.
Messages may be retained long enough to investigate, document, and resolve the issue. Relevant facts from a correction can be incorporated into an article, but private contact details should not become page content. If you want a public credit for substantial research help, ask explicitly and provide the display name you want used. Anonymous corrections are acceptable when they contain enough evidence to review.
Before sending, confirm that your message contains the page URL, the specific passage or behavior, the book and chapter or public source, the correction or requested outcome, and a spoiler note if the subject reaches beyond the page’s current scope. Keep copied source material brief. Separate confirmed facts from your interpretation. If several pages share one problem, list them together rather than sending twenty identical messages.
The goal is not to make every article sound certain. It is to make each article honest about what is known, where it comes from, and why it matters inside the story. Thoughtful reader reports are one of the best ways to keep that standard intact as the archive expands.
- Copyright and Rights Requests
- Terms of Use
- Editorial Program
- Canon and Continuity Policy
- Spoiler Policy
- Category:Site information
- Category:Editorial process