Repository navigation
FlockSync 0.3.5-beta
Pre-releaseFlockSync 0.3.5-beta
Addon fixes
- Fixed stale gear and last-seen information when officer detection was unavailable.
- The addon now saves the logged-in character's own scan regardless of officer catcher status.
- Equipment is captured again at logout or reload, preventing pending scans from leaving removed items in the exported data.
- Collecting other players' guild broadcasts remains restricted to officers.
- Older character updates cannot restore removed equipment or move last-seen timestamps backwards.
Updating the addon
- Download FlockSync-Raider-Only.zip, or FlockSync-Addon-Bundle.zip if you also need the officer helper.
- Exit WoW before replacing addon files.
- Extract into your WoW client's Interface/AddOns directory. FlockSync/FlockSync.toc must sit directly inside the FlockSync addon folder, not an extra nested directory.
- Keep your existing SavedVariables files; do not delete your settings or collected data.
- Log in and allow the addon to load. After changing equipment, use /reload or log out so WoW writes SavedVariables.
- Officers: wait for the desktop app to report a successful sync.
- Click Refresh on the web dashboard to load the latest gear and last-seen information.
If using CurseForge, install main addon version 0.3.2-beta when available. You may need to allow Beta files in the client. Officers using CurseForge for the main addon can obtain the separate FlockSync_AppHelper folder from the GitHub officer bundle.
Last seen represents the character's in-game scan time, not the desktop upload time. Re-uploading an unchanged file does not make an offline character appear recently seen. The web roster currently requires a manual Refresh to show new server data.
Download choices
- FlockSync-Raider-Only.zip: main WoW addon for all guild members. Regular members do not need the desktop app, AppHelper, or a server account.
- FlockSync-Addon-Bundle.zip: the same main addon plus FlockSync AppHelper for officers collecting guild data.
- FlockSync-Setup-0.2.2-beta-x64.exe: Windows desktop installer for officers.
- FlockSync-Portable-0.2.2-beta-x64.exe: portable desktop alternative without installation.
- FlockSync_Pi_Deploy.zip: API/web server source and Docker deployment tooling.
- flocksync-release.json: component versions used by update checkers; published alongside the downloads.
Officers collecting data need the main addon, AppHelper, and the desktop app. Installing AppHelper does not itself grant officer permissions.
Component versions
- Main addon: 0.3.2-beta — updated
- AppHelper: 0.2.1-beta — unchanged
- Desktop: 0.2.2-beta — unchanged
- Server/API/web: 0.2.2-beta — unchanged
Existing desktop, server, and AppHelper installations at these versions do not need reinstalling for this addon fix. All downloads remain included for convenient first-time installation.
New installations
Extract the appropriate addon ZIP into Interface/AddOns, enable the addons, and complete the in-game setup walkthrough.
Officers additionally install the Windows desktop app, configure their full server URL without an /api suffix, select their WoW client folder, and log in with an authorized account.
For server hosting, follow DEPLOYMENT.md in the repository. Copy .env.example to .env, configure unique credentials and your Cloudflare tunnel token, and prepare an existing writable backup directory. Keep the live SQLite database on local storage, not the NAS.
For future server upgrades, preserve .env and data and use sh deploy/update-server.sh. It verifies a database backup before rebuilding or restarting the application. Do not bypass the backup guard or use docker compose down -v.
Update notices
This is a Beta release. Desktop and server update checks compare each component's version, so the new overall tag does not prompt users already running the unchanged desktop/server versions.
Addon notices use release metadata received through desktop sync and guild relay. Beta addon installations can receive beta or stable notices; alpha installations can receive all channels; stable installations ignore previews. Notices appear only at initial character login, so fresh metadata may require a subsequent sync and login.