Skip to main content

Network & Replication

RakNet replication stack, Client/Server Replicators, physics senders/receivers.

Subsystem Metrics​

  • Total Documented Functions: 1546
  • Functions Exercised in Tests: 100
  • Platform-Divergent Implementations: 168
  • Component Source Files: 100

Source Files​

View all 100 source files in this subsystem
Source FilePath
API.cppNetwork/API.cpp
BoostAppend.cppNetwork/BoostAppend.cpp
ChatFilter.cppNetwork/ChatFilter.cpp
Client.cppNetwork/Client.cpp
Client.hNetwork/Client.h
ClientReplicator.cppNetwork/ClientReplicator.cpp
ClientReplicator.hNetwork/ClientReplicator.h
ClusterUpdateBuffer.cppNetwork/ClusterUpdateBuffer.cpp
ClusterUpdateBuffer.hNetwork/ClusterUpdateBuffer.h
Compressor.cppNetwork/Compressor.cpp
ConcurrentRakPeer.cppNetwork/ConcurrentRakPeer.cpp
ConcurrentRakPeer.hNetwork/ConcurrentRakPeer.h
CrashReporter.cppNetwork/CrashReporter.cpp
DataBlockEncryptor.cppNetwork/DataBlockEncryptor.cpp
Dictionary.cppNetwork/Dictionary.cpp
Dictionary.hNetwork/Dictionary.h
DirectPhysicsReceiver.cppNetwork/DirectPhysicsReceiver.cpp
ErrorCompPhysicsSender.cppNetwork/ErrorCompPhysicsSender.cpp
ErrorCompPhysicsSender2.cppNetwork/ErrorCompPhysicsSender2.cpp
ErrorCompPhysicsSender2.hNetwork/ErrorCompPhysicsSender2.h
GameConfigurer.cppNetwork/GameConfigurer.cpp
GamePerfMonitor.cppNetwork/GamePerfMonitor.cpp
GamePerfMonitor.hNetwork/GamePerfMonitor.h
InterpolatingPhysicsReceiver.cppNetwork/InterpolatingPhysicsReceiver.cpp
InterpolatingPhysicsReceiver.hNetwork/InterpolatingPhysicsReceiver.h
Item.cppNetwork/Item.cpp
Item.hNetwork/Item.h
Marker.cppNetwork/Marker.cpp
MechanismItem.cppNetwork/MechanismItem.cpp
MechanismItem.hNetwork/MechanismItem.h
MovementHistoryJob.cppNetwork/MovementHistoryJob.cpp
NetPmc.cppNetwork/NetPmc.cpp
NetworkClusterPacketCache.cppNetwork/NetworkClusterPacketCache.cpp
NetworkFilter.cppNetwork/NetworkFilter.cpp
NetworkOwnerJob.cppNetwork/NetworkOwnerJob.cpp
NetworkPacketCache.cppNetwork/NetworkPacketCache.cpp
NetworkProfiler.cppNetwork/NetworkProfiler.cpp
NetworkProfiler.hNetwork/NetworkProfiler.h
NetworkSettings.cppNetwork/NetworkSettings.cpp
NetworkSettings.hNetwork/NetworkSettings.h
OrderedSet.hNetwork/OrderedSet.h
Peer.cppNetwork/Peer.cpp
PersistentDataStore.cppNetwork/PersistentDataStore.cpp
PersistentDataStore.hNetwork/PersistentDataStore.h
PhysicsReceiver.cppNetwork/PhysicsReceiver.cpp
PhysicsReceiver.hNetwork/PhysicsReceiver.h
PhysicsSender.cppNetwork/PhysicsSender.cpp
Player.cppNetwork/Player.cpp
Players.cppNetwork/Players.cpp
PropertySynchronization.hNetwork/PropertySynchronization.h
Replicator.ChangePropertyItem.cppNetwork/Replicator.ChangePropertyItem.cpp
Replicator.DeleteInstanceItem.cppNetwork/Replicator.DeleteInstanceItem.cpp
Replicator.EventInvocationItem.cppNetwork/Replicator.EventInvocationItem.cpp
Replicator.GCJob.cppNetwork/Replicator.GCJob.cpp
Replicator.GCJob.hNetwork/Replicator.GCJob.h
Replicator.HashItem.cppNetwork/Replicator.HashItem.cpp
Replicator.ItemSender.cppNetwork/Replicator.ItemSender.cpp
Replicator.JoinDataItem.cppNetwork/Replicator.JoinDataItem.cpp
Replicator.JoinDataItem.hNetwork/Replicator.JoinDataItem.h
Replicator.MarkerItem.cppNetwork/Replicator.MarkerItem.cpp
Replicator.NewInstanceItem.cppNetwork/Replicator.NewInstanceItem.cpp
Replicator.NewInstanceItem.hNetwork/Replicator.NewInstanceItem.h
Replicator.PingBackItem.cppNetwork/Replicator.PingBackItem.cpp
Replicator.PingItem.cppNetwork/Replicator.PingItem.cpp
Replicator.PingJob.hNetwork/Replicator.PingJob.h
Replicator.ProcessPacketsJob.hNetwork/Replicator.ProcessPacketsJob.h
Replicator.ReferencePropertyChangedItem.cppNetwork/Replicator.ReferencePropertyChangedItem.cpp
Replicator.RockyItem.cppNetwork/Replicator.RockyItem.cpp
Replicator.SendDataJob.hNetwork/Replicator.SendDataJob.h
Replicator.StatsItem.cppNetwork/Replicator.StatsItem.cpp
Replicator.StatsItem.hNetwork/Replicator.StatsItem.h
Replicator.StreamJob.cppNetwork/Replicator.StreamJob.cpp
Replicator.StreamJob.hNetwork/Replicator.StreamJob.h
Replicator.TagItem.cppNetwork/Replicator.TagItem.cpp
Replicator.cppNetwork/Replicator.cpp
Replicator.hNetwork/Replicator.h
ReplicatorStats.cppNetwork/ReplicatorStats.cpp
RoundRobinPhysicsSender.cppNetwork/RoundRobinPhysicsSender.cpp
Server.cppNetwork/Server.cpp
Server.hNetwork/Server.h
ServerReplicator.cppNetwork/ServerReplicator.cpp
ServerReplicator.hNetwork/ServerReplicator.h
Streaming.cppNetwork/Streaming.cpp
Streaming.hNetwork/Streaming.h
TopNErrorsPhysicsSender.cppNetwork/TopNErrorsPhysicsSender.cpp
TopNErrorsPhysicsSender.hNetwork/TopNErrorsPhysicsSender.h
Util.cppNetwork/Util.cpp
WebChatFilter.cppNetwork/WebChatFilter.cpp
CompactCFrame.hNetwork/include/network/CompactCFrame.h
CrashReporter.hNetwork/include/network/CrashReporter.h
CrispProxy.hNetwork/include/network/CrispProxy.h
GameConfigurer.hNetwork/include/network/GameConfigurer.h
NetPmc.hNetwork/include/network/NetPmc.h
NetworkClusterPacketCache.hNetwork/include/network/NetworkClusterPacketCache.h
NetworkOwner.hNetwork/include/network/NetworkOwner.h
NetworkPacketCache.hNetwork/include/network/NetworkPacketCache.h
Player.hNetwork/include/network/Player.h
Players.hNetwork/include/network/Players.h
RakNetFast.hNetwork/include/network/RakNetFast.h
rijndael.cppNetwork/rijndael.cpp

