Voting API Docs
A planned voting API for server owners. Nothing is live yet and these docs are a design outline.
Last updated
Metin247 plans to offer a voting API in the future, so server owners could reward players who support their server. To be completely clear: nothing is live. There is no voting system, no endpoint, no API keys and no sample code today. This page describes the design principles we intend to follow.
Why we are planning it
Many Metin2 private servers run vote-for-reward systems. A shared, well-behaved voting service could save owners from building their own and give players one familiar place to vote. We would only build it if it can be done fairly and safely.
Design principles
- Fairness first. Votes would be a community signal and never a paid product. Voting will not be for sale and will not be linked to advertising.
- Privacy-minded. We want to collect as little personal data as possible and be open about what is stored and for how long.
- Owner control. Servers would decide their own rewards. We would only confirm that a valid vote happened, and delivery of in-game rewards would remain the owner's responsibility.
- Simple, documented behaviour. Clear rules on limits, errors and retries, published before launch.
Anti-bot approach
Vote manipulation harms honest servers, so abuse prevention is part of the design from the start. Plans being considered include rate limits, basic challenge checks, detection of suspicious patterns and the ability to discount or remove votes that look automated. We will not publish every detail, because that would help abusers. We do not support botting or vote farming of any kind.
What is not decided
Data formats, authentication method, rate limits and the overall launch timing are all undecided. Any numbers you may see in mock-ups on the site are illustrative only. We will update this page and the changelog when something real exists.
Get involved
Server owners who have opinions about what a voting service should and should not do are welcome to write to [email protected]. General feedback can go to [email protected]. Your input will help shape the documentation before a single line goes live.