<aside> <img src="/icons/reorder_gray.svg" alt="/icons/reorder_gray.svg" width="40px" />

Menu

</aside>

Frostbyte’s Unreal Documentation

Intro

FAQ

Getting Started

Blueprint Principals

Blueprint Conventions

Folder Structure

Core Blueprints

Base Player Controller

Base HUD and GUI

Established systems

Doors

Debugging Tools

Better Print String

Links

References

Misc

Base template page

<aside> 💡

General guidelines that will strongly benefit you and potential collaborators!

</aside>

The 3 R’s

• Comment your blueprints • Create helper functions • Collapse your nodes • Include descriptions (tooltips) • Do not make graphs too large to read | | Reusability | Keeping code modular can make the world of a difference for scalability.

• Use inheritance, interfaces, components and dispatchers • Avoid duplicating blueprints unless there’s a clear justification | | Reliability | Reliable systems means nothing can break easily.

• Make appropriate variables and functions private • Ensure parent classes are abstract • Add editor warnings for when things could go wrong ◦ This can be done by prints and/or other means |

Other notes

• Each blueprint should have a single purpose
• Keep things designer friendly, such as including instance editable variables, data assets and data tables
• Avoid using string-based events AT ALL COSTS, like tags, “get component by tag”, “set timer by function name”, etc
  • String based events can lead to a destructive workflow from silent errors

Continue to Blueprint Conventions