Niagara Naming Conventions and Best Practices

[Allar]

I haven't been able to dive real deep into Niagara pipelines, so far all my current game dev experience has been on teams that have still been figuring it out.

I'm looking for any and all insight on how to manage, name, and really just best practices of all kinds. Literally anything useful in Niagara authoring that is helpful to know and conform to.

Please discuss here, on the Gamemakin Discord at https://discord.gg/Kdq5dth , or just create pull requests with your contributions. If possible, please include ways you've seen these in practice, pros and cons, possible alternates. Feel free to contact me through other secure means if you would like to talk behind an NDA or encryption.

[dunenkoff]

Got one right off the bat - never ever use spaces in Niagara variable or module names, you gonna have a bad time when you write a custom HLSL code/expression and try to reference that.

[Allar]

Got one right off the bat - never ever use spaces in Niagara variable or module names, you gonna have a bad time when you write a custom HLSL code/expression and try to reference that.

b1f341c

[lucastucious]

We use typical prefix.
NS_ for Niagara system
NE_ for Niagara emitter.

It works great.

Edit : More detailed answer here : #31 (comment)