mirror of
https://github.com/DarkflameUniverse/DarkflameServer.git
synced 2026-11-19 18:25:27 +00:00
refactor(entity): each component type has an allocator, as the client
DoObjectComponentLoad walks the client's load order and calls the type's allocator from a table, like ObjectLoader2, instead of one 76-case switch. Components with rules of their own have a static Allocator (the client's LWOxComponent::Allocator); the rest share a registry allocator. The load state moves to ObjectLoadState.h so the allocators can take it. Construction bytes are identical for all 15,962 LOTs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -10,6 +10,8 @@
|
||||
#include "CDPetComponentTable.h"
|
||||
#include "eHelpType.h"
|
||||
|
||||
struct ObjectLoadState;
|
||||
|
||||
/**
|
||||
* Represents an entity that is a pet. This pet can be tamed and consequently follows the tamer around, allowing it
|
||||
* to dig for treasure and activate pet bouncers.
|
||||
@@ -19,6 +21,9 @@ class PetComponent final : public Component
|
||||
public:
|
||||
static constexpr eReplicaComponentType ComponentType = eReplicaComponentType::PET;
|
||||
|
||||
// The client's allocator for this type (ObjectLoader2::DoObjectComponentLoad calls it in load order)
|
||||
static void Allocator(Entity& entity, ObjectLoadState& state);
|
||||
|
||||
// Bits of the serialized pet status. State number N is bit 1 << (N - 1) (the client's StateNumToIndex,
|
||||
// 0x00bd19b0); the meanings are what the live server sent (2014 packet captures) and what the client does with them.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user