Home › Submission Tutorial

How To Submit (Guide + Discovery)

Simple instructions with zero guesswork. Follow each checklist exactly.

Before You Start (Read This First)

  1. Open Create Post and decide first: Guide or Discovery. Never mix both in one post.
  2. For Discovery, the title is optional. If empty, BoundLore generates one from your structured fields (entity + location).
  3. Write for strangers. A person who does not know you must still understand your post.
  4. Never submit placeholders like "test", "asdf", random letters, or copy-paste spam.
  5. Use the step-by-step wizard. Complete one section, then continue. Use skip buttons (Unclear / No / Not observed) only when data is truly unknown.
  6. If you add evidence (image/video/file), you must map what exact facts it proves.
  7. After submit, your post enters review. Admin approves, rejects, or requests fixes.

Discovery (Structured Facts)

Use Discovery for reproducible, verifiable in-game facts. Think like a data record, not a blog post.

Step by Step

  1. Click Discovery on Create Post.
  2. Step 1 (Basics): choose Category and required Subcategory.
  3. Step 2 (Discovery Data): answer one question at a time (Identity, conditions, reproduction, expected vs observed, confidence).
  4. Use quick-skip only when needed: Unclear, No, Not observed.
  5. Step 3 (Auto Relations): link related entries or explicitly skip relations if not available.
  6. Step 4 (Evidence): map screenshots/videos/files to the fields they prove.
  7. If you add image/video/upload evidence, tick exactly which fields that evidence supports, then add a useful note.
  8. Add Update Phase, Patch Tag, and Source URL when possible for future verification.
  9. Click Submit for Review.

Field By Field (What To Enter + Why)

Entity name: required. The actual name of the item/NPC/location/mechanic discovered.
Discovery type: required taxonomy for indexing and automation (creature, item, bug, exploit, secret, etc.).
Category/Subcategory: where this belongs. This controls filters and relation suggestions.
World / Region / Where found / Coordinates: location identity for search and map-level filtering.
Trigger conditions + Requirements: time/weather/event/quest/class/level dependencies.
How to reproduce: exact steps another user can repeat.
Observed result: what happened exactly after your steps.
Expected result: what should happen instead (critical for validation and troubleshooting).
Confidence + Impact + Tags: verification quality and analytics-ready metadata.
Auto Relations: optional links to item/creature/location/guide/dependency graph.
Evidence mapping: tell the system which facts each evidence item proves.
Discovery Quality Rule: someone else should be able to repeat your steps and reach a similar result.

Do Not Do This

  1. Do not write long roleplay text in Discovery.
  2. Do not skip required identity fields (entity name/type/location).
  3. Do not upload evidence without mapping it to fields.
  4. Do not use skip values everywhere to force-pass the form.
  5. Do not post theories as facts.

Guide (Practical Explanation)

Use Guide for teaching: strategy, flow, recommendations, and practical steps for players.

Step by Step

  1. Click Guide on Create Post.
  2. Set a clear Title and pick a Guide Category.
  3. Write your content in order: goal, preparation, steps, troubleshooting.
  4. Use Guide References to link related creatures/items/locations/guides.
  5. Add Source URL and update info when available.
  6. Click Submit for Review.

Field By Field (What To Enter + Why)

Title: describe outcome, not clickbait. Better trust, better search ranking.
Guide category: puts guide in the correct hub and helps users find it.
Content: write clear steps with context and expected result.
Guide references: link entries discussed by the guide to build a data network.
Source / patch: tells readers how current and trustworthy the guide is.
Guide Quality Rule: a new player should understand the process after reading once.

Simple Guide Structure

  1. Goal: What this guide helps with.
  2. Preparation: What the player needs first.
  3. Steps: Ordered actions (1, 2, 3, ...).
  4. Troubleshooting: common errors and fixes.
  5. Verification: how the reader knows the method worked.

Guide Mistakes To Avoid

  • No huge text wall without steps.
  • No missing references for key entities.
  • No outdated patch claims without version note.

Mandatory One-Time Confirmation

You must confirm you read this tutorial before your account can submit posts.

Back to Submit

Status: not confirmed yet.

Start a Discovery Start a Guide