Abstract: A data provider application programming interface (API) is configured for use with a game content editing application. An asset relationship management file, which is generated with the data provider API, includes information such as relationship references and annotations and is updated by the data provider API when a digital asset is edited. The asset relationship management file is then stored in a data store. An asset relationship graph is generated, based on the asset relationship management file in the data store. The asset relationship graph includes asset graph nodes that map dependency relationships between asset files. A graph API is also described. The graph API is configured for accessing the relationship graph through a server process to expose dependency relationships and annotations to a client process, such as an application. Thus, the effect of changes to one asset on other assets can readily be evaluated.

Abstract: Systems and methods are provided for an extensive content build pipeline. The exemplary content build pipeline is based on a code build process using a standard XIF file format containing reference to game content produced using various game content editors and tools. This standardized file format is capable of containing the information required by the content build as metadata, thus enabling a standard content build pipeline. This is opposed to being based on a number of game-specific formats and thus requiring the use of exporters. However, game engine developers can then optimize the XIF files to their particular game engine format.