Function Reference​

1. SafeInitFree​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

public: SafeInitFree();
PropertyValue
Return Typepublic:
ModifiersNone
Source LocationNetwork/API.cpp:74
SubsystemNetwork & Replication

How it Works Internally​

Executes SafeInitFree within Network & Replication. Coordinates interactions with AddReference.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: AddReference.
  • External Library Dependencies: RakNet UDP Networking Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on SafeInitFree.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


2. RBX::Network::isPlayerAuthenticationEnabled​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool RBX::Network::isPlayerAuthenticationEnabled();
PropertyValue
Return Typebool
ModifiersNone
Source LocationNetwork/API.cpp:90
SubsystemNetwork & Replication

How it Works Internally​

Executes isPlayerAuthenticationEnabled within Network & Replication.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isPlayerAuthenticationEnabled.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


3. RBX::Network::isNetworkClient​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool RBX::Network::isNetworkClient(const Instance* context);
PropertyValue
Return Typebool
ModifiersNone
Source LocationNetwork/API.cpp:95
SubsystemNetwork & Replication

How it Works Internally​

Executes isNetworkClient within Network & Replication.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isNetworkClient.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


4. createSecureReplicator​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

shared_ptr<RBX::Network::ServerReplicator> createSecureReplicator(RakNet::SystemAddress a, RBX::Network::Server* s, RBX::NetworkSettings* networkSettings);
PropertyValue
Return Typeshared_ptr&lt;RBX::Network::ServerReplicator&gt;
Modifiersstatic
Source LocationNetwork/API.cpp:102
SubsystemNetwork & Replication

How it Works Internally​

Executes createSecureReplicator within Network & Replication.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on createSecureReplicator.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


5. initVersion1​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void initVersion1();
PropertyValue
Return Typevoid
Modifiersstatic
Source LocationNetwork/API.cpp:107
SubsystemNetwork & Replication

How it Works Internally​

Executes initVersion1 within Network & Replication. Coordinates interactions with externally, defined, rot13.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: externally, defined, rot13.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on initVersion1.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


6. initVersion2​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void initVersion2();
PropertyValue
Return Typevoid
Modifiersstatic
Source LocationNetwork/API.cpp:130
SubsystemNetwork & Replication

How it Works Internally​

Executes initVersion2 within Network & Replication.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on initVersion2.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


7. RBX::Network::initWithServerSecurity​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void RBX::Network::initWithServerSecurity();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/API.cpp:137
SubsystemNetwork & Replication

How it Works Internally​

Executes initWithServerSecurity within Network & Replication. Coordinates interactions with initVersion1, initWithoutSecurity, defined, initVersion2.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: initVersion1, initWithoutSecurity, defined, initVersion2.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on initWithServerSecurity.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


8. RBX::Network::initWithPlayerSecurity​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void RBX::Network::initWithPlayerSecurity();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/API.cpp:150
SubsystemNetwork & Replication

How it Works Internally​

Executes initWithPlayerSecurity within Network & Replication. Coordinates interactions with initVersion1, initWithoutSecurity, initVersion2.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: initVersion1, initWithoutSecurity, initVersion2.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on initWithPlayerSecurity.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


9. RBX::Network::initWithCloudEditSecurity​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void RBX::Network::initWithCloudEditSecurity();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/API.cpp:158
SubsystemNetwork & Replication

How it Works Internally​

Executes initWithCloudEditSecurity within Network & Replication.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on initWithCloudEditSecurity.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


10. RBX::Network::initWithoutSecurity​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void RBX::Network::initWithoutSecurity();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/API.cpp:166
SubsystemNetwork & Replication

