Engine:CVAR base path: Difference between revisions

(Created page with "{{dev/uicvar}} Path for content and assets. <kua>set base_path './data/'</kua> == Arguments == * name - 'base_path' * value - Full or start folder relative path for base data and assets. Default value is './data/'. == Associations == * Is by default placed in the 'global' context. == Details == Path to the base asset load location. The path is either a full OS file system path to the library location, or a path relative to the launch location, which is the location o...")
 
Line 25: Line 25:


The relative file paths and names inside an archive or location, are the paths and names used to request an asset.
The relative file paths and names inside an archive or location, are the paths and names used to request an asset.
data
    pak0.zip
      file.txt
      model
          file1.obj
  file.txt
    model
      file2.obj


Default precedence:
Default precedence:
By default, Engine tries to load a single archive file named 'pak0.zip' in the specified 'base_path'. This file will then be asset location tier 0, the lowest. The 'base_path' itself will be asset tier 1.
By default, Engine tries to load a single archive file named 'pak0.zip' in the specified 'base_path'. This file will then be asset location tier 0, the lowest. The 'base_path' itself will be asset tier 1.


So for example, on startup Engine will look for a file named 'config.cfg', first in the file system at 'base_path', and then inside the 'pak0.zip' file loded from 'base_path'. If neither are found, will load with static defaults.
For example, on startup Engine will look for a file named 'config.cfg', first in the file system at 'base_path', and then inside the 'pak0.zip' file loaded from 'base_path'. If neither are found, will load with static defaults.


== Examples ==
== Examples ==