Snippets

Snippets are short, reusable replies you can send with one command. They keep tone consistent and reduce typing during busy periods. Snippets are helpful, but they should never replace thinking. Use them as a starting point, not a script.

Viewing Snippets

• !snippets lists all available snippets.
• !s <shortcut> shows the text for a specific snippet.

Creating Snippets

Create a snippet when a response is both common and predictable.

• !s <shortcut> <text> creates a new snippet.

Example: !s hi Hello, thanks for reaching out to Lane Esports. How can we help?

Using Snippets

Snippets can be sent normally or anonymously depending on context.

• !!shortcut sends the snippet to the user.
• !!!shortcut sends the snippet anonymously.

Editing Or Deleting

Keep snippets up to date so the tone stays professional and consistent.

• !edit_snippet <shortcut> <text> or !es <shortcut> <text> edits a snippet.
• !delete_snippet <shortcut> or !ds <shortcut> deletes a snippet.

Prefix Configuration

Snippet prefixes are configurable in config.ini:

• snippetPrefix defaults to !!
• snippetPrefixAnon defaults to !!!

If snippets are not working, check these values or ask an Admin.

Writing Good Snippets

• Keep them short and polite.
• Avoid promises you cannot guarantee.
• Use placeholders sparingly and clearly, like [IGN] or [Ticket ID].
• Refresh snippets when policy or tone changes.

When Not To Use A Snippet

• When a user is upset or the issue is sensitive.
• When the request is unique and needs a custom reply.
• When you need to ask a specific clarifying question.

Snippet Hygiene

If a snippet feels outdated or too rigid, update it or remove it. Stale snippets create inconsistent support.