LancerLogin v1.1.0

LancerLogin 1.1.0 adds dated member labels and configurable attendance rules. It also makes offline kiosk scans easier to recover and review, and keeps rapid scans from showing an earlier member's name.

Bugs fixed

• Concurrent kiosk replay can no longer remove a queued scan before that scan is sent. Queue writes are made durable before cloud delivery.
• A delayed display update can no longer restore the previous member's name after a new scan starts.
• Optional meetings no longer reduce a member's standard attendance rate.
• Dashboard update controls remain above long release notes, and Current and Available show their respective versions during an update.

Features added

• Add overlapping, dated member labels; preview label changes from CSV; and choose meeting audiences by label. Configure required or optional attendance and a weekly mentor target, with consistent results across the dashboard and reports.
• Preview and apply label or activation changes to selected roster members. Administrators can associate labels with Discord roles and run a reviewed manual role sync. Discord commands are registered during installation updates.
• Review rejected kiosk scans and safe rejection reasons behind the local settings PIN. The kiosk retains pending scans and records accepted, duplicate, and rejected outcome counts after replay without blocking later valid scans.

Features removed

None.

Installation and update

1. Back up the entire installation before updating the dashboard. The web update applies database migrations 0030 through 0032 for labels, attendance rules, and Discord role associations. In Settings → Updates, use Back up and begin update, download and confirm the backup, then choose Start update to v1.1.0. Verify the dashboard and API report v1.1.0 after completion.
2. Update the physical kiosk separately to v1.1.0 for the queue and display fixes. As an Administrator, check its status in Kiosks, choose Update to latest stable, and confirm the installed kiosk release. If release lookup or completion is unavailable, use the approved on-device recovery procedure after preserving the local state. Keep pending scans and retained outcomes private; do not restore an old queue automatically.
3. Review any rejected scans in the kiosk's PIN-protected local review page. A rejection record is evidence for an operator to assess, not an automatic attendance correction.