LancerLogin v2.0.1

LancerLogin v2.0.1

This release fixes setup problems in the optional integrations. Discord bot setup no longer fails when you add the Interactions Endpoint URL, an installation that uses passwords can turn on Google sign-in, and Google Calendar, Discord and Resend setup explain each step and each failure more clearly.

Bugs fixed

• Discord setup no longer fails with "the specified interactions endpoint URL could not be verified". The Interactions Endpoint URL now appears after you choose Save credentials, because Discord checks the address as soon as you save it in the Developer Portal.
• Discord setup now lists every permission the bot needs, including Create Public Threads for absence-notice threads and Create Events for calendar sync. It also explains that a private anomaly report channel needs the bot added to it.
• Installations created with Username and password can now turn on Google sign-in. Admins can add or change a user's Google email in Settings > Access, and verifying Google requires an active Admin whose email matches.
• Google sign-in and Google Calendar setup show the exact redirect URI the installation uses, and their failures appear as a message on the Settings > Integrations card instead of a raw error page.
• Google Calendar refuses an authorization that leaves out one of its two permissions, and explains how to fix it.
• Resend errors now include Resend's own reason, such as an unverified domain.
• The Active roster member checkbox in Edit roster member and the Block re-contests after rejection checkbox display correctly.

Features added

• Google Calendar can be re-authorized from its card with Re-authorize Google Calendar, without re-entering the client ID and secret. The card warns when authorization needs renewing.
• Setup steps for Google Calendar and Resend email on the documentation site, and an updated Create the Discord bot section.

Features removed

• None.