How it Works Internally​

Executes initWithoutSecurity within Network & Replication. Coordinates interactions with VMProtectBeginMutation, classDescriptor, singleton, VMProtectEnd.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: VMProtectBeginMutation, classDescriptor, singleton, VMProtectEnd.
  • External Library Dependencies: OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on initWithoutSecurity.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


11. RBX::Network::setVersion​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void RBX::Network::setVersion(const char* version);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/API.cpp:188
SubsystemNetwork & Replication

How it Works Internally​

Executes setVersion within Network & Replication.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setVersion.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


12. RBX::Network::setSecurityVersions​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void RBX::Network::setSecurityVersions(const std::vector<std::string>& versions);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/API.cpp:194
SubsystemNetwork & Replication

How it Works Internally​

Executes setSecurityVersions within Network & Replication. Coordinates interactions with setAllowedSecurityVersions.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: setAllowedSecurityVersions.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setSecurityVersions.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


13. RBX::Network::isTrustedContent​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool RBX::Network::isTrustedContent(const char* url);
PropertyValue
Return Typebool
ModifiersNone
Source LocationNetwork/API.cpp:199
SubsystemNetwork & Replication

How it Works Internally​

Executes isTrustedContent within Network & Replication. Coordinates interactions with isUrl, urlString, to_lower, find.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: isUrl, urlString, to_lower, find, substr, size.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isTrustedContent.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


14. isDebuggedDirectThreadFunc​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void isDebuggedDirectThreadFunc(weak_ptr<RBX::DataModel> weakDataModel);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/API.cpp:257
SubsystemNetwork & Replication

How it Works Internally​

Executes isDebuggedDirectThreadFunc within Network & Replication. Coordinates interactions with defined, VMProtectBeginMutation, lock, VMProtectIsDebuggerPresent. Employs reference-counted heap object ownership (boost::shared_ptr).

  • Control Flow & Execution: Iterative loop processing, Conditional branching.
  • Memory Management: Reference-counted heap object ownership (boost::shared_ptr).
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: defined, VMProtectBeginMutation, lock, VMProtectIsDebuggerPresent, addHackFlag, sleep, milliseconds, VMProtectEnd.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isDebuggedDirectThreadFunc.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


15. RBX::spawnDebugCheckThreads​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void RBX::spawnDebugCheckThreads(weak_ptr<RBX::DataModel> dataModel);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/API.cpp:277
SubsystemNetwork & Replication

How it Works Internally​

Executes spawnDebugCheckThreads within Network & Replication. Coordinates interactions with bind.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: bind.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on spawnDebugCheckThreads.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


16. boost::hash_value​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

std::size_t boost::hash_value(const shared_ptr<RBX::PartInstance>& b);
PropertyValue
Return Typestd::size_t
ModifiersNone
Source LocationNetwork/BoostAppend.cpp:6
SubsystemNetwork & Replication

How it Works Internally​

Executes hash_value within Network & Replication. Coordinates interactions with hasher, get.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: hasher, get.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on hash_value.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


17. ChatFilter::filterMessageBase​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool ChatFilter::filterMessageBase(shared_ptr<Player> sourcePlayer, shared_ptr<Instance> receiver,
const std::string& message,
const ChatFilter::FilteredChatMessageCallback callback);
PropertyValue
Return Typebool
ModifiersNone
Source LocationNetwork/ChatFilter.cpp:15
SubsystemNetwork & Replication

How it Works Internally​

Executes filterMessageBase within Network & Replication. Coordinates interactions with chats, starts_with, bind.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: chats, starts_with, bind.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on filterMessageBase.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


18. Client::findClient​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Client* Client::findClient(const RBX::Instance* context, bool testInDatamodel);
PropertyValue
Return TypeClient*
ModifiersNone
Source LocationNetwork/Client.cpp:75
SubsystemNetwork & Replication

How it Works Internally​

Executes findClient within Network & Replication. Coordinates interactions with findServiceProvider, RBXASSERT.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: findServiceProvider, RBXASSERT.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on findClient.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


19. Client::clientIsPresent​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool Client::clientIsPresent(const RBX::Instance* context, bool testInDatamodel);
PropertyValue
Return Typebool
ModifiersNone
Source LocationNetwork/Client.cpp:82
SubsystemNetwork & Replication

How it Works Internally​

Executes clientIsPresent within Network & Replication. Coordinates interactions with findClient.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: findClient.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on clientIsPresent.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


20. Client::physicsOutBandwidthExceeded​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool Client::physicsOutBandwidthExceeded(const RBX::Instance* context);
PropertyValue
Return Typebool
ModifiersNone
Source LocationNetwork/Client.cpp:87
SubsystemNetwork & Replication

How it Works Internally​

Executes physicsOutBandwidthExceeded within Network & Replication. Coordinates interactions with findClient, isLimitedByOutgoingBandwidthLimit.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: findClient, isLimitedByOutgoingBandwidthLimit.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on physicsOutBandwidthExceeded.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


21. Client::getNetworkBufferHealth​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

double Client::getNetworkBufferHealth(const RBX::Instance* context);
PropertyValue
Return Typedouble
ModifiersNone
Source LocationNetwork/Client.cpp:99
SubsystemNetwork & Replication

How it Works Internally​

Executes getNetworkBufferHealth within Network & Replication. Coordinates interactions with findClient, GetBufferHealth.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: findClient, GetBufferHealth.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getNetworkBufferHealth.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


22. Client::findLocalSimulatorAddress​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

