ForgeKeep content standards

Editorial policy and content standards.

How we create, maintain, and correct independent guides for MMO guild leaders and public ForgeKeep tools.

Last reviewed: 2026-09-20

Purpose and scope

ForgeKeep publishes practical guidance for people who run MMORPG guilds: leaders, officers, raid callers, treasurers, and members who need to understand a shared process. Our public guides focus on operating methods such as event preparation, attendance review, point rules, loot decisions, record keeping, and resource planning. They are written to help a reader make a clearer decision or build a repeatable process, not to fill a search result with a variation of the same advice.

ForgeKeep is an independent guild-management service. We are not affiliated with LORDNINE, Smilegate, Discord, or any game publisher unless we explicitly state otherwise. A guide can discuss a game, feature, or community workflow without representing an official rule, patch note, or endorsement. When a decision depends on current in-game values, regional availability, account rules, or a publisher announcement, readers should check the relevant official source and their current game client.

How we create useful original content

Each guide begins with a concrete reader problem and a practical outcome. For example, a guide about attendance should help a leader define evidence, exceptions, corrections, and privacy boundaries—not merely repeat that attendance matters. We use checklists, decision questions, and worked operating patterns when they make the material easier to apply. The public handbook and guide library are written for people running real groups with limited volunteer time, so we prefer clear steps and explicit tradeoffs over generic promises.

We do not republish third-party articles, databases, patch notes, screenshots, or media as our own work. When a guide refers to a product or external source, we add our own analysis or context and avoid presenting copied material as a ForgeKeep resource. We also avoid publishing private guild records, member information, screenshots, or financial details as public examples. Public guides explain the method; private ForgeKeep workspaces hold the records that authorized guild members choose to manage.

Accuracy, dates, and updates

Every public guide displays publication and update dates so readers can judge its freshness. We review game-specific material when a patch, regional change, or reader report suggests that a factual detail may be stale. General guild-operation principles may remain useful for longer, but they are still reviewed when the product workflow or a commonly reported edge case changes. We update the guide when a revision changes the reader-facing substance; we do not change an update date merely to make an old article look new.

We distinguish between a planning method and a claim about a live game. A calculator can show the result of the values a user enters, but it cannot guarantee a market price, drop, or future patch behavior. A guide can recommend that a leader set a correction window, but it cannot decide a guild dispute. Where a topic has uncertainty, the guide should say what needs confirmation and point readers back to their current in-game text, guild rules, or official publisher information.

Corrections, feedback, and rights concerns

Readers can report an error, missing context, accessibility issue, or rights concern to forgekeepnoreply@gmail.com. Please include the relevant page URL, what appears inaccurate or incomplete, and any source that helps us verify the issue. Do not include passwords, payment information, access tokens, personal contact details for other people, private screenshots, or guild records that you are not authorized to share. We review reports in good faith and correct, clarify, update, or remove material when the evidence supports a change.

Product support and privacy requests follow their own paths because they can involve account or guild information. Visit the Contact page for those requests, and review the Privacy Policy before sending information. Editorial feedback never requires readers to disclose private workspace data in a public channel.

Commercial independence and advertising

ForgeKeep’s public guides are not pay-for-placement articles and we do not accept payment to alter an editorial conclusion. Product pages describe ForgeKeep features; guides explain operational methods and clearly identify related features only where that connection helps a reader evaluate a workflow. A link to a ForgeKeep product page does not make an independent game, publisher, or community responsible for the guide’s content.

If ForgeKeep displays advertising after receiving the required approval, advertising will be clearly labeled and kept separate from the publisher content it accompanies. We will not place ads on private workspaces, authentication pages, legal pages, or screens whose only purpose is navigation, alerts, or a user action. The Privacy Policy explains data-related disclosures, and the site will maintain the disclosures and consent controls required for the regions in which ads are served.