Tutorial Channel Help Desk

For a how-to channel: help organised by tutorial, a stuck-at-which-step format, project files and version warnings.

5 categories
14 channels
6 roles
Small

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

START HERE

how-to-ask-for-help
Which tutorial, which step, what you see, and which version.
new-tutorials
Posted automatically.
general
Everything else.

HELP

stuck-here
One thread per problem. Tag the tutorial series.
solved
Threads worth keeping.
Screen Share

TUTORIALS

beginner-series
Rename to your first series.
intermediate-series
Rename to your second series.
advanced-series
Rename to your third series.

RESOURCES

project-files
Starting points and finished versions.
version-warnings
Which tutorials no longer match current software. Honest and current.

COMMUNITY

tutorial-requests
One per post. Votes decide.
what-should-i-learn-next
Ask the room.
show-what-you-made
Results. Also the best evidence of which steps are hard.

Roles

CreatorAdministrator
ModeratorModerator
HelperModerator
Viewer
Muted

Overview

A tutorial channel's server exists for one thing, which is people who followed along and got stuck. #how-to-ask-for-help states the format that makes an answer possible: which tutorial, which step or timestamp, what you see instead, and which version of the software or kit you are using. That last item is the one everybody omits and the one that explains most failures. #stuck-here is a forum with one thread per problem, tagged by tutorial, so the person who hits the same wall in six months finds the answer rather than asking again. #solved collects the threads worth keeping. Tutorials is one channel per series the channel runs, so a question about the beginner series does not sit under the advanced one. #project-files is read-only and holds the downloads, starting points and finished versions, which removes the single most common request a tutorial channel receives. #version-warnings is the channel that saves the most frustration: a running note of which tutorials no longer match current software, written honestly rather than left for viewers to discover at step eleven. Requests keeps #tutorial-requests and #what-should-i-learn-next. #show-what-you-made is where people post their results, and it is both the most encouraging channel and the best source of evidence about which steps people actually struggle with.

When to use it

Tutorial channels get help requests with no version, no step and no description of what actually happened, so the reply is a guess. The same question arrives repeatedly because no answer is findable, and viewers hit a step that stopped working two software versions ago with no warning. This layout enforces a question format, keeps solved threads searchable, and publishes which tutorials have gone out of date.

What makes it different

A required format including the version, which is the omission that explains most failures.
One forum thread per problem, so the next person finds the answer instead of asking again.
A version-warnings channel listing which tutorials no longer match current software.
Project files are published, which removes the most common request the channel receives.

Recommended Vetox setup

Welcomer
Point Welcomer at #how-to-ask-for-help so a viewer's first question already includes the version and the step.
Notifications
Point Notifications at the channel feed so #new-tutorials posts each video without the creator relaying it.
Starboard
Point Starboard at #show-what-you-made so results are visible, which encourages the next person to finish.
Suggestions
Run Suggestions on #tutorial-requests so the next video answers what most viewers actually want.

Questions

Why is the version field so important?

Because it explains the majority of tutorial failures and almost nobody volunteers it. A menu moved, a default changed, a setting was renamed: the viewer follows the video exactly, sees something different, and concludes they did it wrong. Once the version is in the question, the answer is usually one line, and it also tells the creator which tutorials are quietly rotting.

Should old tutorials be deleted when they stop working?

Rarely. Most remain useful to people on older versions, and deleting them breaks every link and comment that pointed there. The better answer is the version-warnings channel plus a pinned note, which is honest without destroying the archive. Reserve deletion for tutorials whose advice has become actively harmful rather than merely outdated.

Common mistakes

Taking help requests with no version or step, so every answer is a guess about a different setup.
Answering in chat, which means the same question is answered from scratch every few weeks.
Never publishing which tutorials have gone stale, so viewers discover it halfway through.

Consider instead

Educational Channel Hub The videos explain subjects rather than walking viewers through a procedure.
Product Support Hub You are supporting your own product rather than teaching with third-party tools.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages