nova_getAvatar
Fetch an avatar's current state (position, animation, presence).
Method
nova_getAvatar is registered in the canonical JSON-RPC catalog. Use POST /rpc, Content-Type: application/json, JSON-RPC 2.0 and a caller-controlled request id. Node RPC profile, build feature and runtime activation checks still apply.
Fetch an avatar's current state (position, animation, presence).
Request binding
Source handler: rpc_nova::handle_get_avatar in sigil/node/sigil-node/src/rpc_nova.rs, line 58.
The handler uses no directly named params.get fields, or delegates input parsing to a typed helper. Use the request types below rather than assuming an empty parameter object.
Parsing excerpt
These source excerpts show binding and validation; they are not runnable client code.
let avatar_id = match extract_string_param(&req.params, 0, "avatar_id") {
Some(id) => id,
None => {
let world_id = match extract_string_param(&req.params, 0, "world_id") {
Some(id) => id,
None => {
return RpcResponse::error(
req.id.clone(),
-32602,
"missing 'avatar_id' or world_id/owner_did parameters",
)
}
let world_id = match extract_string_param(&req.params, 0, "world_id") {
Some(id) => id,
None => {
return RpcResponse::error(
req.id.clone(),
-32602,
"missing 'avatar_id' or world_id/owner_did parameters",
)
}
};
let owner_did = match extract_string_param(&req.params, 1, "owner_did") {
Some(id) => id,
None => {
return RpcResponse::error(
req.id.clone(),
-32602,
"missing 'owner_did' parameter",
)
}
};Responses and failures
Check HTTP status, parse the JSON-RPC envelope, reject error, and require result on success. Preserve large base-unit integers without floating-point rounding. A catalog method does not bypass authentication, capability, policy or activation requirements.