Bring the player to the table. Bring the character into the world. Make sure both can leave well.
The first monster in a virtual campaign should not be the microphone settings.
It happens often enough.
Everyone has arrived. Someone has made tea. Another player is six time zones away and has organised an evening around this game. The opening scene is ready.
Then somebody cannot hear anybody.
For the next twenty minutes, five adults discuss browser permissions.
There is no drama in that worth preserving.
Virtual campaign onboarding is often treated as the practical rubbish to get through before roleplaying begins: Discord link, character sheet, safety form, perhaps a hurried Session Zero.
For a long campaign, that is backwards.
Onboarding is the process by which a real person enters the table, their character enters the fictional world, and both become connected strongly enough that their choices can matter.
Done properly, it begins before Session Zero.
And it does not quite end until the character has found their place in the campaign.
Sometimes it even has one final task months or years later: helping that character leave.
> Good onboarding brings the player to the table and the character into the world.
Start with a conversation, not a character sheet
Before I want statistics, equipment or a three-page biography, I want to know who I am going to play with.
That does not mean interrogating somebody as though they were applying for security clearance.
It means having an actual conversation.
Why did this campaign interest them?
What have they enjoyed in previous games?
What usually loses them?
Do they enjoy investigation, relationships, political play, exploration, combat, horror or improvisation?
How much initiative do they like taking?
Do they enjoy being placed under pressure?
How serious do they like the fiction to remain?
What does reliability realistically look like for them?
And perhaps most importantly: what do they think this campaign is?
That last question catches an extraordinary number of problems before they become problems.
A player may see “dark fantasy” and imagine heroic fantasy with blood on the walls.
The Game Master may mean helpless social horror in a collapsing feudal society.
Neither interpretation is wrong.
They are simply not the same campaign.
> Good onboarding does not only ask whether the player fits the campaign. It asks whether the campaign fits the player.
That matters particularly in virtual play.
Online groups often contain people who have never met before. They may live in different countries, belong to different roleplaying traditions and have very different assumptions about what counts as normal table behaviour.
A twenty-minute conversation can prevent months of friction.
It can also lead to the perfectly good conclusion that somebody should play another campaign instead.
That is not rejection.
That is good matchmaking.
Tell the player what kind of promise the campaign makes
The interview works both ways.
The Game Master should explain the campaign clearly enough that the player can make an informed decision.
Not the entire lore.
Not every faction.
Certainly not the secret ending.
The player needs the campaign’s promise.
What kind of world is this?
What sort of pressure lives there?
How much freedom will the characters have?
How dangerous is the game?
How much does research or setting knowledge matter?
Is this heroic adventure, political tragedy, investigative horror, military fiction, pulp, survival, satire or some mixture?
What happens when characters fail?
What happens when they succeed?
If the world keeps moving between sessions, say so.
If factions act without waiting for the party, say so.
If relationships, promises and reputation matter, say so.
If the campaign offers enormous freedom but no guarantee that every idea will work, say that too.
Players do not need certainty about the fiction.
They need clarity about the kind of game they are agreeing to play.
> Uncertainty belongs in the fiction. Consent belongs at the table.
Do the technical check before it becomes everyone’s technical check
Once both sides know they actually want the same campaign, deal with the machinery.
Do it separately.
Before Session Zero if possible.
The exact tools hardly matter. Foundry, Roll20, Fantasy Grounds, Discord, a browser sheet, cameras, theatre of the mind — all can work.
What matters is that the player can use what this particular campaign requires.
Can they hear and be heard?
Does their headset behave?
Can they enter the virtual tabletop?
Can they open their character sheet?
Can they make a test roll?
Can they move a token if the game uses them?
Can they open a handout?
Can they find the place where announcements appear?
Do they know where to tell the group if they are going to be late?
A five- or ten-minute rehearsal can save half a session.
And keep it focused.
A player does not need to learn every Foundry function because Foundry contains it.
They need the functions they will actually use.
Technology should disappear behind the game.
> Teach what the player needs to play, not everything the software knows how to do.
The same principle applies to the number of tools.
One voice platform, one dependable home for campaign information, one clear character sheet and one sensible place for important messages will beat a magnificent ecosystem nobody can remember.
Virtual play already asks the brain to filter screens, voices, notifications and interfaces.
Do not make the players fight the furniture.
Safety needs an explanation, not a checkbox
Safety is part of onboarding because trust is part of onboarding.
A questionnaire can help.
It is not enough.
If the campaign uses Lines and Veils, explain what they mean.
If there is an X-card or pause tool, show people how it works.
If private messages are acceptable for safety communication, tell them where to send them.
Explain the Open Door.
Explain that somebody can step away.
Explain what happens if a scene becomes uncomfortable halfway through.
Most importantly, make clear that using a safety tool does not require a courtroom argument.
> A safety tool that nobody knows how to use is not yet a safety tool.
The interview is also the right place to establish tone.
Two players can both agree to horror and still want completely different horror.
One may enjoy bleak realism.
Another may prefer pulp, where terrible things happen but characters retain greater capacity to respond.
One may be comfortable with themes of grief but not detailed cruelty.
Another may be comfortable discussing violence but not intimate coercion.
The question is not simply what themes may exist.
It is how closely the camera may approach them.
The goal is not to remove danger from difficult fiction.
It is to make sure the danger belongs to the characters.
> Challenge the character. Respect the player.
Do not attach a backstory to the character
Character creation is where onboarding stops being preparation and begins becoming worldbuilding.
A common method is:
The player writes a backstory.
The Game Master reads it.
Everyone says it is interesting.
The document then dies quietly in a folder.
That is not integration.
A living campaign asks a different question:
Where does this character already belong?
If the character grew up in this city, which part?
What institution educated them?
Which historical event shaped their family?
Which war, strike, famine, migration, scandal, technological shift or supernatural event changed their assumptions?
Where did they work?
Who knows them?
Who remembers them badly?
Who would notice if they vanished?
Where are they welcome?
Where do they still owe money?
Which organisation has a file with their name on it?
What story about them is slightly wrong?
The point is not to bury the player under lore.
It is to connect personal history to world history.
> Do not attach a backstory to the character. Connect the character’s history to the world’s history.
That difference changes play immediately.
A character does not merely enter Edinburgh.
They went to school somewhere in Edinburgh.
Someone taught them.
Someone disliked them.
They may remember a neighbourhood before it changed.
Their mother may still attend the same church.
A former colleague may now work for an institution the campaign cares about.
An old promise may suddenly matter.
The world can answer because the character existed in it before the camera arrived.
Let the player contribute inheritance, not truth by decree
Players should also be allowed to bring something into the world.
This is where shared lore becomes useful.
A player might say:
“My grandmother always told me never to cross that bridge after midnight.”
Excellent.
What has been established?
That the grandmother said it.
Not that there is definitely a demon beneath the bridge.
Another character may have inherited an old military watch.
A family feud.
A childhood friend.
A local rumour.
An embarrassing political connection.
A pub where everybody knows their father.
These things make the setting personal without handing complete authority over reality to the player.
> Players can establish what their characters inherited. Play discovers what that inheritance means.
Sometimes the grandmother was right.
Sometimes she was protecting someone.
Sometimes she misunderstood an old event.
Sometimes the warning becomes important for reasons nobody expected.
That uncertainty is where play lives.
Give the character relationships before giving them plot
A new character should not exist in social vacuum.
They need points of attachment.
That does not mean creating twenty NPCs.
A handful of meaningful connections is enough.
Someone they trust.
Someone who expects something from them.
Someone they have disappointed.
An institution they know from the inside.
A place that feels familiar.
Perhaps someone who remembers a version of them they would rather leave behind.
These relationships give the Game Master much more than traditional plot hooks.
They give the world ways to respond.
If the character becomes famous, their former employer reacts.
If they disgrace themselves, their sister hears about it.
If they help a neighbourhood, somebody remembers.
If they betray a faction, the betrayal travels through people.
> A character becomes part of a living world when their actions have somewhere to land.
Joining an existing campaign requires two-sided onboarding
Bringing a new character into an established campaign is harder than starting everybody together.
The new player needs onboarding.
So does the existing group.
The classic solution is familiar:
“You meet a stranger in the tavern.”
Five minutes later, everybody has somehow decided to entrust the stranger with their lives.
Sometimes that is charming.
Usually it is just convenient.
A living campaign can do better.
Ask why these people would actually meet.
What does the new character need from the existing group?
What does the group need from them?
Who might already know them?
Which faction or institution connects them?
Could they have participated in something the party caused earlier?
Did somebody recommend them?
Were they sent because the party’s previous actions created a vacancy, debt, investigation or threat?
Now the character is not taped onto the campaign.
The changed world has produced a reason for them to appear.
The established players should also know enough to help.
Not the new character’s secrets.
But the social fact of their arrival.
A group integrates newcomers much more naturally when the fiction gives everybody something to work with.
Session Zero is where the threads meet
Session Zero remains important.
It simply is not the beginning.
By now we know the player.
The player understands the campaign.
The technology works.
Safety tools have been explained.
The character already has roots.
Session Zero lets those separate strands become a table.
Now we can establish group relationships.
Why are these characters together?
What do they already know about each other?
Where are tensions?
What keeps them from walking away the first time they disagree?
Friendship is one answer.
It is not the only one.
Duty works.
Debt works.
Shared guilt works.
Professional respect works.
Family works.
A promise to somebody dead works extremely well.
And then let the world breathe.
Give them a small piece of it.
A letter.
A report.
A newspaper.
A photograph.
A visitor.
A rumour.
An object nobody quite understands.
Session Zero should end with more than completed forms.
It should end with appetite.
The first sessions are still part of onboarding
Nobody becomes perfectly integrated because Session Zero ended.
The first two or three sessions tell us things an interview cannot.
How readily does the player speak?
Do they need more space to enter conversations?
Do they enjoy the amount of pressure they thought they would?
Does the character’s background actually produce useful play?
Is one connection clearly more interesting than another?
Did everyone misunderstand a piece of the campaign tone?
Good onboarding remains adjustable.
A relationship can be deepened.
An irrelevant background detail can remain irrelevant.
A safety boundary can change.
A technical setup can be simplified.
A player can discover that they want more investigation and less combat than they expected.
This is not a failure of preparation.
People learn games by playing them.
> Onboarding gives the campaign a strong beginning. Play tells us what needs adjusting.
Eventually, onboarding has an opposite problem
Players leave campaigns.
That is normal.
Jobs change.
Children arrive.
Health changes.
People move.
Schedules stop working.
Interest changes.
Sometimes somebody simply decides that Thursday night needs to become Thursday night again.
A living campaign should be capable of surviving that.
The easiest solution is to pretend the character never mattered.
For a long campaign, that is often the worst one.
If the character built relationships, changed factions, held office, made enemies, saved somebody, ruined somebody, owned property or became part of the group’s history, deleting them damages the world as well as the character.
But the opposite extreme is no better.
A departing player does not owe the campaign a dramatic death.
> A departing player does not owe the campaign a dead character.
Nor does a living world promise that every former player character will remain perfectly safe forever.
> A living world does not owe the character immortality.
The exit should make sense.
Perhaps the character leaves the city.
Takes a post elsewhere.
Retires.
Stays with a faction.
Goes into hiding.
Returns home.
Breaks with the group.
Disappears.
Or dies because the situation they are currently in makes that a plausible consequence.
The point is not to protect the fiction from departure.
It is to let the world answer departure honestly.
Decide what happens to the character before the player disappears
This is part of consent too.
Ask.
May the character remain in the world as an NPC?
May the Game Master use them actively?
May they only be mentioned?
Should they move offscreen?
Would the player prefer them to remain alive where reasonably possible?
Are there things the Game Master should never decide for them?
A character may belong to the shared history of a campaign while still feeling deeply personal to the person who played them.
That deserves respect.
If possible, offer a final session or final meaningful action.
But do not script the funeral in advance.
> Give the departing character a final chance to matter, not a guaranteed heroic outcome.
Maybe they save somebody.
Maybe they take the job they always wanted.
Maybe they fail.
Maybe their final act creates a problem everybody else spends the next year dealing with.
That is still legacy.
Leaving play does not mean leaving history
This is where living campaigns become different from disposable adventures.
The player may be gone.
The character’s consequences are not.
A neighbourhood remembers.
An institution keeps the file.
A faction still hates them.
Someone still loves them.
A song still contains the wrong version of what happened.
A new player may meet someone who says:
“You’re travelling with them? I knew Duncan once.”
Now absence has become part of the world.
That is Bardic Resonance in its quietest form.
History does not require the character to remain on stage.
> A character can leave the campaign without leaving its history.
And occasionally, years later, the old name returns.
Not as fan service.
Because the world had a reason to remember.
A practical onboarding sequence
For long virtual campaigns, the process can remain simple:
- Speak to the player and establish mutual fit.
- Explain the campaign promise, tone and expectations.
- Complete the technical check before the group needs it.
- Discuss boundaries and teach the safety tools.
- Build the character with enough setting knowledge to make informed choices.
- Connect the character’s personal history to world history.
- Establish a few relationships, obligations and places that already matter.
- If joining an existing group, build a credible social reason for the connection.
- Use Session Zero to connect the characters and give them their first taste of the world.
- Adjust during the first sessions as actual play reveals what works.
- When somebody leaves, decide together what happens to the character.
- Let the world remember whatever mattered.
None of this needs to feel like corporate induction.
Most of it can be conversational.
The important thing is that nothing essential is left to accident.
Onboarding is the first act of consequence
The best virtual onboarding does not eliminate uncertainty.
It removes the wrong uncertainty.
The player should not wonder whether the microphone works.
They should not wonder whether they are allowed to use the safety tool.
They should not wonder what sort of campaign they accidentally joined.
Their character, however, may have no idea who sent the letter.
They may not know why an old enemy has returned.
They may discover that the story their grandmother told them was only half true.
That is where uncertainty belongs.
Bring the player to the table.
Bring the character into the world.
Connect their history to the history already there.
Give their choices somewhere to land.
And when the day comes for them to leave, do not erase the footprints merely because the chair is empty.
A living campaign remembers who passed through it.
Stories that remember. Worlds that change.
Read: https://mythveilchronicles.com/ Play: https://startplaying.games/gm/dunchan Watch: https://www.youtube.com/@MythveilChronicles Support: https://www.patreon.com/MythveilChronicles Collaborate: https://www.linkedin.com/in/francisco-jos%C3%A9-z-b05aab371/