struct

TReplicationSlot

One game-installed callback slot, stored the only way a slot crossing a DLL boundary can be stored safely: a plain function pointer, an opaque context, and a release hook for the context.

Module
Networking
Header
#include "Networking/Replication/ReplicationManager.h"
Namespace
Mowo
Template
template<typename FnT>

A std::function here was the ABI hazard — it is constructed by the installer (a hot-reloadable game module, a plugin, a test's frame) and destroyed by this class, in another image, through that image's allocator and its copy of the callable's inline destructor. It was also unattributable: with no address to test, a module unload had to wipe every slot on every manager, including the ones the dying module never touched.

All three pointers here are addresses in the INSTALLER's image. Construction and destruction of the context both happen there, and FModuleManager can say which module owns the slot.

Properties

TypeNameDescription
FnTfnDefault nullptr.
void*contextDefault nullptr.

Public functions

ReturnsNameDescription
void
operatorbool
voidReset
voidAbandonDrop the slot WITHOUT running the release hook.
boolOwnedByTrue when this module owns any of the three addresses, i.e.

Function details

void

C++
void (*release)(void* context) = nullptr

operatorbool

C++
explicit operator bool() const

Reset

C++
void Reset()

Abandon

C++
void Abandon()

Drop the slot WITHOUT running the release hook. Only for a module unload, where the hook itself lives in the pages about to be unmapped — leaking the context is the only available answer, and the image it was allocated from is going away with it.

OwnedBy

C++
template<typename FOwns> bool OwnedBy(FOwns&& owns) const

True when this module owns any of the three addresses, i.e. unloading it would leave the slot pointing into unmapped memory.

Generated from Networking/Replication/ReplicationManager.h via networking.json · Nov 4, 2026Version 1.0.0