Core RPG handbook · Development build / version notes

Documentation / Tile Tick Core RPG

Travel & Locations

Authoritative location travel, destinations, scene restore and limitations.

On this page

Travel is server authoritative and supports both same-scene repositioning and location/scene transitions through one location-session path.

Important types#

  • LocationDefinition describes a location/loading/grid scope.
  • TravelDefinition describes travel content.
  • TravelDestination exposes stable destination IDs and arrival data.
  • NetworkLocationSession is the authoritative player travel/session coordinator.
  • NetworkTravelTrigger supports server-triggered travel when entering a configured trigger.

Travel flow#

Player requests interaction or enters server travel trigger
↓
Server validates destination and readiness
↓
NetworkLocationSession begins authoritative travel
↓
Same-scene reposition OR owner scene/location load
↓
Arrival position committed
↓
Location state saved/replicated
↓
Client transition presentation completes

Login restore#

Gameplay readiness includes scene restoration. A reconnecting player is not fully ready until the saved location/scene has been restored and the local presentation is bound.

Current limitations#

  • The demo save settings register only Demo for scene restoration.
  • Travel group policies beyond Individual and instances beyond shared instance 0 are not fully implemented.
Do not reintroduce old local travel paths beside NetworkLocationSession. New travel must stay inside the authoritative location/session architecture.