RBX::SystemAddress Client::findLocalSimulatorAddress(const RBX::Instance* context) const;
PropertyValue
Return TypeRBX::SystemAddress
Modifiersconst
Source LocationNetwork/Client.cpp:108
SubsystemNetwork & Replication

How it Works Internally​

Executes findLocalSimulatorAddress within Network & Replication. Coordinates interactions with findClient, RakNetToRbxAddress, getClientAddress, Unassigned.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: findClient, RakNetToRbxAddress, getClientAddress, Unassigned.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on findLocalSimulatorAddress.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


23. Client::playerConnect​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

shared_ptr<Instance> Client::playerConnect(int userId, std::string server, int serverPort, int clientPort, int threadSleepTime);
PropertyValue
Return Typeshared_ptr&lt;Instance&gt;
ModifiersNone
Source LocationNetwork/Client.cpp:118
SubsystemNetwork & Replication

How it Works Internally​

Executes playerConnect within Network & Replication. Coordinates interactions with FASTLOG3, serverPort, clientPort, threadSleepTime. Employs reference-counted heap object ownership (boost::shared_ptr).

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Reference-counted heap object ownership (boost::shared_ptr).
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: C++ exception throw on invalid state or failure; Standard runtime error exception formulation.
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: FASTLOG3, serverPort, clientPort, threadSleepTime, runtime_error, createLocalPlayer, getPreviousPlaceId, rawPeer, Startup, GetInternalID, remoteAddress, c_str.
  • External Library Dependencies: RakNet UDP Networking Engine, OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on playerConnect.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


24. Client::disconnect​

Status: 🧪 Tested  |  🌐 Cross-Platform Uniform

void Client::disconnect(int blockDuration);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/Client.cpp:193
SubsystemNetwork & Replication

How it Works Internally​

Executes disconnect within Network & Replication. Coordinates interactions with FASTLOG, visitChildren, bind, removeAllChildren.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: FASTLOG, visitChildren, bind, removeAllChildren, rawPeer, CloseConnection, Shutdown.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

This function is exercised in 26 test case(s):

  • CustomEvents::SendValuesOnlyWhenConnected (App.UnitTest/CustomEvents.cpp:127)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(0, callCounter-&gt;calls), BOOST_REQUIRE_EQUAL(0, callCounter-&gt;calls)
    • Callsite Snippet: conn.disconnect();
  • CustomEvents::ValueClamping (App.UnitTest/CustomEvents.cpp:188)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(0, evt-&gt;getPersistedCurrentValue()), BOOST_REQUIRE_EQUAL(1, evt-&gt;getPersistedCurrentValue())
    • Callsite Snippet: conn.disconnect();
  • CustomEvents::SettingParentToNullDoesBreakConnection (App.UnitTest/CustomEvents.cpp:239)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(1, callCounter-&gt;calls), BOOST_REQUIRE_EQUAL(.1f, callCounter-&gt;lastValue)
    • Callsite Snippet: conn.disconnect();
  • CustomEvents::BreakingConnectionSetsReceiverToZero (App.UnitTest/CustomEvents.cpp:301)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(1, callCounter-&gt;calls), BOOST_REQUIRE_EQUAL(.1f, callCounter-&gt;lastValue)
    • Callsite Snippet: conn.disconnect();

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


25. Client::setGameSessionID​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Client::setGameSessionID(std::string value);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/Client.cpp:210
SubsystemNetwork & Replication

How it Works Internally​

Executes setGameSessionID within Network & Replication.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setGameSessionID.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


26. Client::configureAsCloudEditClient​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Client::configureAsCloudEditClient();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/Client.cpp:218
SubsystemNetwork & Replication

How it Works Internally​

Executes configureAsCloudEditClient within Network & Replication.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on configureAsCloudEditClient.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


27. Client::isCloudEdit​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool Client::isCloudEdit() const;
PropertyValue
Return Typebool
Modifiersconst
Source LocationNetwork/Client.cpp:223
SubsystemNetwork & Replication

How it Works Internally​

Executes isCloudEdit within Network & Replication.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isCloudEdit.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


28. Client::onServiceProvider​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

void Client::onServiceProvider(ServiceProvider* oldProvider, ServiceProvider* newProvider);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/Client.cpp:228
SubsystemNetwork & Replication

How it Works Internally​

Executes onServiceProvider within Network & Replication. Coordinates interactions with disconnect, now, setConnection, get. Employs heap memory deallocation via operator delete.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Multi-case state dispatch, Explicit result return.
  • Memory Management: Heap memory deallocation via operator delete; Reference-counted heap object ownership (boost::shared_ptr).
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT); Exception handling block (try/catch recovery).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: disconnect, now, setConnection, get, doIt, connect, bind, sendVersionInfo, rawPeer, Send, getDataSendPriority, sendTicket.
  • External Library Dependencies: Boost C++ Libraries, RakNet UDP Networking Engine, OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on onServiceProvider.

Behavioral Differences Across Code Files​

Divergence Analysis: Behavior branches internally via conditional compilation for: Windows (Win32/x64 API).

  • Platform Preprocessor Guards: Windows (Win32/x64 API)

29. Client::sendVersionInfo​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Client::sendVersionInfo();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/Client.cpp:261
SubsystemNetwork & Replication

How it Works Internally​

Executes sendVersionInfo within Network & Replication. Coordinates interactions with rawPeer, Send, getDataSendPriority.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: rawPeer, Send, getDataSendPriority.
  • External Library Dependencies: RakNet UDP Networking Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on sendVersionInfo.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


30. Client::sendTicket​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Client::sendTicket();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/Client.cpp:270
SubsystemNetwork & Replication

