Mass Forge support request

Copy this template into the support destination listed by the installed release. Replace bracketed prompts, remove sections that do not apply, and review all text and attachments before sending.

Summary

[One sentence describing the problem and its impact.]

Severity

[Critical / High / Normal / Question, using SUPPORT_POLICY.md.]

Reproduction

1. [Start from a blank project, minimal reproduction, or clearly described existing setup.]
2. [List exact assets, traits, nodes, settings, or C++ calls involved.]
3. [Describe the action that triggers the problem.]

Reproduction frequency: [Always / Intermittent, with an approximate rate]

Expected result

[What should happen, citing the relevant guide or API contract when possible.]

Actual result

[What happens instead, including the exact Mass Forge result enum/message.]

Environment

• Mass Forge version: [VersionName from the report]
• Unreal Engine version and changelist: [Exact value from the report]
• Platform and operating system: [Exact values from the report]
• Build target/configuration: [Editor, Development, or Shipping]
• Project type: [Blueprint / C++ / mixed]
• Entity type: [Actorless Mass / represented Mass / ordinary Actor]
• Network context: [Standalone / server / client / not applicable]
• Reproduces with an unmodified Mass Forge release: [Yes / No / Not tested]

Support report

[Paste the reviewed output from Copy Support Report or MassForge.CopySupportReport.]

Relevant assets and configuration

• Entity Config traits: [List]
• Schema domains/attributes involved: [List names and stable slots]
• Effect, damage, ability, targeting, or migration asset IDs: [List]
• Queue/direct execution path: [Describe]
• Recent schema or plugin upgrade: [Describe]

Logs and evidence

[Paste the smallest relevant log excerpt with timestamps. Attach a minimal project, screenshots, or short capture only when needed. Remove credentials, personal data, proprietary content, and unrelated logs.]

Workaround

[Known workaround, or “None.”]

Additional context

[Timing, time dilation, pause/travel state, entity destruction/reuse, LOD/representation changes, or callback/re-entrancy details if relevant.]

Submission checklist

• [ ] Project Health was run immediately before copying the report.
• [ ] The reproduction uses the smallest practical setup.
• [ ] Exact result enums/messages and asset IDs are included.
• [ ] The report and attachments were reviewed and sanitized.
• [ ] No passwords, tokens, private keys, personal data, or unnecessary proprietary files are included.