LinSy

Key Features:

• Google Calendar integration - Booking, editing and comments - Recurring events (1-7 days)
• Scheduling - Hidden channels (do not appear in the schedule)
• Role configuration (up to 5) - Conflict warnings (+/- 1 hour) - 15-minute alerts and color-coded events
• Auto-thread creation (optional) - Voice channels for events (temporary or fixed) - Participant roster in threads
• Participant list display (optional) - DM summaries with Unsubscribe option - Active Titles with direct links to Events
• Context Menu commands (right-click → Apps) for quick actions
• Utility functions (recovery, notifications, permission checks)
• Localized in Ru, En

Инструкцию на русском Вы сможете найти в дискорд канале бота.

For Users

📅 Creating an event Use /create — a quick form will appear. Fill in the title, date, and optionally a description and repeat interval. The date field is pre-filled with the current server time for convenience. Date format: DD.MM HH:MM — Discord will automatically show each user their local time inside the event. Events can be scheduled up to 30 days in advance.

🔔 Signing up Click the button below the event card to sign up. If roles are configured (e.g. 🛡️ Tank, 💚 Healer, 🔥 DPS) — click the role you want. Click the same button again to cancel your signup.

💬 Comment Press 💬 to add a short comment to your signup. Any signed-up participant can leave a comment — it will be visible to everyone on the event card.

🖱️ Context Menu (right-click → Apps) Right-click any event card to access: Delete, Edit, Confirm Participants, Comment — works in channels, threads, and search results.

📋 /list View the full participant list for any event by its ID.

📬 /me Get a summary of all your upcoming signups sent directly to your DMs.

✏️ Editing & deletion The event author can edit (✏️) or delete (❌) their own event at any time.

For Administrators

⚙️ Initial Setup Before using the bot, grant it the following permissions in the event channel: View Channel · Send Messages · Embed Links · Attach Files · Send Messages in Threads · Create Public Threads · Manage Threads · Manage Channels · Manage Messages · Bypass Slowmode · Read Message History

Then run these commands:

/set_server action:timezone number:3 — sets the server timezone (e.g. 3 for Moscow, -5 for New York). Default is UTC+0. /set_channel action:events — marks the current channel as an event channel.

🌐 Server Settings — /set_server action:status — show server settings. action:language lang:en — set the bot language (en / ru). action:timezone number:3 — set the server timezone. action:logs — receive the server event log for the last 48 hours via DM. action:event_delete number:42 — force-delete an event by ID (must be in the event's channel). action:clear — remove all bot event messages in the current channel.

📢 Channel Settings — /set_channel action:status — show all settings for the current channel. action:events — toggle event channel on/off. action:schedule — hide/show this channel in the schedule. action:threads — toggle auto-created discussion threads on/off. action:members — toggle participant list display in event cards on/off. action:roles value:Tank 🛡️ 2 Healer 💚 2 DPS 🔥 8 /12 — configure signup roles. Use without value to reset.

🔘 Button Settings — /set_button action:show_status — show button settings. action:sticky_button — toggle the sticky create button on/off. action:sticky_permission value:@role1 @role2 — restrict who can use the sticky button. action:toggle_sub_buttons — show/hide management buttons (💬 📝 ❌ ✅) under event cards.

🔊 Voice Settings — /set_voice action:status — show voice channel settings for all channels. action:voice_temp — toggle temporary voice channels (auto-created 15 min before events). action:voice_fixed channel:#voice — link a permanent voice channel to this event channel.

🛠️ Other Commands /set_schedule — designate a channel for the automatic event schedule feed.

💡 Useful to Know In the edit modal, the event author (or admin) can manually add or remove participants by entering their ID or @username. To transfer event ownership, use the field: author:USER_ID Example: author:235085133500252160