suggestions & reports.

suggestions and reports are separate records with separate channels and workflows. a suggestion is an idea meant to be posted, voted on, and answered in a community-facing suggestion channel. a report is a complaint about a member, sent to a staff-only report channel. configure both destinations before asking members to use them.

::suggestions

the post contains the idea, its numbered id, status, vote tally when enabled, and the submitter unless anonymous suggestions are on.

::reports

the post contains the reported member, complaint, status, and reporter visibility chosen by the report anonymous setting.

neither system is a substitute for a ticket. use a report when staff must assess another member’s conduct; use a support ticket when the member needs an ongoing private conversation.

anyone may submit an idea once an administrator has set the suggestion channel. havoc creates a numbered post there, then confirms where it went. when voting is enabled, the post has up and down controls and keeps the tally on the suggestion card. the controls remain attached to old posts after havoc restarts.

,suggest add a weekly community event
/feedback suggest suggestion: add a weekly community event
,suggestion status 12
/suggestion status id: 12

suggestion configuration requires manage server. set the destination first, then decide whether the post identifies its author and whether members can vote. running the base config command is a quick check before publishing the feature.

staff with manage messages move a suggestion from its initial state to approved, denied, or implemented. an optional reason becomes the visible staff response. approving says the idea is accepted; implementing says the work is complete. denying closes the idea without claiming it will happen.

a report names one member and requires a reason. with the prefix form, havoc first removes the command message so the target and complaint do not remain in public. if it cannot remove that message, it refuses to file the report; grant havoc manage messages in the submission channel or use the slash form, whose confirmation is private.

,report @member repeated harassment in #general
/report run member: @member reason: repeated harassment in #general

havoc rejects self-reports and reports targeting bots. after a successful prefix submission it tries to send the confirmation by direct message, with a short non-identifying channel confirmation as a fallback. the full complaint is posted only in the configured report channel.

the report channel must be staff-only. havoc refuses a channel readable by everyone or by ordinary roles, because the complaint and the reported member belong in a restricted destination. report anonymous mode has a narrower meaning than suggestion anonymity: it hides the reporter on the staff-channel card, but authorized staff can still reveal the identity with report view.

every report receives an id. staff can claim an open report to show who is handling it, inspect the reporter privately, then resolve it as handled or deny it without action. optional notes remain with the final state. these commands require manage messages plus access to the report channel.

prefer resolve or deny when an audit trail matters. deletion is for duplicates, tests, or content that must not be retained; once deleted, the numbered report and original staff post are gone.