Anticheat Trial and Refund Checklist

Short answer

Before you buy or renew an anticheat, confirm the trial length, refund window, refund conditions, feature scope, and licence scope in writing. Run a dated staging test inside the window, record every result, and decide several days before the refund deadline. Keep the vendor's terms and your test log together, so a refund request has evidence behind it.

Get the terms in writing

Vendors describe trials and refunds in different places. Save the terms as they stand on the day you pay, with the date, and compare them with any sales chat answer.

Plan the trial around a decision date

A fixed date gives the test a finish line. Without one, trials drift until the refund window has closed.

• Set the decision date three working days before the refund deadline.
• Write three to five pass or fail requirements, using your requirements document or the Minecraft anticheat evaluation checklist for server owners.
• Book staff time for the test, including review of alerts.
• Decide who can approve a refund request, and what evidence they need.

Run the trial in order

Keep these steps in this order. Installing on production first leaves no clean baseline to compare against.

• Back up the current configuration and record the current server and plugin versions.
• Install the trial on a staging server, not production.
• Run your scripted scenarios and the latency steps you defined.
• Record each alert, mitigation, and staff review minute in the trial log.
• Test the uninstall path and confirm the server starts cleanly without the plugin.
• Write the decision and its evidence, then send any cancellation or refund notice before the deadline.

Keep one trial log

A refund request is easier to settle when the log shows dates, versions, and the vendor's answers. Use one log per trial, and keep it with your purchase records.

Trial log: [plugin name and version]
Vendor terms saved: [file name, date saved]
Trial start: [YYYY-MM-DD, source of the start rule]
Refund deadline: [YYYY-MM-DD, time zone]
Staging server: [name, Minecraft version, proxy, plugin list]
Scripts run: [name, count, dates]
Latency steps: [step, delay, loss]
Alerts: [count per script, check name]
Mitigations: [count, type]
Staff minutes: [total review time]
Legitimate scripts punished: [yes or no, details]
Decision: [buy, renew, cancel, or extend]
Approver: [name, date]

Uninstall and cancel cleanly

Test removal before you buy. A plugin that cannot be removed cleanly is a cost the refund terms may not cover.

• Remove the plugin jar and restart the staging server.
• Delete any data folder only after you have copied the files you need.
• Revoke any webhook or API token you gave the plugin.
• Remove settings that other plugins used to point at it.
• Save the server log that shows a clean start without the plugin.

Watch renewals and price changes

Auto-renewal is a common reason owners keep paying for a plugin they no longer run. Put the renewal date in your calendar and check the vendor's current price before it renews. Keep the old and new terms, so any price change can be compared with the terms you bought. Ask whether the renewal price is locked for a term, and write the answer down.

What the trial cannot show

A trial shows how the plugin behaves on the server and scripts you used. It does not measure detection quality across all players. It also does not show performance at your player count unless you test at that count. If the trial is limited, plan the test around those limits and write them in the log. FairPlay's current terms are on its BuiltByBit listing. Read them there, because seller-published terms can change.