Table of Contents

Class ObjectFallbacksSection

Namespace
LlamaLogic.Architecture
Assembly
LlamaLogic.Architecture.dll

Represents the ObjectFallbacks section: the game's object fallback data, four sets of object ids (🔓)

public sealed class ObjectFallbacksSection : LotArchitectureSection
Inheritance
ObjectFallbacksSection
Inherited Members

Remarks

The game hands this data to its "Object Fallback Manager", the target of a Python function of that name. Version 2 is the only one supported: a byte followed by four categories, each a 32-bit count and that many object ids. Version 1 stores the data as an ObjectFallbackDataList message instead; no lot examined has it, so it is rejected.

The game reads exactly four categories whatever Unknown1 says, and loads each id other than 0 into a set, so the order of the ids on disk is the order of the game's hash set and means nothing. The meaning of the categories has not been established. In the lots examined Unknown1 is 4, and each section has two or three ids, all in the second category.

Constructors

ObjectFallbacksSection()

Initializes a new instance of the ObjectFallbacksSection class

public ObjectFallbacksSection()

Fields

CategoryCount

Gets the number of categories, which is 4

public const int CategoryCount = 4

Field Value

int

Properties

Categories

Gets the object ids of each of the four categories

public IReadOnlyList<Collection<ulong>> Categories { get; }

Property Value

IReadOnlyList<Collection<ulong>>

Unknown1

Gets/sets the byte that precedes the categories

public byte Unknown1 { get; set; }

Property Value

byte

Remarks

The game clamps it to at most 4 and passes it along while inserting ids, but no code in the game's simulation library makes use of it (other parts of the game were not examined). It is 4 in every lot examined.