Editorial Policy

This policy describes the editorial standards for FilterBlade’s original tools, guides, and articles. The site is an independent, unofficial fan-made resource, not an official source for Path of Exile and not a service operated by Grinding Gear Games, NeverSink, or filterblade.xyz. Editorial usefulness depends on accurate scope: readers should be able to distinguish a documented language rule, a suggested workflow, a simplified tool result, and an observation actually checked in a client.

Sources and factual claims

For filter-language behavior, prefer the official documentation over recollections or copied community examples. A community post can provide useful context, but its presence on an official forum does not automatically make its instructions staff-authored. When documentation leaves a question open, describe the uncertainty. Do not silently resolve a disputed point by presenting the most convenient interpretation as established fact.

Time-sensitive claims require a source and a review context. A page that records a documentation review has not necessarily been tested against the latest client patch. Installation instructions should identify the platform and verification limits where these matter. Do not infer console, macOS, Linux, or PoE 2 compatibility solely from a Windows example or a similar-looking interface in another game.

Original examples and starter data

Examples should be written to teach a specific concept, such as rule order, a boundary condition, or a readable style. They must not be presented as a complete filter for every character. The bundled presets use original starter data rather than copied NeverSink rules or economy feeds. Names such as Strict describe an intended attention tradeoff; they do not establish a universal value ranking or a guaranteed correspondence to another author’s preset.

Constructed item examples should be distinguishable from text copied from an actual item. Simplifying an example is acceptable when the simplification is explained and does not remove the behavior being taught. Never invent test results, client screenshots, market values, usage statistics, awards, testimonials, or endorsements. A demonstration may show how to run a test without claiming that the test has already been performed in the game.

Tool outputs and verification language

Use precise status language. A syntax check covers the implemented grammar checks. An item evaluation covers supported conditions and supplied properties. A contrast calculation measures a modeled color relationship, not universal accessibility. A text diff identifies textual changes, not gameplay significance. Reports must preserve unknown states for unresolved imports, unsupported semantics, and missing information instead of converting uncertainty into a pass.

Articles should encourage separate checks for syntax, intended behavior, and client loading. Important recommendations should include a recovery path such as saving a known-good file. Do not describe browser-only analysis as official validation. Where a tool cannot inspect local assets, explain that the asset is unverified unless the user has supplied suitable evidence; do not tell the reader that a custom sound is absent merely because the browser cannot see their folder.

Authorship and accountability

No named owner’s biography or independently verified expert credentials were supplied with this content package. Editors must not manufacture them for an author box or structured data. A publishing account can be shown as the publishing account without claiming professional qualifications. If a real contributor later supplies a biography, it should accurately describe their role and relevant experience, with consent for any personal information displayed.

Editorial responsibility includes checking that visible copy matches enabled features. Do not advertise OAuth, account synchronization, live prices, guaranteed mail delivery, or a tested game patch when those capabilities or observations do not exist. A change to the host, analytics provider, contact handling, or commercial model may also require changes to the site’s legal notices and disclosures rather than only an update to a marketing sentence.

Corrections and update dates

Send correction reports through Contact, including the affected URL, the disputed statement, and a reliable source or minimal reproducible example. Avoid including secrets or unrelated personal data. Reports are assessed by severity, reproducibility, and available evidence. There is no guaranteed response deadline. A reported issue can remain unresolved while conflicting documentation or an unavailable client environment prevents a reliable conclusion.

When correcting a material error, explain the practical effect where useful and update the article’s review information honestly. A spelling correction is not a new game-version verification. A change to an example should prompt a review of related tool instructions and internal links. If previous advice could hide wanted items, the correction should make that risk clear rather than burying the change in unrelated copy.

Commercial influence and reader trust

The starter site does not include fabricated sponsorships, paid reviews, or affiliate claims. If the operator later adds advertising, affiliate links, sponsored material, or gifted products, those relationships need clear disclosures close to the relevant content. Commercial arrangements must not be disguised as independent testing. Recommendations should explain their reasoning and limitations even when there is no financial relationship.

Reader trust is better served by a useful limitation than by an impressive but unsupported claim. See About for the site’s scope and Disclaimer for practical reliance limits. The aim is not to eliminate every possibility of error. It is to make the evidence, uncertainty, and correction process visible enough that readers can make informed decisions about their own filters.