📮 RPC Payload Helpers
Short Description
Blueprint helpers for building AutoReplication RPC payloads and arguments.
Long Description
The payload library provides functions to create FGorgeousRPCPayload instances and append typed arguments. It handles serialization details so you can keep handler signatures clean and consistent.
🚀 Features
- Create payloads with a handler name.
- Add typed arguments (bool, int, float, string, name).
- Wildcard argument support via custom thunk.
📚 Usage Examples
Use Make AutoReplication RPC Payload then Add RPC Argument nodes to build the payload.
FGorgeousRPCPayload Payload = UGorgeousAutoReplicationRPCPayloadLibrary::MakeAutoReplicationRPCPayload(TEXT("HandleInvite"));
UGorgeousAutoReplicationRPCPayloadLibrary::AddAutoReplicationRPCStringArgument(Payload, TEXT("InviteCode"), TEXT("ABC123"));AddAutoReplicationRPCArgument
Adds a wildcard argument to the payload using a custom thunk. The argument name must match the handler function parameter.
| Parameter Name | Type | Description |
|---|---|---|
Payload |
FGorgeousRPCPayload& |
Payload being built. |
ArgumentName |
FName |
Parameter name used by the handler. |
Value |
wildcard |
Value to serialize into the payload. |
Add Add RPC Argument (Wildcard) and connect a value that matches your handler parameter type.
Best Practices
- Keep handler parameter names stable; payload argument names must match.
- Use typed helpers when possible to avoid wildcard mismatches.
Troubleshooting
- If a handler parameter is not filled, verify the argument name matches exactly.
- If serialization fails, ensure the argument type is Blueprint-compatible.