An alliance server, ready for your next event.
The FarmOps Alliance Starter gives members a place to connect, officers a private planning area, and everyone a clear home for events and Storm teams.
The template is free to use. The connected FarmOps Discord Bot is included in Alliance Pro and currently limited to BETA pilot access.
Where everything belongs
Events share one channel, with a separate discussion thread per event when enabled. Members can reply in event threads and use signup buttons. Team A/B channels are visible to all alliance members; the team roles are optional labels.
Finish these steps after creating your server
- Create and name your server. Open the Discord preview on desktop or in a browser. This creates a new server; templates cannot merge into an existing one. If you already have an alliance server, use the layout as a guide and keep your current channels.
- Install FarmOps from your alliance’s Discord page. In Connection & channels, choose this new server. Discord asks for the specific permissions listed below. The template itself does not install the bot or connect an alliance.
- Give the bot access to the private channels. Two moves, both unavoidable: Discord adds a new bot at the bottom of the role list, and a template cannot hand it a role. In Server Settings → Members, give only the FarmOps bot the FarmOps Access role — that is what opens the private channels, so never assign it to members. Then in Server Settings → Roles, drag FarmOps above Alliance Owner, because Discord never lets a bot assign a role sitting above its own. Skip either and FarmOps will report the channels or roles as out of reach.
- Select the template channels in FarmOps. Refresh channels and permissions, then select Use template channels and member role. Review #events, #announcements, #officer-alerts and Alliance Member. Enable the integration and save. In Roles & announcements, choose Set up all alliance roles. This reuses the template’s roles, creates any missing roles and saves every staff, R1–R5, Storm team and Event Participant mapping together. The configured officer alerts channel also receives access for the staff roles.
- Connect your staff and members. Invite staff and choose their roles in FarmOps. Once they connect Discord, their Owner, Manager, Admin or Officer role follows automatically. Game ranks are separate and require a verified character. Members start in #connect with
/farmops connectand verify their character; the configured member role opens the alliance channels after synchronization. Staff changes queue a sync, and all roles are checked every five minutes. Roles FarmOps assigned are removed when eligibility ends; manually assigned roles stay under your control. - Publish your first event. Check the event card in #events, submit a response and confirm it appears in the FarmOps calendar. For Storms, select the roster in the Storm planner and complete the game’s own registration.
- FarmOps Access
- Give this role only to the FarmOps bot so it can reach private alliance channels.
- Alliance Owner
- Follows alliance ownership in FarmOps. Opens the private staff channels.
- Manager
- Follows the Manager role in FarmOps. Opens the private staff channels.
- FarmOps Admin
- Follows the Admin role in FarmOps. Opens staff channels without Discord Administrator permission.
- Officer
- Follows the Officer role in FarmOps. Opens the private staff channels.
- R5
- Follows your verified character’s R5 rank in the FarmOps roster. Game ranks do not grant staff access.
- R4
- Follows your verified character’s R4 rank in the FarmOps roster. Game ranks do not grant staff access.
- R3
- Follows your verified character’s R3 rank in the FarmOps roster. Game ranks do not grant staff access.
- R2
- Follows your verified character’s R2 rank in the FarmOps roster. Game ranks do not grant staff access.
- R1
- Follows your verified character’s R1 rank in the FarmOps roster. Game ranks do not grant staff access.
- Alliance Member
- Opens alliance channels. Select this as the member role in FarmOps.
- Storm Team A
- Follows published Team A participation in the 48 hours before the event.
- Storm Team B
- Follows published Team B participation in the 48 hours before the event.
- Event Participant
- Temporary role for published event participation. Removed when participation ends.
Permissions for the Discord Bot
Discord lists these permissions before you connect. FarmOps uses them for the channels, roles and events you configure.
- Event cards and reminders
- View Channels, Send Messages, Embed Links and Read Message History.
- Verified members and team roles
- Manage Roles. The FarmOps role must sit above the roles it assigns.
- Event discussion threads
- Create Public Threads, Send Messages in Threads and Manage Threads, including closing threads when events finish.
- Discord Scheduled Events
- Create Events, which also lets FarmOps update or remove the events it created.
What a template carries over
Discord copies the channel layout, topics, roles and channel permissions. Messages, members, bot installations, game verification and FarmOps settings do not become part of your new server. Setup instructions live in the channel topics so they remain available after creation.
The starter uses standard text and voice channels. Discord does not transfer Community channel types such as Forums, Announcement channels or Stages. The #announcements channel here is a normal text channel. Later template updates do not change a server you already created.