For a first practice project, use one identifiable SpawnLocation and a broad start platform. Test it through the normal player entry. A Part named “Spawn” or a START sign is not the same object type.
Create a single-spawn baseline
Use a separate project without team or checkpoint scripts. Inspect Explorer for the template’s existing SpawnLocation before adding another. Keep only one enabled spawn for this baseline; make this simplification in the practice copy, not in a team-based game you intend to preserve.
If you are following our practice course, Start has Size 12, 1, 12 and Position 0, 8, 0. Put the SpawnLocation directly above it with the following values:
| Property | Value | Purpose |
|---|---|---|
| Name | PracticeSpawn | Makes the intended object easy to identify. |
| Size | 6, 1, 6 | Fits inside the 12-by-12 start platform. |
| Position | 0, 9, 0 | Places its bottom on the platform’s top. |
| Anchored | true | Keeps the spawn object stationary under physics. |
| CanCollide | true | Provides a physical standing surface. |
| Enabled | true | Allows this spawn to be used. |
| Neutral | true | Uses a non-team-specific baseline. |
| AllowTeamChangeOnTouch | false | Avoids adding team-change behaviour to this exercise. |
The position and dimensions are Qrajo’s practice design. Roblox documents the spawn-specific properties in its SpawnLocation reference. Do not copy this neutral setup over a project that intentionally assigns players to teams.
Test normal entry three times
- Select the normal character Test mode, not Test Here.
- Observe the initial location before moving. Record whether the character is on the intended platform with room to walk.
- Walk from the spawn to the first landing. Check for an overhead obstruction or an unclear route.
- Stop and repeat twice without changing the setup. Record each observed starting position.
Three attempts are a small consistency check, not proof of all future spawning behaviour. Test Here uses a camera-based starting point and therefore does not answer the same question. See the testing-mode guide for choosing a mode.
Use the result to narrow the problem
| What happens | Check next |
|---|---|
| The character appears near the camera. | Confirm that you selected Test, rather than Test Here. |
| Attempts begin at different intended spawn objects. | List all enabled SpawnLocations and the project’s team rules. |
| The character begins correctly but falls. | Inspect the standing surface and objects immediately below it. |
| The character starts correctly, then relocates. | Inspect checkpoint, respawn or teleport behaviour separately. |
Restore complexity in stages
Save the working single-spawn version first. Add a second spawn, team assignment or checkpoint system only when you have a specific expected result to test. Do not assume that duplicating a SpawnLocation automatically creates an ordered checkpoint course.
For a useful handoff note, list the enabled spawns, whether teams are used, the selected test mode and the first location observed on each attempt. Keep “initial entry” separate from “where I respawn after a failure” so a collaborator can reproduce the correct problem.
Updated September 22, 2026: Added a single-spawn baseline with numerical placement and entry checks. Official references were checked for this revision. The exercises are original practice designs, not reports of gameplay testing. Qrajo is independent of Roblox. Editorial policy · Report a correction.
