Release Channels
Every public HWH userscript has a stable channel. Some scripts also get a beta channel when a planner, UI flow or risky behavior needs testing before stable release.
Stable
Section titled “Stable”Stable is the channel for normal daily use.
- File:
script.user.js. - Updates: through
script.meta.js. - Install sources: GreasyFork, GitHub raw and direct download from the site.
- Rule: stable receives changes that passed checks and do not look like an experiment with a glowing red button.
Beta is a separate userscript with a separate file. It does not replace stable automatically.
- File:
script-beta.user.js. - Updates: through
script-beta.meta.js. - Install sources: GitHub raw and direct download from the site; GreasyFork is added separately when the page exists.
- Rule: beta is for testing new behavior, and reading result reports is not optional.
Right now HWH AutoFarmer is published to beta as 1.8-beta.2. This channel covers the new planning, UI and farming behavior while stable remains the normal safe entry point.
Direct Downloads
Section titled “Direct Downloads”The site publishes ready .user.js files in a static directory:
- Stable:
/downloads/stable/<script>.user.js - Beta:
/downloads/beta/<script>-beta.user.js
Use these links when GreasyFork is unavailable or when you want to install directly from the documentation site. Tampermonkey opens the normal install screen, just like it does for a raw link.
GitHub Raw
Section titled “GitHub Raw”GitHub raw remains the technical channel for @downloadURL and @updateURL. It is useful for automatic updates and the public mirror, while the site shows a separate Download .user.js button for humans.
Do Not Run Two Channels Together
Section titled “Do Not Run Two Channels Together”Stable and beta of one script can both exist in Tampermonkey, but they should not be enabled at the same time. Disable stable before testing beta, or disable beta before returning to stable. Two AutoFarmers spending resources together is not A/B testing, it is request chaos with a nicer hat.
When To Use Beta
Section titled “When To Use Beta”Use beta when:
- you want to test a feature before stable;
- you are ready to inspect the result window and diagnostics;
- you can quickly return to stable;
- you understand which resources the script may spend.
Do not use beta when you need a quiet daily run without surprises. That is what stable is for: boring, therefore useful.
