Browse documentationqbx_spawn
On this page
Resource guide

qbx_spawn

A safer handoff from spawn selection to the world.

QboxOX LibOX MySQLQBX Properties
Resource page View source
Version
v0.1.1
Updated
Aug 15, 2026
License
GPL-3.0
01 / OVERVIEW

Start here

This Qbox spawn-selector fork adds collision-aware placement for normal coordinate destinations. It freezes the player, sets streaming focus, requests collision for up to ten seconds, applies the final coordinate and heading, then triggers the loaded events and restores the world view. Property spawns keep the upstream qbx_properties entry path.

02 / REQUIREMENTS

What you need

Frameworkqbx_core
Requiredox_lib and oxmysql
Optionalqbx_properties for owned-property spawns
Databaseplayers table with stored position data
03 / INSTALLATION

Install and start

  1. 01

    Place qbx_spawn in resources and keep the expected resource name.

  2. 02

    Configure the enabled labels and vec4 coordinates in config/client.lua.

  3. 03

    Start qbx_properties before qbx_spawn when owned properties should appear in the selector.

  4. 04

    Test each coordinate after a fresh connection and verify collision, heading, fade-in, and player-loaded events on the production map build.

Recommended start orderplain text
ensure oxmysql
ensure ox_lib
ensure qbx_core
ensure qbx_properties       # optional owned-property destinations
ensure qbx_spawn
04 / CONFIGURATION

Configuration checkpoints

01

Configure the spawn list

Edit config/client.lua to add, remove, or reorder label and vec4 entries. The current snapshot enables Paleto Bay, Sandy Shores, Legion Square, Mission Row, Vespucci Beach, and Grapeseed.

Exampleplain text
{ label = 'Legion Square', coords = vec4(195.17, -933.77, 29.7, 144.5) }
02

Validate every coordinate

Use safe ground coordinates with the intended heading and verify that the production map build streams collision there. The ten-second wait reduces fall-through risk but cannot correct a bad destination.

03

Decide whether to expose property spawns

Start qbx_properties before qbx_spawn to list properties owned by the player. Keyholder-only properties are not included by the current server query.

04

Keep upstream updates manual

The manifest repository and version checker still point to Qbox-project/qbx_spawn. Review upstream changes against the custom client patch before replacing files.

05 / USAGE

Validate the resource

Test a fresh connection

Join with a character that has a saved position, move through every configured map option, select a normal coordinate, and confirm collision loads before the screen fades in.

Test repeated selector setup

Open the flow with multiple characters or reconnects and confirm the selected button resets to the first entry rather than keeping a stale index.

Validate property entry separately

Select an owned property and confirm qbx_properties handles the interior entry. The new collision-wait helper is intentionally not used on that path.

06 / TROUBLESHOOTING

Common checks

A player still falls through at one spawn

Validate that coordinate against the active map and collision files. The helper waits up to ten seconds and is a mitigation, not a guarantee for invalid or slow custom-map locations.

Property destinations are missing

Confirm qbx_properties starts first, the properties table exists, and the current character owns a property. The query does not include properties held only through keys.

Last location cannot be read

Confirm qbx_core resolves the player, oxmysql is running, and the players row contains valid JSON position data for the character's citizen ID.

An upstream update removes the mitigation

The version checker targets the upstream Qbox repository. Compare client/main.lua before applying an update and preserve the collision helper and selection reset intentionally.

07 / REFERENCE

Source and release notes

  • The fork is exactly one custom commit ahead of the audited upstream main branch and keeps manifest version 0.1.1.
  • Collision-aware placement applies to ordinary coordinates only; property spawns use qbx_properties.
  • The repository README image is an expired Discord CDN asset and is not used on this site.
  • This GPL-3.0 fork retains Qbox Project attribution and should be treated as a repository snapshot rather than a tagged release.