How it Works Internally​

Executes sendTicket within Network & Replication. Coordinates interactions with serializeStringCompressed, singleton, osPlatform, getRobloxProductName.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: serializeStringCompressed, singleton, osPlatform, getRobloxProductName, encryptDataPart, rawPeer, Send, getDataSendPriority.
  • External Library Dependencies: RakNet UDP Networking Engine, OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on sendTicket.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


31. rakIdToString​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

std::string rakIdToString(int id);
PropertyValue
Return Typestd::string
ModifiersNone
Source LocationNetwork/Client.cpp:301
SubsystemNetwork & Replication

How it Works Internally​

Executes rakIdToString within Network & Replication. Coordinates interactions with format.

  • Control Flow & Execution: Multi-case state dispatch, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: format.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on rakIdToString.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


32. Client::OnFailedConnectionAttempt​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Client::OnFailedConnectionAttempt(RakNet::Packet *packet, RakNet::PI2_FailedConnectionAttemptReason failedConnectionAttemptReason);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/Client.cpp:317
SubsystemNetwork & Replication

How it Works Internally​

Executes OnFailedConnectionAttempt within Network & Replication. Coordinates interactions with rakIdToString, singleton, printf, RakNetAddressToString.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: rakIdToString, singleton, printf, RakNetAddressToString, c_str, connectionFailedSignal.
  • External Library Dependencies: OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on OnFailedConnectionAttempt.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


33. programMemoryPermissionsHackChecker​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void programMemoryPermissionsHackChecker(weak_ptr<DataModel> weakDataModel);
PropertyValue
Return Typevoid
Modifiersstatic
Source LocationNetwork/Client.cpp:327
SubsystemNetwork & Replication

How it Works Internally​

Executes programMemoryPermissionsHackChecker within Network & Replication. Coordinates interactions with VMProtectBeginMutation, lock, FASTLOG, areMemoryPagePermissionsSetupForHacking. Employs reference-counted heap object ownership (boost::shared_ptr).

  • Control Flow & Execution: Iterative loop processing, Conditional branching.
  • Memory Management: Reference-counted heap object ownership (boost::shared_ptr).
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: VMProtectBeginMutation, lock, FASTLOG, areMemoryPagePermissionsSetupForHacking, FASTLOG1, sleep, milliseconds, VMProtectEnd.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on programMemoryPermissionsHackChecker.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


34. Client::sendPreferedSpawnName​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Client::sendPreferedSpawnName() const;
PropertyValue
Return Typevoid
Modifiersconst
Source LocationNetwork/Client.cpp:345
SubsystemNetwork & Replication

How it Works Internally​

Executes sendPreferedSpawnName within Network & Replication. Coordinates interactions with serializeStringCompressed, GetSpawnName, FASTLOGS, RakNetAddressToString.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: serializeStringCompressed, GetSpawnName, FASTLOGS, RakNetAddressToString, c_str, rawPeer, Send, getDataSendPriority.
  • External Library Dependencies: RakNet UDP Networking Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on sendPreferedSpawnName.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


35. Client::HandleConnection​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

void Client::HandleConnection(RakNet::Packet *packet);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/Client.cpp:357
SubsystemNetwork & Replication

How it Works Internally​

Executes HandleConnection within Network & Replication. Coordinates interactions with getPreviousPlaceId, rawPeer, Send, getDataSendPriority. Employs reference-counted heap object ownership (boost::shared_ptr).

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Reference-counted heap object ownership (boost::shared_ptr).
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Exception handling block (try/catch recovery).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: getPreviousPlaceId, rawPeer, Send, getDataSendPriority, sendTicket, sendPreferedSpawnName, findWorkspace, clearTerrain, GetExternalID, setAndLockParent, defined, VMProtectBeginMutation.
  • External Library Dependencies: Boost C++ Libraries, RakNet UDP Networking Engine, OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on HandleConnection.

Behavioral Differences Across Code Files​

Divergence Analysis: Behavior branches internally via conditional compilation for: Windows (Win32/x64 API).

  • Platform Preprocessor Guards: Windows (Win32/x64 API)

36. Client::OnReceive​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

RakNet::PluginReceiveResult Client::OnReceive(RakNet::Packet *packet);
PropertyValue
Return TypeRakNet::PluginReceiveResult
ModifiersNone
Source LocationNetwork/Client.cpp:410
SubsystemNetwork & Replication

How it Works Internally​

Executes OnReceive within Network & Replication. Coordinates interactions with singleton, printf, RakNetAddressToString, c_str.

  • Control Flow & Execution: Conditional branching, Multi-case state dispatch, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: singleton, printf, RakNetAddressToString, c_str, HandleConnection, sendVersionInfo, connectionFailedSignal, rakIdToString, connectionRejectedSignal, RBXASSERT.
  • External Library Dependencies: RakNet UDP Networking Engine, OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on OnReceive.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


37. setTicket​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void setTicket(const std::string& t);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/Client.h:34
SubsystemNetwork & Replication

How it Works Internally​

Executes setTicket within Network & Replication.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setTicket.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


38. disconnect​

Status: 🧪 Tested  |  🌐 Cross-Platform Uniform

void disconnect();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/Client.h:39
SubsystemNetwork & Replication

How it Works Internally​

Executes disconnect within Network & Replication.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

