c7401864

Guide
- Agents and actions
- Authoring a behaviour tree
- Behaviour trees
- The blackboard
- The AI debugger
- Environment queries
- GOAP
- Perception
- Sensors
- Utility
- Nodes over the world
- Move sets
- Pose constraints
- The variation harness
- Getting content into a running game
- Fuzzing a format that has a grammar
- Symbols
- Component defaults
- Components
- Entity queries
- Booleans and handoff
- The editing pipeline
- Editor scripts
- Element selection
- Face materials
- Foliage mode
- The frame panel
- Icons
- The editor shell
- Inspectors in markup
- Editable meshes in a scene
- Editor modes
- Building to a number
- Scene menus
- The shape tool
- Snapping
- Sub-object picking
- Sculpt and paint mode
- Water mode
- Writing an editor plugin
- Block-out shapes
- Booting an application
- Floating things on water
- Character movement
- Editable meshes
- Growing a forest
- Foliage instances
- Grass
- Mesh booleans
- Mesh operations
- Mesh surfaces
- Networked players
- Players and possession
- Splines
- Terrain brushes
- The terrain heightfield
- Painting a terrain
- Sculpting a heightfield
- Where the water surface is
- Saving and restoring a world
- Leashing and spawn tables
- Attributes and the modifier algebra
- Chat channels, routing and moderation
- Collections, achievements and transmog
- Abilities and damage
- Definitions and the content walk
- Dynamic events and world bosses
- Currencies, vendors, trade, mail and the auction
- Effects
- Gameplay events
- Player housing
- Dungeons, raids and lockouts
- Interactables, gathering and crafting
- Inventory and the container algebra
- Items
- Authoring a loot table
- Loot tables
- Gameplay modules
- Mounts and vehicles
- Levels, talents and reputation
- Arenas, battlegrounds and objectives
- The quest and event-chain editor
- Quests, stages and objectives
- Gameplay randomness
- Requirements
- Weapons and hit claims
- Parties, guilds, friends and presence
- Gameplay tags
- Maps, discovery and travel
- Admission, health and the control plane
- Durable state and the ledger
- The gameplay bridge
- Matchmaking, queues and ratings
- Placing players
- Placing realms
- Shards, keys and specs
- The cluster
- The live verbs, at three in the morning
- The service plane
- Transfer tickets
- Transferring players
- Upgrading a fleet
- Writing a realm
- Choosing a frame
- Drawing foliage
- The ambient split, and the nodes that fill it
- Drawing grass
- Impostors
- Culling and streaming instances
- Turning on dynamic global illumination
- The look profile
- Meshes and materials, type by type
- Drawing particles
- Lighting a scene in lux and lumens
- Making a room look different
- The post-processing node kinds
- Tracing rays against the scene's own triangles
- A pass that reads the frame so far
- Render quality presets
- Making everything cast a shadow
- The Standard Frame
- Drawing a terrain
- Streaming texture mip tails
- Timing the frame on the GPU
- Fog a shadow can fall through
By kind
- Components48
- Systems55
- Controls169
- Shaders63
- Graph nodes64
- Importers28
- Annotations45
- Diagnostics8
- Log events69
All namespaces315
Releases1

InverterDecorator

class

Core/Vixen.Ai/BehaviorTrees/Nodes/FlowDecorators.cs:26

csharp

public sealed class InverterDecorator

Inverts what the node it is attached to returns.

Read the guide page for this →

Remarks

Gates nothing: a node under an inverter is always entered, and it is the result that turns over. That is the difference between this and a negated condition, and it is why CompositeDecorator with Not exists as well.

Methods (2)

public override bool Evaluate(in BehaviorContext context, ReadOnlySpan<byte> state)
Whether the node may be entered, or may keep running.
public override ActionStatus Finish(in BehaviorContext context, Span<byte> state, ActionStatus result)
The node has finished, and this is the last chance to change what that meant.

Used by (2)

BehaviorTreeDecoratorTestsVixen.Ai.Tests
BuildStateVixen.Ai