minecraftthesift.com
Site information

Contact and Corrections

Help make a page more useful with a precise correction and its supporting source.

On this page
  1. Contact and corrections
  2. Prepare a useful correction
  3. Newsletter and privacy requests
  4. Rights and attribution concerns
  5. Game and account support
  6. Choose the right request
  7. Report a content or version problem
  8. Report a tool or accessibility issue
  9. Resolve a newsletter problem
  10. Explain a rights or attribution concern
  11. What happens after a request

Contact and corrections

Email support@minecraftthesift.com for corrections, broken links, rights concerns, newsletter problems or privacy requests. The mailbox uses Lark. There is no separate contact-upload form on this site.

For information about the site and its maintainer, see About minecraftthesift.com.

Prepare a useful correction

Include the page URL, the sentence or step that needs attention, and a link to the announcement, author page or release file supporting your correction. For a community project, include its author, Minecraft version, loader and file version so similarly named projects stay separate.

For a broken link, include its visible label and the page where it appears. For a display problem, include your browser and device and describe what you expected to happen. FileChecker works locally: we do not automatically receive its file or results, so describe the issue in your message without attaching a private package.

Newsletter and privacy requests

Newsletter confirmation and updates come from subscriptions@minecraftthesift.com. Use the unsubscribe link in an update to stop future messages, or contact support from the subscribed mailbox. A click on Subscribe does not confirm a subscription; follow the confirmation email first. Mail-server acceptance is not proof that an email reached your inbox.

For access, correction or deletion of stored information, email support from the affected address and state what you want changed. We verify mailbox ownership before removing data. Withdrawal and deletion are different: a minimal unsubscribe or bounce/complaint record may be kept to prevent accidental sending until an ownership-verified deletion is completed. Read the privacy notice for the data scope and retention process.

We do not publish an unverified response-time guarantee. Please keep the original conversation together so its status and supporting evidence can be reviewed.

Rights and attribution concerns

Identify the image or passage, its URL on this site, the original work and your relationship to it. Explain the correction or removal you are requesting. Do not send passwords, one-time login codes, account tokens, identity documents or unpublished files unless a specific, necessary verification method has first been agreed.

Game and account support

This independent guide cannot resolve Minecraft purchases, account access, game service problems or a creator’s support queue. Follow the relevant publisher or author’s own support links for those requests.

See the editorial policy for how corrections are reviewed and the privacy notice for how site requests and support messages are handled.

Choose the right request

A clear subject helps us distinguish a content correction from a mailbox problem or a privacy request. You can use a short label such as “Page correction,” “Broken link,” “Tool problem,” “Newsletter,” or “Privacy request,” followed by the affected page or topic. Put the essential question near the start of the message; a long account of every step you took is usually unnecessary.

Request Include Keep out of the message
Incorrect guide Page, passage, project, source Unrelated personal account details
Wrong release or dependency Author, file version, loader, source URL Private download tokens
Broken link Page and visible link label A password-protected replacement
Tool or display issue Browser, device, action, visible result Private mod packages or full device logs
Newsletter problem Affected mailbox and approximate time Confirmation or unsubscribe token
Privacy request Information concerned and requested action Identity documents unless a necessary method is agreed

Report a content or version problem

A statement needs correcting

Quote the shortest passage that identifies the issue and explain the replacement fact. A link to the original announcement or creator release is especially useful. If your evidence concerns another version, say so: the right correction might be a version note rather than removal of the original instruction.

For example, “The installation table links to file A, but the requirement quoted belongs to file B” points to a specific relationship that can be checked. “The guide is wrong” leaves the subject, implementation, and affected step unclear. You do not need technical writing experience; the aim is simply to make it possible to find the same evidence you found.

Two projects have been mixed together

Include both authors when similar names are involved. The Sift’s community projects can use different files and entrance methods, so the useful question is which instruction belongs to which project. A screenshot of a title alone may not identify the release; an author page or file listing usually provides stronger context.

If you are reporting your own gameplay observation, distinguish what happened from what you think caused it. State the project, game version, loader, and visible result. The site can review how that observation affects a guide without treating one attempt as proof of every version’s behavior.

Report a tool or accessibility issue

Describe the task you attempted, the control you used, and the result you expected. Include any short visible error text. For the compatibility checker, the selected edition, project, and loader help identify the branch. For the portal finder, identify the game or author selected. For the note practice tool, explain whether the problem concerns choosing notes, feedback, copying the sequence, or resetting a round.

For FileChecker, describe the package format and whether the problem happened while selecting, reading, or comparing a file. The package itself stays in your browser, so we cannot inspect it merely because you used the tool. Start with a description or a small, nonprivate example agreed through support rather than emailing an entire archive.

Accessibility reports are welcome. Tell us whether the issue concerns keyboard movement, focus visibility, screen-reader wording, zoom, contrast, or a narrow screen. Name the browser and assistive technology when relevant. You can describe where a control became unreachable without supplying medical or other personal information.

Resolve a newsletter problem

If a confirmation email has not appeared, check that the address you entered is the mailbox you are viewing, then inspect its spam or filtered folders. Tell support the approximate request time and affected address if the problem continues. Repeatedly submitting many requests can make the situation harder to distinguish, so keep one support conversation together.

If you did not request a subscription, leave the confirmation unfinished. Receiving a request email and being an active subscriber are different states. Do not forward its secret link into a public issue or social post. Support can investigate a request using the affected mailbox and approximate time without needing a publicly exposed token.

For stopping updates, use the unsubscribe route included in a message or write from the subscribed address. For deleting stored information, say explicitly that you want deletion rather than only stopping mail. These requests have different effects, and support should confirm which one is being handled before changing the record.

Explain a rights or attribution concern

Identify the material on this site and the original work it concerns. Explain whether you are requesting attribution, a factual clarification, a change of presentation, or removal. If you are acting for someone else, describe that relationship and a reasonable way to verify it. A precise location and requested outcome help avoid changing unrelated material.

Concept artwork, factual diagrams, quoted text, and linked third-party pages are different objects. Naming which one is involved helps focus the review. This mailbox can address material published here; it cannot remove files from another creator’s distribution page or change an official game’s store listing.

What happens after a request

We use the information to locate the relevant page, service record, or external source and may ask for the missing detail needed to resolve it. A content report can lead to a correction, an update for a newer release, or an explanation of why two versions differ. A privacy request may require mailbox-ownership verification before data is changed.

The maintainer works in the America/New_York time zone. That identifies the operating context, not a promise of staffed hours or a response deadline. If you send additional evidence, reply in the same conversation so the request and its later details remain connected. Keep account recovery, purchases, and game-service incidents with the publisher or platform that controls them.

Books, crystals and a parchment map inside an imagined stone archive.
Original concept art · imagined setting, not gameplay