Got questions? Join the Discord.

Join

Contact Us

Kingshot Mastery is an independent fan site built by players, for players. Every guide on this site is written from real gameplay experience — we test mechanics, run the numbers, and update content when the game changes. If you have spotted an error, have a suggestion for new content, or want to share something useful from your own alliance experience, we want to hear from you.

What We Can Help With

  • Guide corrections — If a mechanic has changed or data in a guide is wrong, send us the correct information and we will update the page within 72 hours.
  • Content suggestions — Missing a guide for a specific event, hero, or mechanic? Tell us and we will add it to the content roadmap.
  • Tool feedback — Found something off in one of our calculators? Let us know the inputs you used and the expected result so we can investigate.
  • Partnerships — Content creators, alliance leaders with large communities, or websites relevant to Kingshot players are welcome to reach out.

How to Reach Us

All messages are read. Response times vary — corrections and factual errors are prioritized and typically addressed within 24–72 hours.

Get in Touch

For general questions, partnerships, content corrections, or guide suggestions.

contact@kingshotmastery.com

Frequently Asked Questions

When are guides updated?

We review all content within 72 hours of major patch notes releases. Minor adjustments are made weekly based on community feedback and in-game testing.

Can I write for you?

We are occasionally looking for specialized experts — particularly players with deep knowledge of KvK coordination, high-level PvP, or endgame gear optimization. Send us a sample of your writing or strategy analysis.

Is this site official?

No — Kingshot Mastery is a fan-made resource, entirely independent of the game developers. We are not affiliated with or endorsed by the creators of Kingshot.

How do I report a broken tool or calculator?

Email us with the calculator name, the inputs you used, what result you got, and what you expected. Screenshots are helpful if the issue is visual.