This function is exercised in 26 test case(s):

  • CustomEvents::SendValuesOnlyWhenConnected (App.UnitTest/CustomEvents.cpp:127)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(0, callCounter-&gt;calls), BOOST_REQUIRE_EQUAL(0, callCounter-&gt;calls)
    • Callsite Snippet: conn.disconnect();
  • CustomEvents::ValueClamping (App.UnitTest/CustomEvents.cpp:188)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(0, evt-&gt;getPersistedCurrentValue()), BOOST_REQUIRE_EQUAL(1, evt-&gt;getPersistedCurrentValue())
    • Callsite Snippet: conn.disconnect();
  • CustomEvents::SettingParentToNullDoesBreakConnection (App.UnitTest/CustomEvents.cpp:239)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(1, callCounter-&gt;calls), BOOST_REQUIRE_EQUAL(.1f, callCounter-&gt;lastValue)
    • Callsite Snippet: conn.disconnect();
  • CustomEvents::BreakingConnectionSetsReceiverToZero (App.UnitTest/CustomEvents.cpp:301)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(1, callCounter-&gt;calls), BOOST_REQUIRE_EQUAL(.1f, callCounter-&gt;lastValue)
    • Callsite Snippet: conn.disconnect();

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


39. doScans​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

void doScans(unsigned int scanMask);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationNetwork/ClientReplicator.cpp:149
SubsystemNetwork & Replication

How it Works Internally​

Executes doScans within Network & Replication. Coordinates interactions with defined, VMProtectBeginMutation, get, isCeBadDll. Employs dynamic heap allocation via c++ operator new.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Dynamic heap allocation via C++ operator new; Reference-counted heap object ownership (boost::shared_ptr); Unique RAII pointer lifetime control (boost::scoped_ptr).
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: defined, VMProtectBeginMutation, get, isCeBadDll, checkAndLocalUpdate, kernelUpdate, scan, detectTitle, detectFakeAttach, detectEarlyKick, isSpeedhack, VMProtectEnd.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on doScans.

Behavioral Differences Across Code Files​

Divergence Analysis: Behavior branches internally via conditional compilation for: Windows (Win32/x64 API).

  • Platform Preprocessor Guards: Windows (Win32/x64 API)

40. sleepTime​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

Time::Interval sleepTime(const Stats& stats);
PropertyValue
Return TypeTime::Interval
Modifiersvirtual
Source LocationNetwork/ClientReplicator.cpp:204
SubsystemNetwork & Replication

How it Works Internally​

Executes sleepTime within Network & Replication. Coordinates interactions with computeStandardSleepTime.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: computeStandardSleepTime.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on sleepTime.

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: XboxClient/renderJob.cpp, App/util/Win/CheatEngine.cpp, WindowsClient/RenderJob.cpp.

  • Alternative Implementation Files: XboxClient/renderJob.cpp, App/util/Win/CheatEngine.cpp, WindowsClient/RenderJob.cpp

41. error​

Status: 🧪 Tested  |  ⚠️ Platform Divergent

Error error(const Stats& stats);
PropertyValue
Return TypeError
Modifiersvirtual
Source LocationNetwork/ClientReplicator.cpp:209
SubsystemNetwork & Replication

How it Works Internally​

Executes error within Network & Replication. Coordinates interactions with computeStandardErrorCyclicExecutiveSleeping.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: computeStandardErrorCyclicExecutiveSleeping.

How it is Used in Tests​

This function is exercised in 2 test case(s):

  • LuaReflection::ypcallFailure (App.UnitTest/LuaReflection.cpp:261)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(result-&gt;values.size(), 2), BOOST_CHECK_EQUAL(result-&gt;values.at(0).get&lt;bool&gt;(), false)
    • Callsite Snippet: "return ypcall(function() error('failure') end) "
  • LuaReflection::Events2 (App.UnitTest/LuaReflection.cpp:636)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK_EQUAL(event2Value, 2), BOOST_CHECK_EQUAL(event2Value, 1)
    • Callsite Snippet: " error('ha!')\n"

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: XboxClient/async.h, App/util/Win/CheatEngine.cpp.

  • Alternative Implementation Files: XboxClient/async.h, App/util/Win/CheatEngine.cpp

42. stepDataModelJob​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

TaskScheduler::StepResult stepDataModelJob(const Stats& stats);
PropertyValue
Return TypeTaskScheduler::StepResult
Modifiersvirtual
Source LocationNetwork/ClientReplicator.cpp:214
SubsystemNetwork & Replication

How it Works Internally​

Executes stepDataModelJob within Network & Replication. Coordinates interactions with VMProtectBeginMutation, doScans, nowFast, VMProtectEnd.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: VMProtectBeginMutation, doScans, nowFast, VMProtectEnd.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on stepDataModelJob.

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: XboxClient/renderJob.cpp, WindowsClient/RenderJob.cpp.

  • Alternative Implementation Files: XboxClient/renderJob.cpp, WindowsClient/RenderJob.cpp

43. getLastRunTime​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Time getLastRunTime() const;
PropertyValue
Return TypeTime
Modifiersconst
Source LocationNetwork/ClientReplicator.cpp:224
SubsystemNetwork & Replication

How it Works Internally​

Executes getLastRunTime within Network & Replication.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getLastRunTime.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


44. sleepTime​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

Time::Interval sleepTime(const Stats& stats);
PropertyValue
Return TypeTime::Interval
Modifiersvirtual
Source LocationNetwork/ClientReplicator.cpp:267
SubsystemNetwork & Replication

How it Works Internally​

Executes sleepTime within Network & Replication. Coordinates interactions with computeStandardSleepTime.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: computeStandardSleepTime.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on sleepTime.

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: XboxClient/renderJob.cpp, App/util/Win/CheatEngine.cpp, WindowsClient/RenderJob.cpp.

  • Alternative Implementation Files: XboxClient/renderJob.cpp, App/util/Win/CheatEngine.cpp, WindowsClient/RenderJob.cpp

