<aside> ⚠️ Never submit not-compiling blueprint to source control. It may cause unexpected behaviours to the entire game

</aside>

General

Naming convention is exactly the same as presented in Coding Standards specific section.

Variables

• Mark Editable all the variables that are considered safe to change their value, for blueprint configuration purpose
• Mark Editable only Public variables. Avoid to do it with private variables
• All Editable variables should be accompained by a Tooltip that describe how changing the value affects the blueprint exeution
• In a scenario where we have a blueprint that has several variables, consider assigning categories to them

<aside> 💡 You can define sub-categories by using the pipe character |, i.e. Config | Animations.

</aside>

<aside> 💡 i.e.

|-- Config | |-- Animations | |-- Effects | |-- Audio | |-- Recoil | |-- Timings |-- Animations |-- State |-- Visuals

</aside>

on going...