Epok Engine

EPOK RUNTIME

epok::bp::trace

Function · 1 overload

Function

Performs `trace` as part of compiled Blueprint execution and object interaction.

Belongs to
epok::bp
Header
blueprint_runtime.hpp
Overloads
1

Declaration

Declaration
inline void trace(uint32_t, uint32_t, ObjectId, TraceKind = TraceKind::Enter, int32_t = 0)

Performs `trace` as part of compiled Blueprint execution and object interaction.

ParameterTypeMeaning
arg1uint32_tValue supplied for arg1. Keep referenced or pointed-to data valid for the complete call.
arg2uint32_tValue supplied for arg2. Keep referenced or pointed-to data valid for the complete call.
arg3ObjectIdValue supplied for arg3. Keep referenced or pointed-to data valid for the complete call.
arg4TraceKindValue supplied for arg4. Keep referenced or pointed-to data valid for the complete call.
arg5int32_tValue supplied for arg5. Keep referenced or pointed-to data valid for the complete call.

Returns: Nothing (void).

Example

C++ example
#include "blueprint_runtime.hpp"

// Assume these named values have been initialized with valid data:
// uint32_t arg1
// uint32_t arg2
// ObjectId arg3
// TraceKind arg4
// int32_t arg5

epok::bp::trace(arg1, arg2, arg3, arg4, arg5);

Why use it

It provides direct, allocation-conscious access to compiled Blueprint execution and object interaction. No exception-based error path is implied by the signature.

Trade-offs and warnings

This is classified as **Engine internal**. Prefer a higher-level Epok service unless you need this exact control.

Declared in runtime/blueprint_runtime.hpp:329

Related members