45. error​

Status: 🧪 Tested  |  ⚠️ Platform Divergent

Error error(const Stats& stats);
PropertyValue
Return TypeError
Modifiersvirtual
Source LocationNetwork/ClientReplicator.cpp:272
SubsystemNetwork & Replication

How it Works Internally​

Executes error within Network & Replication. Coordinates interactions with computeStandardError.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: computeStandardError.

How it is Used in Tests​

This function is exercised in 2 test case(s):

  • LuaReflection::ypcallFailure (App.UnitTest/LuaReflection.cpp:261)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(result-&gt;values.size(), 2), BOOST_CHECK_EQUAL(result-&gt;values.at(0).get&lt;bool&gt;(), false)
    • Callsite Snippet: "return ypcall(function() error('failure') end) "
  • LuaReflection::Events2 (App.UnitTest/LuaReflection.cpp:636)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK_EQUAL(event2Value, 2), BOOST_CHECK_EQUAL(event2Value, 1)
    • Callsite Snippet: " error('ha!')\n"

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: XboxClient/async.h, App/util/Win/CheatEngine.cpp.

  • Alternative Implementation Files: XboxClient/async.h, App/util/Win/CheatEngine.cpp

46. stepDataModelJob​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

TaskScheduler::StepResult stepDataModelJob(const Stats& stats);
PropertyValue
Return TypeTaskScheduler::StepResult
Modifiersvirtual
Source LocationNetwork/ClientReplicator.cpp:277
SubsystemNetwork & Replication

How it Works Internally​

Executes stepDataModelJob within Network & Replication. Coordinates interactions with VMProtectBeginMutation, get, getThreadContext, step. Employs dynamic heap allocation via c++ operator new.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Multi-case state dispatch, Explicit result return.
  • Memory Management: Dynamic heap allocation via C++ operator new; Reference-counted heap object ownership (boost::shared_ptr).
  • Concurrency & Thread Safety: TaskScheduler global job queue dispatching.
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT); C++ exception throw on invalid state or failure; Standard runtime error exception formulation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: VMProtectBeginMutation, get, getThreadContext, step, getLastCompletedHash, updateHsceHash, getHsceAndHash, getHsceOrHash, addHackFlag, defined, getLastGoldenHash, getLastCompletedTime.
  • External Library Dependencies: Boost C++ Libraries, RakNet UDP Networking Engine, OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on stepDataModelJob.

Behavioral Differences Across Code Files​

Divergence Analysis: Behavior branches internally via conditional compilation for: Windows (Win32/x64 API). Alternative platform-specific implementations exist in: XboxClient/renderJob.cpp, WindowsClient/RenderJob.cpp.

  • Platform Preprocessor Guards: Windows (Win32/x64 API)
  • Alternative Implementation Files: XboxClient/renderJob.cpp, WindowsClient/RenderJob.cpp

47. getLastRunTime​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Time getLastRunTime() const;
PropertyValue
Return TypeTime
Modifiersconst
Source LocationNetwork/ClientReplicator.cpp:366
SubsystemNetwork & Replication

How it Works Internally​

Executes getLastRunTime within Network & Replication.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getLastRunTime.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


48. getLastHashTime​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Time getLastHashTime() const;
PropertyValue
Return TypeTime
Modifiersconst
Source LocationNetwork/ClientReplicator.cpp:370
SubsystemNetwork & Replication

How it Works Internally​

Executes getLastHashTime within Network & Replication.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getLastHashTime.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


49. memPermissionChanged​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool memPermissionChanged(uintptr_t regionBase, size_t regionSize, size_t protection);
PropertyValue
Return Typebool
Modifiers__forceinline
Source LocationNetwork/ClientReplicator.cpp:390
SubsystemNetwork & Replication

How it Works Internally​

Executes memPermissionChanged within Network & Replication. Coordinates interactions with virtualQuery, memset.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: virtualQuery, memset.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on memPermissionChanged.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


50. populateMccReport​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void populateMccReport(RBX::Network::MccReport& report);
PropertyValue
Return Typevoid
Modifiers__forceinline
Source LocationNetwork/ClientReplicator.cpp:405
SubsystemNetwork & Replication

How it Works Internally​

Executes populateMccReport within Network & Replication. Coordinates interactions with getLastRunTime, timestampSeconds, getLastHashTime, nowFast.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: getLastRunTime, timestampSeconds, getLastHashTime, nowFast.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on populateMccReport.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


51. sleepTime​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

Time::Interval sleepTime(const Stats& stats);
PropertyValue
Return TypeTime::Interval
Modifiersvirtual
Source LocationNetwork/ClientReplicator.cpp:433
SubsystemNetwork & Replication

How it Works Internally​

Executes sleepTime within Network & Replication. Coordinates interactions with computeStandardSleepTime.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: computeStandardSleepTime.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on sleepTime.

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: XboxClient/renderJob.cpp, App/util/Win/CheatEngine.cpp, WindowsClient/RenderJob.cpp.

  • Alternative Implementation Files: XboxClient/renderJob.cpp, App/util/Win/CheatEngine.cpp, WindowsClient/RenderJob.cpp

52. error​

Status: 🧪 Tested  |  ⚠️ Platform Divergent

Error error(const Stats& stats);
PropertyValue
Return TypeError
Modifiersvirtual
Source LocationNetwork/ClientReplicator.cpp:438
SubsystemNetwork & Replication

