How we create, review, update, and correct public guides about Minecraft server hosting and the PortalMine platform.
PortalMine publishes educational content to help users make informed server-management decisions. Content should solve a real problem, explain limitations, and avoid exaggerated claims. Pages are not created solely to display advertising or repeat keywords.
Public guides are attributed to the PortalMine Operations & Documentation Team when they are produced and maintained collaboratively. The team name does not imply official affiliation with Mojang Studios or Microsoft.
Product-specific claims are checked against the current PortalMine interface and behavior. General server-administration guidance is reviewed for clarity, safety, and consistency with common Java and Bedrock server practices.
Server performance varies by software, world, plugins, entities, player behavior, hardware, and network conditions. We avoid presenting one memory value, view distance, plugin count, or player count as universally correct. When an answer depends on context, the guide should explain the variables and recommend a safe testing method.
Pages display a reviewed or updated date when practical. Material corrections may be made when the product changes, a broken instruction is found, or a reader provides reliable evidence. Minor grammar and formatting edits may not receive a separate notice.
Correction requests should include the URL, section heading, current wording, and explanation. Send them to support@portalmine.com.
Advertising should be visually distinguishable from editorial content and should not determine conclusions in guides. PortalMine may earn revenue from advertisements, but editorial pages should remain useful without requiring an ad click. We do not encourage invalid clicks, forced interactions, or misleading navigation.
Minecraft is a product and trademark of Mojang Studios, a Microsoft company. PortalMine is independent and is not affiliated with or endorsed by Mojang Studios or Microsoft. References to products or software are for identification and educational purposes.
Technical pages use the organizational byline “PortalMine Operations & Documentation Team.” This is intentional: the content is maintained collectively, and PortalMine does not invent named authors or credentials. The authors page explains the team’s review scope and correction process.
Workflow diagrams are labelled as diagrams and are not presented as live screenshots. Configuration suggestions are described as starting points, not guaranteed performance results. Controlled benchmarks are only claimed when test conditions and results are documented.
Dates change only when a page receives a meaningful review. Small formatting edits do not justify presenting an article as newly researched. Material corrections should explain what changed when the previous wording could have caused a server owner to make a harmful decision.
Automation may help organize drafts, check internal links, or identify missing headings. Published technical claims must still be reviewed against PortalMine behavior and the cited primary documentation. Generated text is not treated as evidence.
Technical claims should be supported by direct product behavior, official project documentation, release notes, configuration references, reproducible tests, or clearly identified operational experience. Community discussions can reveal symptoms and edge cases, but they should not be treated as the sole authority for security, compatibility, or destructive recovery instructions.
Minecraft server behavior changes across editions, protocol versions, server software, Java runtimes, plugins, mods, and hosting controls. A review date indicates when the page was last checked, not a guarantee that every third-party dependency remains unchanged. Content is prioritized for review when a linked workflow, platform control, major game version, or widely used dependency changes.
A material update changes the technical procedure, scope, risk, compatibility conclusion, or product behavior. These changes should trigger a renewed review date. When a page cannot be kept accurate, it should be revised, redirected to a stronger resource, or removed rather than preserved as stale search content.
Product pages can explain PortalMine benefits and limitations. Guides should remain task-centered and should not force a product claim into unrelated troubleshooting. Advertising, where present, does not determine editorial conclusions, and content should remain useful even when the reader is diagnosing a non-PortalMine Minecraft server.
Time-sensitive Minecraft release facts are checked against official Minecraft, Mojang, Microsoft, or project documentation. PortalMine separates sourced facts from operational recommendations and records a visible review date.