Where to Report Issues with the WACUP Preview Build

Report problems with the WACUP Preview build in the preview discussion forum on getwacup.com. The site states plainly that the preview is pre-release software, so issues are expected and belong in that forum rather than in general support channels. Before you post, install the preview into its own directory separate from your existing player — the site recommends this so problems stay isolated and easier to describe.

How to report an issue

1. Confirm which build you are running. The current public preview is WACUP Preview v1.99.55.25130 (x86 and x64, dated September 30 2026). Include this build number in your report; it is the fastest way for others to tell whether your problem is already known.
2. Check the changelogs first. The site links changelogs for both x86 and x64. If a fix or a known issue is listed there, your report may already be covered.
3. Reproduce it in a clean install. Because the preview is meant to be installed into its own directory, a problem that only appears alongside an older install is useful information — say so explicitly.
4. Post in the preview discussion forum. This is the location the site names for reporting issues found in the preview build.
5. Describe what you did, what you expected, and what happened. Add your build number, whether you are on x86 or x64, and any plug-ins involved, since WACUP is built around a plug-in system.

What not to use

The limited-access beta (also build #25130, September 30 2026, x86 and x64) is restricted to registered beta testers. The site says it is intentionally kept narrow to avoid problems from people who don't pay attention. If you are not a registered beta tester, report against the public preview instead.

Quick reference

If you want to help beyond reporting, the site lists beta testing as an option and points to Patreon, PayPal, Ko-fi, and non-financial ways to support development.