Guides & Community
Builds, routes, settings — and the rules that keep them useful.
FragMentor guides are written like field notes: tested, compact, and honest about assumptions. We don’t write to impress — we write to help you win time back. If a guide can’t be followed in one sitting, we trim it until it can.
The main idea is simple: good guidance is reproducible. Another player should be able to copy your steps, match your setup, and get the same result without guessing what you meant.
We focus on systems and decisions: priorities, routes, timings, settings, and tradeoffs. No lore dumps. No plot talk. No “trust me bro” magic builds — if something is strong, we explain why, what it costs, and when it stops working.
Think of it as a calm workshop: share what you learned, document the steps, and keep the tone respectful.
Our guide format
Most guides follow a clear skeleton. You can use it as a template when you submit:
1) Goal: what this guide helps achieve (ranked win condition, boss clear, economy start, etc.).
2) Setup: platform, patch version, difficulty, key settings, required items/perks.
3) Steps: a clean route or priority list with “if X → do Y”.
4) Checks: what “success” looks like at minute 5/10/20 (simple milestones).
5) Variants: one safe alternative for players with different skill/gear.
6) Common mistakes: short list of the usual traps.
Contribution rules
- State your context: platform, patch version, difficulty, key settings, and anything required to reproduce the result.
- Show the steps: route order, timings, priorities, and simple “if X then Y” logic. Keep it copyable.
- Avoid spoilers: keep plot out. If something might leak story context, label it clearly or remove it.
- Be respectful: critique ideas, not players. No insults, gatekeeping, or “skill issue” energy.
- Be honest about testing: if you tested on one patch or one platform, say so. Confidence comes from clarity.
Submissions don’t need to be perfect. Clear steps beat fancy writing every time. We’ll help tighten wording, structure, and labels if the core idea is strong.
Spoiler policy
We default to spoiler-safe writing. That means mechanics, systems, and decisions are welcome — plot details are not.
If your tip requires sensitive context, keep it abstract. Focus on inputs and outcomes: what you do and what changes, without naming story beats.
When in doubt: remove nouns, keep verbs. The goal is useful guidance that doesn’t ruin a first playthrough.
What we publish (and what we don’t)
Quick builds: one playstyle, one goal, clean priorities, plus a safe variant.
Patch briefs: what changed → what broke → what to do next. Short and practical.
Settings notes: input, accessibility, performance, readability — with real-world defaults.
We usually skip: drama posts, rage bait, unverified leaks, and “secret OP” claims without steps and context.
Want to contribute? Send a short message with your context and steps. If it’s solid, we’ll help shape it into a clean guide and keep it spoiler-safe.
The best submissions are simple: one tactic, one reason it works, one way to reproduce it. That’s all.