Builderman
  • ℹī¸Overview
    • What is Builderman?
  • đŸĨ‡First Setup
    • Pre-Requirments
    • Channels & Permissions
    • Custom Settings
  • 📄Commands
    • Default Users
      • /suggest
      • /report
      • /help
      • /invite
    • Approvers
      • Incoming suggestions
      • Incoming bug reports
    • Developers
      • /queue
      • Processing suggestions
      • Processing bug reports
    • Managers
      • /list-games
      • /add-game
      • /delete-game
      • /publish
      • /blacklist
      • /status-embed
    • Administrators
      • /holding-channel
      • /todo-channel
      • /poll-channel
      • /update-channel
      • /update-ping
      • /manager-role
      • /dev-role
      • /approver-role
      • /blocked-role
      • /scope
      • /language
  • ❔FAQ
    • Why does the bot not work after the migration?
    • Slash-Command don't appear
    • What are "scopes"?
    • What does the report Function?
    • My Files are not accepted
Powered by GitBook
On this page
  • General Information
  • Requirments
  • Command Details

Was this helpful?

  1. Commands
  2. Managers

/publish

Should be the same like Developer and Approval

Previous/delete-gameNext/blacklist

Last updated 3 years ago

Was this helpful?

General Information

With the /publish command, managers and administrators can publish project (game) updates with all new features, all bug fixes/changes, and all completed suggestions and bug-reports in the publishment queue.

Requirments

  • There must be at least one project (game) on the server (/add-game)

  • The User must either have the Manager Role (/manager-role) or be an Administrator

Command Details

To execute the command, the name of the project (game) and the version must be defined. Example /add-game game:MyGame version:1.0

Additionally, if no default update-channel has been set, the channel where the update should be set has to be defined. Example /add-game game:MyGame version:1.0 channel:#update-channel

Upon successfully executing the command the user will receive a Direct Message from the bot asking for additional specifications.

First, the user is asked to state what has been added to the game, this can be done by simply sending it to the bot via Direct Messages. The bot will react to the message with a to confirm that it has been added, the feature will also be added to the embed in the initial message.

After the user is done with their inputs, they can click the "Done" button or write "done" to proceed. Upon doing so, the user is now asked to state what has been changed in the game, this can be done by simply sending it to the bot via Direct Messages. The bot will react to the message with a to confirm that it has been added, the feature will also be added to the embed in the initial message.

Once the user is satisfied with the list, they can press the "Done" button or write "done" again to publish the update. A message with all new features, changes, and completed suggestions and bug-reports in the publishment queue will be sent in the defined text channel by the bot. Depending on the settings a ping will be sent with the message.

Note that at any time, the user can revert the current input by pressing the "Revert Input" button, or cancel the entire update by clicking the "Cancel" button or writing "cancel".

📄
✅
âœ