Home › Class layouts › ObjectPairing › ObjectPairing::Manager

Needs the Community Extension. Not available in the unmodified game; works while the Community Extension mod is active (its own functions, or raw memory access with Mem/ObjMem).

ObjectPairing::Manager

GameCore::ObjectPairing::Manager — class, size 304 bytes (0x130).

Bases: Game::Component::IInstance at 0x0

Linux offset Member Type
0x18 m_syncArchive FAutoArchiveClassContainer<GameCore::ObjectPairing::Manager>
0xb0 m_ChildLists FAutoVariable<eastl::map<GameCore::Player::ComponentID, eastl::vector<GameCore::Player::ComponentID, eastl::allocator>, eastl::less<GameCore::Player::ComponentID>, eastl::allocator>, GameCore::ObjectPairing::Manager>
0xf0 m_Parents FAutoVariable<eastl::map<GameCore::Player::ComponentID, GameCore::Player::ComponentID, eastl::less<GameCore::Player::ComponentID>, eastl::allocator>, GameCore::ObjectPairing::Manager>

Virtual functions

Slot order of the class's own vtable (inferred, see Virtual function tables). A virtual call call [vptr+offset] uses the byte offset. Owner is shown when the entry is inherited or overridden elsewhere.

Slot Offset Method Address in current build
0 0x0 \~Manager 0x6409e0
1 0x8 Initialize 0x640f80
2 0x10 Uninitialize 0x6412a0
3 0x18 Reset 0x641240
4 0x20 DoTurn 0x8972d0
5 0x28 Update (Game::Component::IInstance) 0x8972d0
6 0x30 RestoreVisualState (Game::Component::IInstance) 0x9b1040
7 0x38 InitializeVisualState (Game::Component::IInstance) 0x9b1040
8 0x40 InitializeNewGame (Game::Component::IInstance) 0x8972d0