UGC Needs Access, Not Just Permission

Duration: about 5 minutes Primary pillar: UGC & Creators Secondary pillars: Community Learner promise: By the end of this lesson, you will be able to identify one player-owned space your game could support.

### Opening Hook

Permission to create is not the same as a place to belong. Private servers and custom spaces can turn a game into a community home.

### Core Idea

Player-owned spaces create attachment because players can shape the rules, the people, the mods, the maps, and the memories.

The source moment for this lesson is: Nodecraft transcript: custom servers and maps can become community anchors.

### Game Or Real-World Example

Examples to use: Minecraft; Rust; Valheim; Battlefield custom servers.

Use the example to make the lesson concrete. Keep it short, then bring the learner back to the decision or behavior they can apply.

### Practical Model

Ask these questions:

1. What can players control?

1. Who can they invite?
2. What identity can the space develop?

### Mini Action

Identify one player-owned space your game could support.

### Transition

Ownership only scales if creation is accessible. That brings us to friction.

### On-Screen Notes

- Player-owned spaces create attachment.

• Custom servers can become community anchors.
• Control creates identity.

Duration: about 5 minutes Primary pillar: UGC & Creators Secondary pillars: Player Psychology Learner promise: By the end of this lesson, you will be able to remove one step from a creator setup flow.

### Opening Hook

A creator ecosystem can technically exist and still be unreachable to most players.

### Core Idea

Every setup step narrows the creator pool. Downloads, server files, ports, hosting, documentation, moderation, and sharing all decide who gets to participate.

The source moment for this lesson is: Nodecraft transcript: only a small slice of players will create if setup is manual.

### Game Or Real-World Example

Examples to use: One-click installers; Mod hosting tools.

Use the example to make the lesson concrete. Keep it short, then bring the learner back to the decision or behavior they can apply.

### Practical Model

Ask these questions:

1. What must the creator understand?

1. What must the creator configure?
2. Where can the creator fail before making anything?

### Mini Action

Remove one step from a creator setup flow.

### Transition

When players create outside the main game, teams also need better ways to understand that activity.

### On-Screen Notes

- Friction shrinks the creator pool.

• Accessibility matters for UGC.
• Tools decide who participates.

Duration: about 5 minutes Primary pillar: UGC & Creators Secondary pillars: Live Ops Learner promise: By the end of this lesson, you will be able to define one privacy-safe metric for creator or server health.

### Opening Hook

The official game is not always the whole game. Players may be spending meaningful time in private servers, modded spaces, and community-run worlds.

### Core Idea

Measuring the unofficial game helps teams understand long-tail engagement without taking ownership away from players.

The source moment for this lesson is: Nodecraft transcript: private server engagement can reveal the long-tail community.

### Game Or Real-World Example

Examples to use: Palworld-style private server demand; Player-hosted server communities.

Use the example to make the lesson concrete. Keep it short, then bring the learner back to the decision or behavior they can apply.

### Practical Model

Ask these questions:

1. What activity shows health?

1. Can it be measured without exposing private behavior?
2. How should the team respond?

### Mini Action

Define one privacy-safe metric for creator/server health.

### Transition

Now we can audit the friction across the whole UGC path.

### On-Screen Notes

- Private activity can be a health signal.

• Measure without taking over.
• Respect privacy and community ownership.