How it Works Internally​

Executes error within Network & Replication. Coordinates interactions with computeStandardErrorCyclicExecutiveSleeping.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: computeStandardErrorCyclicExecutiveSleeping.

How it is Used in Tests​

This function is exercised in 2 test case(s):

  • LuaReflection::ypcallFailure (App.UnitTest/LuaReflection.cpp:261)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(result-&gt;values.size(), 2), BOOST_CHECK_EQUAL(result-&gt;values.at(0).get&lt;bool&gt;(), false)
    • Callsite Snippet: "return ypcall(function() error('failure') end) "
  • LuaReflection::Events2 (App.UnitTest/LuaReflection.cpp:636)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK_EQUAL(event2Value, 2), BOOST_CHECK_EQUAL(event2Value, 1)
    • Callsite Snippet: " error('ha!')\n"

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: XboxClient/async.h, App/util/Win/CheatEngine.cpp.

  • Alternative Implementation Files: XboxClient/async.h, App/util/Win/CheatEngine.cpp

53. stepDataModelJob​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

TaskScheduler::StepResult stepDataModelJob(const Stats& stats);
PropertyValue
Return TypeTaskScheduler::StepResult
Modifiersvirtual
Source LocationNetwork/ClientReplicator.cpp:443
SubsystemNetwork & Replication

How it Works Internally​

Executes stepDataModelJob within Network & Replication. Coordinates interactions with VMProtectBeginMutation, defined, memPermissionChanged, getThreadContext.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: VMProtectBeginMutation, defined, memPermissionChanged, getThreadContext, isNtdllAddress, populateMccReport, reportReadySignal, FreeConsole, VMProtectEnd, VMProtectBeginVirtualization.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on stepDataModelJob.

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: XboxClient/renderJob.cpp, WindowsClient/RenderJob.cpp.

  • Alternative Implementation Files: XboxClient/renderJob.cpp, WindowsClient/RenderJob.cpp

54. ClientReplicator::createStatsItem​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

shared_ptr<Replicator::Stats> ClientReplicator::createStatsItem();
PropertyValue
Return Typeshared_ptr&lt;Replicator::Stats&gt;
ModifiersNone
Source LocationNetwork/ClientReplicator.cpp:568
SubsystemNetwork & Replication

How it Works Internally​

Executes createStatsItem within Network & Replication. Coordinates interactions with shared_from.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: shared_from.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on createStatsItem.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


55. ClientReplicator::findTargetPlayer​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Player* ClientReplicator::findTargetPlayer() const;
PropertyValue
Return TypePlayer*
Modifiersconst
Source LocationNetwork/ClientReplicator.cpp:616
SubsystemNetwork & Replication

How it Works Internally​

Executes findTargetPlayer within Network & Replication. Coordinates interactions with getLocalPlayer.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: getLocalPlayer.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on findTargetPlayer.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


56. ClientReplicator::isLegalSendInstance​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool ClientReplicator::isLegalSendInstance(const Instance* instance);
PropertyValue
Return Typebool
ModifiersNone
Source LocationNetwork/ClientReplicator.cpp:621
SubsystemNetwork & Replication

How it Works Internally​

Executes isLegalSendInstance within Network & Replication. Coordinates interactions with filterNew, getParent, settings, singleton.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: filterNew, getParent, settings, singleton, printf, getFullName, c_str.
  • External Library Dependencies: OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isLegalSendInstance.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


57. ClientReplicator::isLegalSendProperty​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool ClientReplicator::isLegalSendProperty(Instance* instance, const Reflection::PropertyDescriptor& desc);
PropertyValue
Return Typebool
ModifiersNone
Source LocationNetwork/ClientReplicator.cpp:637
SubsystemNetwork & Replication

How it Works Internally​

Executes isLegalSendProperty within Network & Replication. Coordinates interactions with filterParent, getParent, filterChangedProperty, canReplicate.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: filterParent, getParent, filterChangedProperty, canReplicate, settings, singleton, printf, c_str, getFullName, isCloudEdit, getCurrentEditor, RBXASSERT.
  • External Library Dependencies: OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isLegalSendProperty.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


58. ClientReplicator::isLegalSendEvent​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool ClientReplicator::isLegalSendEvent(Instance* instance, const Reflection::EventDescriptor& desc);
PropertyValue
Return Typebool
ModifiersNone
Source LocationNetwork/ClientReplicator.cpp:671
SubsystemNetwork & Replication

How it Works Internally​

Executes isLegalSendEvent within Network & Replication. Coordinates interactions with filterEvent, settings, singleton, printf.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: filterEvent, settings, singleton, printf, c_str, getFullName.
  • External Library Dependencies: OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isLegalSendEvent.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


59. ClientReplicator::canSendItems​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool ClientReplicator::canSendItems();
PropertyValue
Return Typebool
ModifiersNone
Source LocationNetwork/ClientReplicator.cpp:684
SubsystemNetwork & Replication

How it Works Internally​

Executes canSendItems within Network & Replication.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on canSendItems.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


60. ClientReplicator::isCloudEdit​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool ClientReplicator::isCloudEdit() const;
PropertyValue
Return Typebool
Modifiersconst
Source LocationNetwork/ClientReplicator.cpp:689
SubsystemNetwork & Replication

How it Works Internally​

Executes isCloudEdit within Network & Replication. Coordinates interactions with getParent.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: getParent.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isCloudEdit.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


Additional Functions

There are 1486 additional internal and inline functions in this subsystem. All functions are indexed and cross-referenced in the Complete Function Catalog.