The Repository is the storage location for files used by HeroEngine.
- A master database is handled by the Repository Server process, which talks to the Repository schema to manage the database.
- A portion of the database exists on each client, in the Local Repository Cache
If the Client needs something, it checks its local Repository Cache. If the needed data is there, it is loaded directly into the Client. If the information is not there, a request is sent to the Repository Server, which then downloads it into the Client's Repository Cache.
As the game geography is edited by the Area servers, the updated area files are sent to the Repository Server for clients to download. When the data in the Repository Server is changed, a notification is then sent out to all of the clients about the change. It may not necessarily be immediately downloaded to each client -- this is handled on an as-needed basis.
- HeroEngine game clients can connect to the Repository Server processes, and download files in the repository to their local repository cache.
- HeroEngine editing clients (such as HeroBlade and the Repository Browser), can upload files to the repository.
- High-level overview of how art gets from the artists, to the Repository, to the developers who are building areas
- Client software which allows manipulation and copying of elements in the Repository
- Dynamic process running on each Server Group
- The Art Server is the hardware that maintains the in-process art by artists
- How to purge your local art repository.
- Using the Repository to store text files that can then be accessed by script
- Using the Repository for some data storage of nodes