Unreal Engine 5.8 Upgrade

[spirit986]

Summary

Attempts to give Clade the expertise / "support" for Unreal Engine 5.8

Upgraded with two Fable 5 sessions. The first one on high effort did the initial upgrade.
The 2nd with xhigh effort did the review and polished some inconsistencies.

Type of Change

• New agent
• New skill - Unreal Engine 5.8
• New hook or rule
• Bug fix
• Documentation improvement - Yes fixed some inconsistencies in the documentation
• Other:

Changes

• Adde Version Awareness sections telling Claude if using UE5.8 to verify against the documentation first.

Checklist

• I've tested this in a Claude Code session - IN PROGRESS
• New agents include the Collaboration Protocol section
• New skills use the subdirectory format (.claude/skills/<name>/SKILL.md)
• Reference docs are updated (agent-roster, skills-reference, hooks-reference, rules-reference)
• Hooks use grep -E (POSIX) and fail gracefully without jq/python
• No hardcoded paths or platform-specific assumptions

---

Additional Info

While I am about to test this soon I also attempted to gain understanding what the implication to be if using this with UE5.8 so here are Claude's answers.

How working with UE5.8 will impact the work:

1. First, tell me when is your knowledge cutoff date and is it before or after UE5.8 was released.
2. 2nd What happens when you get asked about UE5.8 how do you come to the answer.
3. 3rd, what are the implications if when one works with UE5.8 and asks you for help?

Answers

1. My knowledge cutoff vs UE 5.8

My training cutoff is January 2026. UE 5.8 was released June 2026 — about five months after my cutoff. I have zero training data about it: not its features, not its APIs, not even the fact that it exists. And in practice the gap is wider than the hard cutoff suggests — deep, reliable coverage of an engine needs time for docs, tutorials, and forum discussion to accumulate, so my genuinely trustworthy Unreal knowledge is more like ~5.3, which is exactly what your VERSION.md assumes. (The docs record "LLM Knowledge Cutoff: May 2025" — older than my actual cutoff, but keeping the conservative floor is correct since other models/agents may serve this project.)

2. How I answer UE 5.8 questions

In layers:

1. Training data for the stable core — AActor/UObject lifecycle, UPROPERTY, replication basics, UMG, GAS fundamentals. These APIs are years old and barely change; my knowledge there is solid.
2. The curated reference library (docs/engine-reference/unreal/) for everything post-cutoff. It was populated by live web research — the previous session fetched Epic's actual 5.8 release notes and migration guides and distilled them into these files. When I say "WASAPI is the Windows default in 5.8," I'm reading that from the repo, not remembering it.
3. Live WebSearch for anything the docs don't cover.

The dangerous failure mode is skipping layers 2–3: I would then extrapolate from 5.0–5.3 patterns and produce fluent, plausible, confidently-worded answers that can be silently wrong — with no internal signal that I'm guessing. That's precisely why this upgrade wired the "Version Awareness" section into all five UE specialist agents: it forces the doc check before any API suggestion.

3. Implications when you work with UE 5.8 and ask me for help

• Concrete examples of what I'd get wrong unaided, all from this very upgrade: I'd assume XAudio2 is the Windows audio backend (it's WASAPI now), wouldn't know 5.8 requires VS2026/MSVC v145 and BuildSettingsVersion.V7, wouldn't know Iris and Mutable went production-ready, and wouldn't warn you that Sequencer looping behavior changed.
• Trust calibration: core gameplay C++/Blueprint questions — fine. Anything involving defaults, build config, plugin maturity status, or "what's the modern way to do X" — only trust answers that cite the reference docs or fresh web results. If I name a 5.8 API without a reference, treat it as unverified.
• The docs are the single point of failure: a curation error propagates into every answer. My review caught exactly this class of bug — the docs claimed Mutable was "Experimental in 5.5–5.7" when it's been Experimental since UE 5.2 (the one 5.8-doc claim I could check against training, and it was wrong — a useful calibration signal). Re-verify the docs as 5.8.x hotfixes land, and update Last Docs Verified when you do.