Namespace Apogee.Content.Packs¶
Classes¶
Packs a game folder into a pack (see Apogee.Runtime --pack, and what an export calls. The sources of imported assets are dropped from a cooked pack,
authored XML and the definitions of the base packages are cooked in place, and a patch pack holds only what changed against its bases.
The secret that encrypts a game's packs: 32 bytes, written as 64 hexadecimal digits. The build tool and the editor read it from the environment (APOGEE_PACK_KEY, which the
.env file of the repository sets), and an export writes it, masked, into the executable of the game it makes (Apogee.Export.PackKeySlot; obfuscation, not protection) so that a shipped game
needs no variable. Without a key packs are not encrypted. It is never written to a pack, a log, or an error message.
What
What
A pack (see name_001.pack…, which must all be there); files are read, decrypted, decompressed and checked against their hashes when asked for. A pack that is encrypted needs the key
(without one, or with a wrong one,
Writes a pack: files added with game.pack, game_001.pack…) at