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. In Discord Server Settings → Members, give only the FarmOps bot the FarmOps Access role. Keep it above Alliance Member and the Storm team roles in Server Settings → Roles. This role opens the private channels the bot uses; do not assign it to members.
- 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. Choose reminders and optional team roles in Roles & announcements.
- Assign your officers and connect a member. Assign Officer yourself in Discord. FarmOps officer access is managed separately. Members start in #connect with
/farmops connectand verify their character; the configured member role opens the alliance channels after synchronization. Existing members can also be assigned Alliance Member manually. - 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.
- Officer
- Private officer coordination. Assign this role yourself.
- FarmOps Access
- Give this role only to the FarmOps bot so it can reach private alliance channels.
- Alliance Member
- Opens alliance channels. Select this as the member role in FarmOps.
- Storm Team A
- Optional Team A label; configure its synchronization in Roles & announcements.
- Storm Team B
- Optional Team B label; configure its synchronization in Roles & announcements.
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.