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 File | Path |
|---|---|
API.cpp | Network/API.cpp |
BoostAppend.cpp | Network/BoostAppend.cpp |
ChatFilter.cpp | Network/ChatFilter.cpp |
Client.cpp | Network/Client.cpp |
Client.h | Network/Client.h |
ClientReplicator.cpp | Network/ClientReplicator.cpp |
ClientReplicator.h | Network/ClientReplicator.h |
ClusterUpdateBuffer.cpp | Network/ClusterUpdateBuffer.cpp |
ClusterUpdateBuffer.h | Network/ClusterUpdateBuffer.h |
Compressor.cpp | Network/Compressor.cpp |
ConcurrentRakPeer.cpp | Network/ConcurrentRakPeer.cpp |
ConcurrentRakPeer.h | Network/ConcurrentRakPeer.h |
CrashReporter.cpp | Network/CrashReporter.cpp |
DataBlockEncryptor.cpp | Network/DataBlockEncryptor.cpp |
Dictionary.cpp | Network/Dictionary.cpp |
Dictionary.h | Network/Dictionary.h |
DirectPhysicsReceiver.cpp | Network/DirectPhysicsReceiver.cpp |
ErrorCompPhysicsSender.cpp | Network/ErrorCompPhysicsSender.cpp |
ErrorCompPhysicsSender2.cpp | Network/ErrorCompPhysicsSender2.cpp |
ErrorCompPhysicsSender2.h | Network/ErrorCompPhysicsSender2.h |
GameConfigurer.cpp | Network/GameConfigurer.cpp |
GamePerfMonitor.cpp | Network/GamePerfMonitor.cpp |
GamePerfMonitor.h | Network/GamePerfMonitor.h |
InterpolatingPhysicsReceiver.cpp | Network/InterpolatingPhysicsReceiver.cpp |
InterpolatingPhysicsReceiver.h | Network/InterpolatingPhysicsReceiver.h |
Item.cpp | Network/Item.cpp |
Item.h | Network/Item.h |
Marker.cpp | Network/Marker.cpp |
MechanismItem.cpp | Network/MechanismItem.cpp |
MechanismItem.h | Network/MechanismItem.h |
MovementHistoryJob.cpp | Network/MovementHistoryJob.cpp |
NetPmc.cpp | Network/NetPmc.cpp |
NetworkClusterPacketCache.cpp | Network/NetworkClusterPacketCache.cpp |
NetworkFilter.cpp | Network/NetworkFilter.cpp |
NetworkOwnerJob.cpp | Network/NetworkOwnerJob.cpp |
NetworkPacketCache.cpp | Network/NetworkPacketCache.cpp |
NetworkProfiler.cpp | Network/NetworkProfiler.cpp |
NetworkProfiler.h | Network/NetworkProfiler.h |
NetworkSettings.cpp | Network/NetworkSettings.cpp |
NetworkSettings.h | Network/NetworkSettings.h |
OrderedSet.h | Network/OrderedSet.h |
Peer.cpp | Network/Peer.cpp |
PersistentDataStore.cpp | Network/PersistentDataStore.cpp |
PersistentDataStore.h | Network/PersistentDataStore.h |
PhysicsReceiver.cpp | Network/PhysicsReceiver.cpp |
PhysicsReceiver.h | Network/PhysicsReceiver.h |
PhysicsSender.cpp | Network/PhysicsSender.cpp |
Player.cpp | Network/Player.cpp |
Players.cpp | Network/Players.cpp |
PropertySynchronization.h | Network/PropertySynchronization.h |
Replicator.ChangePropertyItem.cpp | Network/Replicator.ChangePropertyItem.cpp |
Replicator.DeleteInstanceItem.cpp | Network/Replicator.DeleteInstanceItem.cpp |
Replicator.EventInvocationItem.cpp | Network/Replicator.EventInvocationItem.cpp |
Replicator.GCJob.cpp | Network/Replicator.GCJob.cpp |
Replicator.GCJob.h | Network/Replicator.GCJob.h |
Replicator.HashItem.cpp | Network/Replicator.HashItem.cpp |
Replicator.ItemSender.cpp | Network/Replicator.ItemSender.cpp |
Replicator.JoinDataItem.cpp | Network/Replicator.JoinDataItem.cpp |
Replicator.JoinDataItem.h | Network/Replicator.JoinDataItem.h |
Replicator.MarkerItem.cpp | Network/Replicator.MarkerItem.cpp |
Replicator.NewInstanceItem.cpp | Network/Replicator.NewInstanceItem.cpp |
Replicator.NewInstanceItem.h | Network/Replicator.NewInstanceItem.h |
Replicator.PingBackItem.cpp | Network/Replicator.PingBackItem.cpp |
Replicator.PingItem.cpp | Network/Replicator.PingItem.cpp |
Replicator.PingJob.h | Network/Replicator.PingJob.h |
Replicator.ProcessPacketsJob.h | Network/Replicator.ProcessPacketsJob.h |
Replicator.ReferencePropertyChangedItem.cpp | Network/Replicator.ReferencePropertyChangedItem.cpp |
Replicator.RockyItem.cpp | Network/Replicator.RockyItem.cpp |
Replicator.SendDataJob.h | Network/Replicator.SendDataJob.h |
Replicator.StatsItem.cpp | Network/Replicator.StatsItem.cpp |
Replicator.StatsItem.h | Network/Replicator.StatsItem.h |
Replicator.StreamJob.cpp | Network/Replicator.StreamJob.cpp |
Replicator.StreamJob.h | Network/Replicator.StreamJob.h |
Replicator.TagItem.cpp | Network/Replicator.TagItem.cpp |
Replicator.cpp | Network/Replicator.cpp |
Replicator.h | Network/Replicator.h |
ReplicatorStats.cpp | Network/ReplicatorStats.cpp |
RoundRobinPhysicsSender.cpp | Network/RoundRobinPhysicsSender.cpp |
Server.cpp | Network/Server.cpp |
Server.h | Network/Server.h |
ServerReplicator.cpp | Network/ServerReplicator.cpp |
ServerReplicator.h | Network/ServerReplicator.h |
Streaming.cpp | Network/Streaming.cpp |
Streaming.h | Network/Streaming.h |
TopNErrorsPhysicsSender.cpp | Network/TopNErrorsPhysicsSender.cpp |
TopNErrorsPhysicsSender.h | Network/TopNErrorsPhysicsSender.h |
Util.cpp | Network/Util.cpp |
WebChatFilter.cpp | Network/WebChatFilter.cpp |
CompactCFrame.h | Network/include/network/CompactCFrame.h |
CrashReporter.h | Network/include/network/CrashReporter.h |
CrispProxy.h | Network/include/network/CrispProxy.h |
GameConfigurer.h | Network/include/network/GameConfigurer.h |
NetPmc.h | Network/include/network/NetPmc.h |
NetworkClusterPacketCache.h | Network/include/network/NetworkClusterPacketCache.h |
NetworkOwner.h | Network/include/network/NetworkOwner.h |
NetworkPacketCache.h | Network/include/network/NetworkPacketCache.h |
Player.h | Network/include/network/Player.h |
Players.h | Network/include/network/Players.h |
RakNetFast.h | Network/include/network/RakNetFast.h |
rijndael.cpp | Network/rijndael.cpp |
Function Reference
1. SafeInitFree
Status: ⚪ Untested in Suites | 🌐 Cross-Platform Uniform
public: SafeInitFree();
| Property | Value |
|---|---|
| Return Type | public: |
| Modifiers | None |
| Source Location | Network/API.cpp:74 |
| Subsystem | Network & 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.
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();
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | None |
| Source Location | Network/API.cpp:90 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | None |
| Source Location | Network/API.cpp:95 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | shared_ptr<RBX::Network::ServerReplicator> |
| Modifiers | static |
| Source Location | Network/API.cpp:102 |
| Subsystem | Network & 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | static |
| Source Location | Network/API.cpp:107 |
| Subsystem | Network & 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | static |
| Source Location | Network/API.cpp:130 |
| Subsystem | Network & 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/API.cpp:137 |
| Subsystem | Network & 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/API.cpp:150 |
| Subsystem | Network & 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/API.cpp:158 |
| Subsystem | Network & 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/API.cpp:166 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/API.cpp:188 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/API.cpp:194 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | None |
| Source Location | Network/API.cpp:199 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/API.cpp:257 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/API.cpp:277 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | std::size_t |
| Modifiers | None |
| Source Location | Network/BoostAppend.cpp:6 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | None |
| Source Location | Network/ChatFilter.cpp:15 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | Client* |
| Modifiers | None |
| Source Location | Network/Client.cpp:75 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | None |
| Source Location | Network/Client.cpp:82 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | None |
| Source Location | Network/Client.cpp:87 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | double |
| Modifiers | None |
| Source Location | Network/Client.cpp:99 |
| Subsystem | Network & 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.
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;
| Property | Value |
|---|---|
| Return Type | RBX::SystemAddress |
| Modifiers | const |
| Source Location | Network/Client.cpp:108 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | shared_ptr<Instance> |
| Modifiers | None |
| Source Location | Network/Client.cpp:118 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/Client.cpp:193 |
| Subsystem | Network & 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->calls),BOOST_REQUIRE_EQUAL(0, callCounter->calls) - Callsite Snippet:
conn.disconnect();
- Usage Pattern:
CustomEvents::ValueClamping(App.UnitTest/CustomEvents.cpp:188)- Usage Pattern:
Direct Call - Assertions Checked:
BOOST_REQUIRE_EQUAL(0, evt->getPersistedCurrentValue()),BOOST_REQUIRE_EQUAL(1, evt->getPersistedCurrentValue()) - Callsite Snippet:
conn.disconnect();
- Usage Pattern:
CustomEvents::SettingParentToNullDoesBreakConnection(App.UnitTest/CustomEvents.cpp:239)- Usage Pattern:
Direct Call - Assertions Checked:
BOOST_REQUIRE_EQUAL(1, callCounter->calls),BOOST_REQUIRE_EQUAL(.1f, callCounter->lastValue) - Callsite Snippet:
conn.disconnect();
- Usage Pattern:
CustomEvents::BreakingConnectionSetsReceiverToZero(App.UnitTest/CustomEvents.cpp:301)- Usage Pattern:
Direct Call - Assertions Checked:
BOOST_REQUIRE_EQUAL(1, callCounter->calls),BOOST_REQUIRE_EQUAL(.1f, callCounter->lastValue) - Callsite Snippet:
conn.disconnect();
- Usage Pattern:
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/Client.cpp:210 |
| Subsystem | Network & 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/Client.cpp:218 |
| Subsystem | Network & 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.
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;
| Property | Value |
|---|---|
| Return Type | bool |
| Modifiers | const |
| Source Location | Network/Client.cpp:223 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/Client.cpp:228 |
| Subsystem | Network & 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/Client.cpp:261 |
| Subsystem | Network & 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.
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();
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/Client.cpp:270 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | std::string |
| Modifiers | None |
| Source Location | Network/Client.cpp:301 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/Client.cpp:317 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | static |
| Source Location | Network/Client.cpp:327 |
| Subsystem | Network & 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.
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;
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | const |
| Source Location | Network/Client.cpp:345 |
| Subsystem | Network & 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.
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);
| Property | Value |
|---|---|
| Return Type | void |
| Modifiers | None |
| Source Location | Network/Client.cpp:357 |
| Subsystem | Network & 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.
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.