For a value correction, send the page URL, item name, current row, expected correction, and the source or observation that supports it. Helpful examples include a game update note, a repeated in-game observation, a wiki reference, or a clear screenshot context.
For a source suggestion, include the page that should be improved, the source title or link, what the source proves, and whether it changes a number, confidence label, availability note, or calculator assumption. LootKit may reject sources that only repeat rumors.
For an outdated page report, include the game, the affected LootKit URL, the update that changed the page, and the specific section that should be reviewed. Reports that identify one row or one paragraph are easier to verify than broad messages like the list is wrong.
For a partnership request, explain the site, tool, audience, and proposed collaboration. LootKit does not accept partnerships that involve real-money trading, free Robux claims, account trading, marketplace promotion, or misleading affiliation claims.
Use a clear subject such as LootKit correction, LootKit source suggestion, LootKit outdated page report, LootKit partnership request, or LootKit policy request. Include enough context for the page to be reviewed without guessing.
LootKit prioritizes corrections that affect player decisions, outdated game update references, privacy requests, and policy requests. Not every suggestion will be published, and corrections may be grouped into the next update cycle when evidence is incomplete.
A useful correction request says: the Grow a Garden Mutation Values page lists this multiplier, the latest update or repeated in-game check suggests a different result, and this is the exact row that should be reviewed. That gives LootKit enough context to check the source, update the confidence label, or leave a visible caution.
Contact messages can improve visible pages, but they do not create a private support ticket with Roblox, any game developer, or an item marketplace. LootKit cannot verify account ownership, settle trades, recover lost items, or confirm live server inventory.
Do not send Roblox passwords, payment details, private account information, scam offers, free Robux promotions, real-money trading proposals, or requests to manipulate values. Those messages are not useful for editorial review.
A useful source suggestion says which LootKit page it supports, whether it changes a value, multiplier, availability note, or confidence label, and why the source is stronger than the current note. A source that only repeats a rumor may still be logged, but it will not be treated as verified evidence.
Reports that affect player decisions are reviewed first: wrong calculator assumptions, outdated event availability, misleading confidence labels, and broken internal paths. General opinions, broad complaints, and unsourced claims are slower because they require more manual checking.
Before sending a report, include the exact LootKit URL, the row or section name, what you believe changed, why it matters to a player decision, and what source supports the change. This keeps the review focused and reduces back-and-forth. If the issue is urgent, explain what player action could be affected and whether the current page could mislead a trade, calculation, route, or correction before publishing.