🧳 RPC Result Container

Short Description

Object Variable that stores aggregated AutoReplication RPC results for later inspection.

Long Description

UGorgeousRPC_OV captures metadata and return values from AutoReplication RPC responders. It keeps both ordered and keyed result sets so you can inspect results after the async request completes.

🚀 Features

Stores aggregated responder results.
Exposes cached target variable and owner helpers.
Provides lookup by responder key.

📚 Usage Examples

if (ResultContainer->HasResult())
{
    UGorgeousObjectVariable* ReturnVar = ResultContainer->GetCachedTargetVariable();
}

Use Get Cached Results to inspect all responder payloads from a completed request.

`CaptureResult`

Copies RPC metadata and the resolved target into the container for later inspection.

Parameter Name	Type	Description
`InResult`	`FGorgeousAutoReplicationRPCResult`	Result payload to cache.

ResultContainer->CaptureResult(Result);

Best Practices

Use a result container when you need to persist results across frames.
Reset the container before reuse to avoid stale metadata.

Troubleshooting

If HasResult is false, verify the async action provided a container.
If results look empty, confirm the handler wrote a return Object Variable.