SetAiNavigationBlockerBlocksSight: Difference between revisions

From Wiki G1R-MP G1 Remake Multiplayer
Jump to navigation Jump to search
Document new NPC/player-mode API and events available from 0.1.5
 
Release G1R:MP 0.1.5 BUILD144 / Protocol 37; update availability and migration
 
Line 31: Line 31:
== Notes ==
== Notes ==
* Server-side only. Mutations require the blocker to belong to the calling resource.
* Server-side only. Mutations require the blocker to belong to the calling resource.
* Since 0.1.5. This documents the next release; public 0.1.4 does not include these additions.
* Since 0.1.5. Use the matching 0.1.5 client and server (Protocol 37).
* Use matching updated client and server. See [[NPC scripting]] for lifecycle, defaults, combat examples and collision limitations.
* Use matching updated client and server. See [[NPC scripting]] for lifecycle, defaults, combat examples and collision limitations.
* Default blocksSight is true. false makes it navigation-only; it does not disable navigation collision. Only the owning resource may mutate it. Disabled/destroyed blockers do not block sight.
* Default blocksSight is true. false makes it navigation-only; it does not disable navigation collision. Only the owning resource may mutate it. Disabled/destroyed blockers do not block sight.

Latest revision as of 07:34, 26 September 2026

setAiNavigationBlockerBlocksSight

AVAILABLE FROM UPDATE 0.1.5
This function is available in G1R:MP 0.1.5 and later. The contract below includes the compatibility guarantees introduced in that update.

Sets whether an existing custom navigation blocker also blocks NPC sight and projectiles.

Syntax

setAiNavigationBlockerBlocksSight(blockerId, enabled)

Parameters

Name Type Required Description
blockerId string yes Opaque decimal ID returned by createAiNavigationBlocker, owned by this resource.
enabled bool yes true enables the setting, false disables it.

Returns

Returns true when accepted, false for a rejected request. Acceptance is not proof of a rendered animation, projectile release or hit.

Examples

setAiNavigationBlockerBlocksSight(blockerId, false)

Notes

  • Server-side only. Mutations require the blocker to belong to the calling resource.
  • Since 0.1.5. Use the matching 0.1.5 client and server (Protocol 37).
  • Use matching updated client and server. See NPC scripting for lifecycle, defaults, combat examples and collision limitations.
  • Default blocksSight is true. false makes it navigation-only; it does not disable navigation collision. Only the owning resource may mutate it. Disabled/destroyed blockers do not block sight.