Each entity needs traceable sources, a verification date, live build or unambiguous official entity evidence, useful populated fields, a distinct search purpose and a stable canonical URL. A short name and a “coming soon” message do not pass.
Operations schematicConceptual
From a live observation to a published record
Capture build & sourceProvenance
Validate entity fieldsComplete relationships
Review usefulnessDistinct lookup
Publish & linkSearch and sitemap gate
Our launch verification workflow; incomplete records remain unpublished.
Evidence labels
Confirmed official
An official source describes the system. Pre-release behavior can still change.
Live-build verified
An observation includes a specific released build and its supporting evidence.
Source conflict
Credible sources differ. Both claims remain visible until reconciled.
Verify at launch
The exact value is not established. No guessed preset or entity page is published.
Official media provenance
67 unique official images, sourced from Urban Games’ news and media library. Optimized files and a homepage derivative are not counted as additional unique assets. The linked press Drive pack could not be retrieved; the official website supplied the library below.
Comparison axes; there is no universal winning vehicle.
Operations schematicPlanning math
The route balance sheet
Delivery revenuePer common period
Fleet operationRunning + maintenance
Infrastructure & interestRecurring costs
Net resultRevenue − all costs
User-entered arithmetic, separate from the game’s internal revenue formula.
Operations schematicConceptual
Locate the first persistent queue
ApproachRoad or rail access
Loading positionService time
DepartureExit clear?
Downstream pathCan the line move?
An inspection order for finding a bottleneck, not a capacity simulation.
Operations schematicConceptual
Before changing a signal
Intended routeCorrect destination?
ReservationConflicting movement?
Receiving terminalPrimary or alternative?
Exit pathSpace to continue?
Conceptual inspection flow for the official path-based signaling system.
Operations schematicConceptual
Two services, one shared junction
Passenger serviceObserve waiting
Freight serviceCheck deadlines
Shared reservationPriority affects preference
Clear destinationPhysical space still matters
Priority changes preference. It does not create extra track capacity.
Operations schematicConceptual
Choose the mode around the journey
Road & tramStreet and terminal access
RailTrack and station planning
WaterPier and inland transfer
AirAirport and ground connection
Planning questions for supported modes; no invented ranking or cost values.
Operations schematicConceptual
From company growth to new choices
World developmentPopulation growth
Company rankNew unlocks
Headquarters & perksInvestment choices
Regional effectsPlacement matters
Official progression relationships, without unlock thresholds or perk magnitudes.
Operations schematicConceptual
Survey before building
TemperateCheck terrain
SubarcticCheck source options
AridCheck available inputs
TropicalCheck crossings
Four climate zones. Confirm resource availability on the actual generated map.
Operations schematicConceptual
From a live observation to a published record
Capture build & sourceProvenance
Validate entity fieldsComplete relationships
Review usefulnessDistinct lookup
Publish & linkSearch and sitemap gate
Our launch verification workflow; incomplete records remain unpublished.
Historical context and corrections
TF2 can help explain familiar terminology, but its prices, recipes, maintenance or growth calculations are not evidence for TF3. Guides describe conceptual inspection steps unless a live verification is explicitly stated.
Use the linked primary source to resolve a question. Core pages will be updated before new entity URLs are published. About this independent project.
