Current compatibility status
RaidMuster is a development preview. The addon, companion and web workflows exist, but real WoW Forever client compatibility and Forever-specific content data still require validation. Fixture data and mocked API checks do not establish that the release client works.
Public planning tools do not depend on the game client. You can use the roster template and launch checklist now, while keeping game-specific readiness rules provisional. This status was documented on 14 September 2026.
How a character observation reaches the website
The addon captures supported character information in game. WoW writes SavedVariables to disk through its normal save lifecycle, such as a reload or logout. The companion reads an approved RaidMuster SavedVariables file and uploads observations to the paired workspace.
The companion must point to a reachable RaidMuster server and the correct account file. It does not make the website a continuous view of the live game. A change made in game is only useful to the website after it is captured, saved and delivered.
Captured time and received time answer different questions
Captured time tells you when an observation was made in game. Received time tells you when the server accepted it. If a player was offline from the uploader for three days, a successful upload today may still contain an observation from three days ago.
For example, a character’s equipment may have changed since that older capture. The safe planning action is to request a fresh observation. A recent delivery should not be presented as a recent in-game check if the underlying snapshot is old.
Missing information is not a failed requirement
A field can be absent because the client does not expose it, because the addon did not capture it or because the current source is incomplete. Those situations are different from a confirmed negative result.
When reviewing readiness, separate ‘known complete’, ‘known incomplete’ and ‘unknown’. If a tool cannot observe a relevant requirement, seek a suitable manual confirmation rather than treating every missing value as a failure.
When a character looks out of date
Start with the simplest checks and stop when you have verified the expected new capture. Repeated uploads of the same old file will not create newer in-game evidence.
- Confirm that the addon loaded in the client being tested and that its supported facets are available.
- Save current addon observations through the normal game lifecycle, then check that the companion watches the correct account file.
- Check the companion’s server, pairing and delivery status.
- In the workspace, verify the linked character and compare capture time with receipt time.
- If a field is still absent, record it as unknown and confirm client support before relying on it.