Struct TitleHistories 

pub struct TitleHistories {
    histories: TigerHashMap<&'static str, TitleHistory>,
}

Fields

histories: TigerHashMap<&'static str, TitleHistory>

Implementations

impl TitleHistories

pub fn load_item(&mut self, key: Token, block: Block)

pub fn scan_variables(&self, registry: &mut Variables)

pub fn exists(&self, key: &str) -> bool

pub fn iter_keys(&self) -> impl Iterator<Item = &Token>

pub fn validate(&self, data: &Everything)

pub fn verify_has_holder( &self, key: &Token, date: Date, data: &Everything, overlord: &str, )

Trait Implementations

impl Clone for TitleHistories

fn clone(&self) -> TitleHistories

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for TitleHistories

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for TitleHistories

fn default() -> TitleHistories

Returns the “default value” for a type.

impl FileHandler<Block> for TitleHistories

fn subpath(&self) -> PathBuf

Which files this handler is interested in. This is a directory prefix of files it wants to handle, relative to the mod or vanilla root.

fn load_file(&self, entry: &FileEntry, parser: &ParserMemory) -> Option<Block>

This is called for each matching file, in arbitrary order. If a T is returned, it will be passed to handle_file later. Since load_file is executed multi-threaded while handle_file is single-threaded, try to do the heavy work in this function.

fn handle_file(&mut self, _entry: &FileEntry, block: Block)

This is called for each matching file in turn, in lexical order. That’s the order in which the CK3 game engine loads them too.

fn config(&mut self, _config: &Block)

The FileHandler can read settings it needs from the ck3-tiger config.

fn finalize(&mut self)

This is called after all files have been handled. The FileHandler can generate indexes, perform full-data checks, etc.