什么是 Unreal Engine？

本 Unreal Engine 技能为构建高性能游戏的开发者提供深入的技术指导。它专注于避免导致崩溃的常见架构错误，例如不当的垃圾回收或无效的 Actor 生命周期管理。通过在 Openclaw Skills 生态系统中使用此工具，开发者可以确保其 C++ 代码正确暴露给反射系统，同时保持最佳的 Tick 性能和内存效率。

无论您是管理复杂的网络同步，还是通过软引用优化资产加载，此技能都是专业游戏开发的护栏。它架起了原始 C++ 与专业 Unreal Engine 框架之间的桥梁，确保项目在所有支持的平台上保持可扩展性和可维护性。

下载入口:https://github.com/openclaw/skills/tree/main/skills/ivangdavila/unreal-engine

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

Unreal Engine 应用场景

• 管理 UObject 生命周期，防止野指针和内存泄漏。
• 使用服务器权限和 RPC 实现网络多人游戏逻辑。
• 将高性能开销的蓝图逻辑迁移到优化的 C++ Tick 组。
• 配置异步资产加载，以减少关卡切换期间的内存压力。

1. 监控 C++ 类定义，确保正确使用 UPROPERTY 和 UFUNCTION 等宏以保证反射兼容性。
2. 分析 Actor 初始化顺序，防止因在构造函数中访问 World 而导致的崩溃。
3. 评估网络代码，确保正确实现 GetLifetimeReplicatedProps 和权限检查。
4. 推荐使用 TSoftObjectPtr 和 TWeakObjectPtr 以提高内存管理和引用安全性。

Unreal Engine 配置指南

确保您的工作区中已配置 Unreal Engine 环境。然后，您可以使用以下命令启用此技能：

# 将 Unreal Engine 技能添加到您的智能体配置文件中
openclaw install unreal-engine-guide

Unreal Engine 数据架构与分类体系

该技能将其领域知识组织为几个关键技术领域：

name: Unreal Engine
description: Avoid common Unreal mistakes — garbage collection, UPROPERTY macros, replication authority, and asset reference pitfalls.
metadata: {"clawdbot":{"emoji":"??","os":["linux","darwin","win32"]}}

Garbage Collection

• Raw pointers to UObjects get garbage collected — use UPROPERTY() to prevent
• UPROPERTY() marks for GC tracking — without it, pointer becomes dangling
• TWeakObjectPtr for optional references — doesn't prevent collection, check IsValid()
• NewObject() for UObjects — never raw new, GC won't track it

UPROPERTY and UFUNCTION

• UPROPERTY() required for Blueprint access — and for GC tracking
• UFUNCTION() for Blueprint callable/events — also required for replication
• EditAnywhere vs VisibleAnywhere — edit allows changes, visible is read-only
• BlueprintReadWrite vs BlueprintReadOnly — controls Blueprint access level

Actor Lifecycle

• BeginPlay after all components initialized — safe to access components
• Constructor runs on CDO (Class Default Object) — don't spawn actors or access world
• PostInitializeComponents before BeginPlay — for component setup
• EndPlay for cleanup — called on destroy and level transition

Tick Performance

• Disable tick when not needed — PrimaryActorTick.bCanEverTick = false
• Use timers instead of tick + counter — GetWorldTimerManager().SetTimer()
• Tick groups for ordering — PrePhysics, DuringPhysics, PostPhysics
• Blueprint tick expensive — move hot logic to C++

Replication

• Server is authority — clients request, server validates and replicates
• UPROPERTY(Replicated) for variable sync — implement GetLifetimeReplicatedProps
• UFUNCTION(Server) for client-to-server RPC — must be Reliable or Unreliable
• HasAuthority() to check if server — before executing authoritative logic
• Role and RemoteRole for network role checks — ROLE_Authority is server

Asset References

• Hard references load with parent — bloats memory, use for always-needed
• Soft references (TSoftObjectPtr) load on demand — for optional or large assets
• LoadSynchronous() or AsyncLoad for soft refs — don't access until loaded
• Blueprint class references: TSubclassOf — type-safe class selection

Memory and Pointers

• TSharedPtr for non-UObjects — reference counted, auto-deletes
• TUniquePtr for exclusive ownership — can't copy, moves only
• MakeShared() for creation — single allocation for object and control block
• Never mix raw new/delete with smart pointers — choose one pattern

Common Mistakes

• Accessing null actor in Blueprint — use IsValid() node before access
• PIE (Play In Editor) vs packaged build differ — test shipping build
• Hot reload corrupts Blueprints — close editor, build, reopen
• GetWorld() null in constructor — world doesn't exist yet, use BeginPlay
• Spawning in constructor crashes — defer to BeginPlay or later
• FString for display, FName for identifiers — FName is hashed, faster comparison