Facepunch.ActionGraphs / type
DisplayInfo
Facepunch.ActionGraphs.DisplayInfo Overview
Declared type and relationship surface; behavioural intent is not inferred from the metadata alone.
Generated declaration summary
DisplayInfo is a declared class in the pinned release metadata.
Automatically derived from the pinned declaration; this is not a reviewed tutorial or runtime test.
Exact identity & snapshot
Type relationships
Declarations owned by this type
- Facepunch.ActionGraphs.DisplayInfo..ctor(System.String,System.String,System.String,System.String,System.Nullable`1<System.Boolean>,System.String[]) constructor
- Facepunch.ActionGraphs.DisplayInfo.<Clone>$() method
- Facepunch.ActionGraphs.DisplayInfo.Deconstruct(out System.String,out System.String,out System.String,out System.String,out System.Nullable`1<System.Boolean>,out System.String[]) method
- Facepunch.ActionGraphs.DisplayInfo.Format(System.Func`2<System.String,System.Object>,System.Type) method
- Facepunch.ActionGraphs.DisplayInfo.FromAttributes(System.Reflection.ICustomAttributeProvider,System.String) method
- Facepunch.ActionGraphs.DisplayInfo.FromAttributes(System.Reflection.MemberInfo) method
- Facepunch.ActionGraphs.DisplayInfo.FromAttributes(System.Reflection.ParameterInfo) method
- Facepunch.ActionGraphs.DisplayInfo.Description property
- Facepunch.ActionGraphs.DisplayInfo.Group property
- Facepunch.ActionGraphs.DisplayInfo.Hidden property
- Facepunch.ActionGraphs.DisplayInfo.Icon property
- Facepunch.ActionGraphs.DisplayInfo.Tags property
- Facepunch.ActionGraphs.DisplayInfo.Title property
Inherited members
Direct inherited members are not expanded here because the pinned record does not establish a complete inheritance closure.
Flow
The diagram separates the declared inputs, operation and result. Connections describe the recorded relationship; they do not establish execution order or lifecycle behaviour.
Open this operation in the flow explorer →
Examples
No reviewed code example or workflow covers this declaration. Use the exact declaration and inputs/outputs flow as the available local teaching surface, then run a bounded installed-build probe before relying on behaviour. Open the exact declaration flow.
Constraints and pitfalls
- Execution context: game-or-shared-unknown
- A public declaration is not proof of sandbox allowlisting.
- No compile/runtime verification was run.
Prerequisites and limits
- Resolve the type identity in the pinned release before relying on its declaration.
Still unknown
- Installed-build callability, compile behaviour and runtime effects are not established by this snapshot.
- No indexed implementation-source chunk is linked to this declaration; the entry is declaration-only.
declaration-onlymetadata-only
Upstream documentation availability
Documentation text is not copied into this export because the release metadata redistribution licence is unresolved.
Evidence and verification
pinned metadata source correspondence unverified
- declaration: pinned-release-metadata
Installed-build compile/runtime state: not run.
Related workflows
None selected.
Related diagrams
None selected.