Editor.MapDoc / MapGameObject

.ctor

.ctor(Editor.MapDoc.MapDocument,Sandbox.GameObject) -> System.Void

Overview

Declared construction entry point; allocation and lifecycle effects remain build-specific.

.ctor constructs the recorded type using signature .ctor(Editor.MapDoc.MapDocument,Sandbox.GameObject) -> System.Void; runtime effects remain unverified.

Parameters / inputs

Result and evidenced effects

Declared return: System.Void. A void return is not evidence of no side effect; consult the linked source and workflow constraints.

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: editor
• A public declaration is not proof of sandbox allowlisting.
• No compile/runtime verification was run.

Prerequisites and limits

• Resolve the declaring type and exact overload signature before relying on this declaration.

Still unknown

• Installed-build callability, compile behaviour and runtime effects are not established by this snapshot.

declaration-and-sourcemetadata-and-source-only

Evidence and verification

Related workflows

None selected.

Related diagrams

None selected.