FNiagaraParameterMapHistory

List of emitter namespaces encountered as this parameter map was built.

For each node in MapNodeVisitations, record the start index and end index of variables added within the body of the node, i.e. a Get node will record just the values it pulls out directly.

List of nodes that manipulated the parameter map from input to output.

List of pins that manipulated the parameter map from input to output.

Cached off contents of used parameter collections, in case they change during threaded compilation.

Used parameter collections identified during the traversal.

Cached off contents of used parameter collections, in case they change during threaded compilation.

For each variable that was found, identify the pins that read them from the map in order from first to last read.

Are there any warnings that were encountered during the traversal of the graph for a given variable?

For each variable that was found, identify the pins that wrote to them in order from first to last write.

The metadata associated with each variable identified during the traversal.

The variables that have been identified during the traversal.

Add a variable outside the normal get/set node paradigm.

Helper to add a variable to the known list for a parameter map.

Reverses ResolveAsBasicAttribute.

Find a variable by both name and type.

Find a variable by name with no concern for type.

Get the default value for this variable.

Get the output node associated with this graph.

Get the output pin that we traced to build this history object.

Get the first namespace entry for this variable. Optionally includes the trailing period.

Get the pin that added the parameter map to the graph.

Does this parameter contain the "Initial" namespace as one of its intermediate namespaces? If so, remove the "Initial" namespace and return the original value.

Does this parameter start with the "Emitter" namespace? Note that the emitter namespace is an alias for Emitter and System script types and will be specialized to the name of that specific emitter.

Does this parameter start with the "Emitter" namespace? Note that the emitter namespace is an alias for Emitter and System script types and will be specialized to the name of that specific emitter.

Does this parameter start with the "Module" namespace? Note that the emitter namespace is an alias for all non-funcion/module script types and will be specialized to the function call node's name using the module.

Does this parameter start with the "Particles" namespace?

Given the script type and flags, should we treat the Emitter aliased namespace as read-only?

Is this parameter in the special "Engine" namespace?

Are we required to export this variable as an external constant?

Does this variable belong in a namespace that needs to come in as an external constant to this script?

Does this variable belong in a namespace that needs to come in as an external constant to this script?

Does this parameter contain the "Initial" namespace as one of its intermediate namespaces?

Does the variable start with this namespace?

If this is variable is a parameter in one of our tracked collections, return it.

Called to determine if a given variable should be output from a script.

Called to determine if a given variable should be output from a script.

Given the script type and flags, should we treat the System namespace as read-only?

Is this parameter in the special "System" namespace?

Take an input string and make it hlsl safe.

Take a non-namespaced variable and move it to an appropriate external constant namespace for this script type.

Take a non-namespaced variable and move it to an appropriate external constant namespace for this script type.

Called in a depth-first traversal to identify a given Niagara Parameter Map pin that was touched during traversal.

Use the input alias map to resolve any aliases in this input variable name.

Remove the Particles namespace if it exists.

Prepends the namespace string to the variable name.