How We Test

Separate three kinds of evidence

Hands-on tested

Actions actually performed on a specified plan, backed by dated records of the setup, procedure, observations, and limitations. This label applies only to what was tested.

Specifications checked

Claims checked against identified documentation on a stated date. This does not establish real-world performance or reliability.

Not yet verified

Adequate evidence is missing. The claim must not be presented as a measured result.

Document a reproducible setup

Record the exact host and plan, region, access or payment arrangement, software and Java versions, world settings, player count, test duration, and modpack version where applicable. State which hardware or shared-resource claims cannot be independently checked.

Planned practical checks

1. Purchase and setup: document charges, provisioning, and beginner-facing steps.
2. Management: check joining, permissions, allowlisting, and the supported modpack installation path.
3. Performance: record workload, tools, repeated observations, and variation. Do not extrapolate a short run into long-term uptime.
4. Recovery: back up and restore a disposable test world, not the only copy of a valuable world.
5. Support and exit: document real interactions, export options, and the cancellation terms checked. Do not invent support tickets.

Prices, recommendations, and corrections

Check the exact plan, currency, initial and renewal prices, billing term, upfront payment, and known extras. Display the check date. Unknown amounts remain unknown, and a monthly equivalent is not monthly billing.

Recommendations must explain the reader’s need, trade-offs, and evidence. No score or winner is assigned without a justified method. A price update is not a new performance test.

A “Reviewed by” credit requires an actual review. The editorial signature is not evidence of testing. Free access, sponsorship, or commissions must be disclosed if they occur. Report corrections through Contact.