Gameheim

Send project events to Discord and Slack channels

For the LEAD of a project, or whoever manages its integrations. Connect a Discord or Slack channel with its incoming webhook, choose the events, and the team sees what happens in the project where it already talks. The guide covers what each message contains, how changelists reach a channel on Perforce and what to do when a channel stops receiving.

By Gianmarco Virzì, co-founder and lead developer of Virsion · Updated · 5 min read

The team talks in one place, the project lives in another

Many studios run their day on Discord or Slack. A new crash, a reopened bug or a build that just broke is news the team needs right away, and nobody wants to keep a second tab open to catch it.

Pasting updates into a channel by hand does not last, and a bot that posts everything turns the channel into noise. The messages also need care: a project carries file paths, descriptions and bug details that should stay inside the studio.

How Gameheim posts in your channels

Each channel you connect gets the events you choose for it, in English, Italian or Japanese. Events that arrive close together become one message, with a link to the right page in Gameheim. Nothing comes back from the channel: Gameheim only posts.

EventWhat the message shows
Changelists (Perforce)Number, author, the first line of the description, how many files the channel can see
Commits (Git)Short commit id, author, the first line of the message, number of files
New bugsKey, severity and title
Reopened bugs and crash regressionsKey and title
New crashesTitle of the crash group
Milestones reachedMilestone and phase
Protected path approval requests (Perforce)Who asked, the changelist, the number of files and the approvals needed
Broken CI buildsJob, platform and configuration, the revision of the failed run and the authors of the changes since the last good build
Stale locksWho holds locks past the time limit, and how many
Forced lock releasesWho asked to release the locks of whom, and how many
Project and organization announcementsTitle, author and a link, for announcements published with a notice to the members

How to connect a Discord or Slack channel

Before you start
  • The Integrations permission on the project (integrations:manage). LEAD and ADMIN have it; a LEAD can give it to a custom role.
  • Your organization's plan includes Discord and Slack channels.
  • The rights to create an incoming webhook in the Discord channel or the Slack workspace.
  1. Copy the webhook URL of the channel

    • Discord: channel settings → Integrations → Webhooks → Copy Webhook URL.
    • Slack: create an app with Incoming Webhooks and copy the webhook URL of the channel.
    Note:Whoever knows the URL can post in the channel. Gameheim stores it encrypted and never shows it again after you save: the page keeps only its last characters.
  2. Add the channel in Gameheim

    Open Integrations, choose Discord & Slack and click Add a channel. Give it a name, pick the service, paste the URL, choose the events (locks and announcements have their own groups) and the language of the messages, then Save.

  3. Optional: only some folders

    Under Only these folders, list one folder per line: a depot folder such as //Ocean/main/Content/Maps/... on Perforce, a repository folder such as Content/Maps on Git. A changelist, a commit or a lock then goes out only if one of its files is inside. The folders themselves never appear in the messages.

  4. Perforce: choose the group the channel reads changelists with

    On a Perforce project, changelists reach a channel through a Perforce group: the channel receives only the changelists that group can see. A Perforce admin of the project chooses the group under Changelists and clicks Use this group. The Gameheim extension on the Perforce server checks it within a few minutes.

    Note:A group with admin or super access is refused. Without a group, or while the Gameheim extension is not running on the server, the channel still receives the other events but no changelists.
  5. Send a test message

    Click Send a test message and check the channel. From then on the channel receives the events you chose, from the moment it was switched on.

Who decides what a channel can see

A channel is read by people who may not be in the project, so what it receives is decided by the project, not by whoever reads it. Changelists follow the Perforce group chosen by a Perforce admin. Commits go out only when the hosting's webhook delivered them, and only if whoever sets up the channel can read the repository in Gameheim. Bug and crash events need the permission to read bugs, approval requests the permission to approve protected submits, broken builds the permission to read the changelists, and announcements the permission to read announcements.

Troubleshooting: a channel stops receiving

What you seeWhat to do
Switched off: the webhook no longer existsThe webhook was deleted in Discord or Slack. Create a new one and paste its URL.
Switched off: paste the webhook URL againThe service refused the webhook. Paste a new URL.
No changelists, other events arriveCheck under Changelists that a group is chosen and active, and that the Gameheim extension runs on the Perforce server.
Commits from Bitbucket or Azure DevOps do not match a folderThese hostings send commits without their files, so a folder filter cannot match. Remove the filter for that channel.
Discord and Slack channels are not included in your organization's planThe function is not part of the current plan. The channels you saved stay saved and start again when the plan includes them.

When a channel is switched off, the people who manage the project's integrations get a notice.

Frequently asked questions

Can a message reveal our file paths?

No. Messages carry numbers, authors, titles, the first line of descriptions, counts and links to Gameheim. File paths and file contents never leave Gameheim.

Will a busy day flood the channel?

No. Events that arrive close together become one message, and a long list shows the first few plus a count per kind of event.

Can the channel send anything back to Gameheim?

Not through these webhooks: they only post. To talk both ways, link a Gameheim topic to a Slack or Discord channel: see Link a topic to a Slack or Discord channel.

How many channels can a project have?

Up to ten, each with its own events, language and folders.