mirror of
https://github.com/SabreTools/SabreTools.Serialization.git
synced 2026-04-08 07:13:01 +00:00
7689c6dd07
This change looks dramatic, but it's just separating out the already-split namespaces into separate top-level folders. In theory, every single one could be built into their own Nuget package. `SabreTools.Serialization` still builds the normal Nuget package that is used by all other projects and includes all namespaces.
34 lines
1.4 KiB
C#
34 lines
1.4 KiB
C#
namespace SabreTools.Data.Models.StarForce
|
|
{
|
|
/// <summary>
|
|
/// SFFS consists of 2 major parts: the container files that contain the game
|
|
/// content and a filesystem filter driver (sfvfs02.sys) that handles all file-io.
|
|
/// When a game has SFFS'ed files and uses some file-io api like CreateFile, the
|
|
/// SFFS filterdriver sees this request and handles it if needed.that way, SFFS is
|
|
/// totally transparent to the game, since it never knows if the data is coming from
|
|
/// real file API or from the SFFS filterdriver. during SF initialization, the
|
|
/// SF-process registers itself as a SFFS process in a processid list, maintained
|
|
/// from the filterdriver. Part of that registration are the names of the
|
|
/// containerfiles, the process uses and an application key, that is needed to
|
|
/// decrypt headerinfos. Note that SFFS itself is completly vm-free.
|
|
/// </summary>
|
|
/// <see href="https://web.archive.org/web/20231020050651/https://forum.xentax.com/viewtopic.php?f=21&t=2084"/>
|
|
public sealed class FileSystem
|
|
{
|
|
/// <summary>
|
|
/// Header
|
|
/// </summary>
|
|
public Header Header { get; set; } = new();
|
|
|
|
/// <summary>
|
|
/// Files
|
|
/// </summary>
|
|
public FileEntry[] Files { get; set; } = [];
|
|
|
|
/// <summary>
|
|
/// File headers
|
|
/// </summary>
|
|
public FileHeader[] FileHeaders { get; set; } = [];
|
|
}
|
|
}
|