Stadium Loading

Stadium Folder And Archive Loading

Stadium assignments are read from FSW/settings.ini. A stadium value can point to:

StadiumGBD/<stadium name>/
StadiumGBD/<stadium name>.zip
StadiumGBD/<stadium name>.rar

When an assignment points to an archive, the app extracts it into a temporary folder under runtime/, finds the first valid stadium folder inside it, applies the stadium files, and then cleans up the temporary extraction.

Valid stadium folders are expected to include normal Server 16 stadium files such as:

model.rx3
texture_day.rx3
texture_night.rx3
crowd_day.dat
crowd_night.dat
EntranceScene/
1/
3/
GameplayCamGBD/
GoalpostGBD/

Optional files supported by the runtime:

• NoSeats.rx3 for crowd-chair replacement.
• EntranceScene/bcstadiumcams_176.dat and EntranceScene/bcstadiumcams_261.dat for the stadium's entrance/exterior camera. See Entrance Camera Packs.
• StadiumMovie.vp8 and StadiumBumper.big for stadium-specific movies. Both files must be present. A Movie pack assigned to the match (round, tournament, derby or home team) takes priority over the stadium's movie. See Movies.
• GameplayCamGBD/bcgameplay_176.dat and GameplayCamGBD/bcgameplay_261.dat for per-stadium gameplay camera overrides.
• GoalpostGBD/ for per-stadium goal model files. Contents are copied to the game's goal-net directory on load and removed automatically when the next stadium (without goalposts) is applied.

Archive extraction is used only for loading the stadium files. Preview lookup does not extract archives, so preview images are resolved from StadiumGBD/render/thumbnail/stadium/<stadium name>.*.