npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

behave-graph

v0.9.10

Published

Simple, extensible behavior graph engine

Downloads

35

Readme

Behave-Graph

GitHub license npm version

Behave-Graph is a standalone library that implements the concept of "behavior graphs" as a portable TypeScript library with no required external run-time dependencies. Behavior graphs are expressive, deterministic, and extensible state machines that can encode arbitrarily complex behavior.

Behavior graphs are used extensively in game development as a visual scripting language. For example, look at Unreal Engine Blueprints or Unity's Visual Scripting or NVIDIA Omniverse's OmniGraph behavior graphs.

This library is intended to follow industry best practices in terms of behavior graphs. It is also designed to be compatible with these existing implementations in terms of capabilities. Although, like all node-based systems, behavior graphs are always limited by their node implementations.

Another neat fact about behavior graphs is that they offer a sand boxed execution model. Because one can only execute what is defined by nodes exposed by the host system, you can restrict what can be executed by these graphs. This type of sand-boxing is not possible when you just load and execute arbitrary scripts.

Documentation

Community Resources

You can join our Discord here:

https://discord.gg/mrags8WyuH

@beeglebug has started an amazing interactive React node graph editor for behave-graph here:

https://github.com/beeglebug/behave-flow

image

Feature Overview

This library, while small, contains a nearly complete implementation of behavior graphs.

Features:

  • Customizable While this library contains a lot of nodes, you do not have to expose all of them. For example, just because this supports for-loops and state, does not mean you have to register that node type as being available.
  • Type Safe This library is implemented in TypeScript and fully makes use of its type safety features.
  • Small This is a very small library with no external dependencies.
  • Simple This library is implemented in a forward fashion without unnecessary complexity.
  • High Performance Currently in performance testing, the library achieves over 2M node executions per second.

Node Types:

  • Events You can implement arbitrary events that start execution: Start, Tick
  • Actions You can implement actions that trigger animations, scene scene variations, or update internal state: Log
  • Logic You can do arithmetic, trigonometry as well as vector operations and string manipulation: Add, Subtract, Multiply, Divide, Pow, Exp, Log, Log2, Log10, Min, Max, Round, Ceil, Floor, Sign, Abs, Trunc, Sqrt, Negate, And, Or, Not, ==, >, >=, <, <=, isNan, isInfinity, concat, includes.
  • Queries You can query the state from the system.
  • Flow Control Control execution flow using familiar structures: Branches, delays, if-then, sequences and for-loops.
  • State You can set and load state arbitrarily: Set, Get.
  • Time Time nodes allow you to wait: Delay.

Designed for Integration into Other Systems

This library is designed to be extended with context dependent nodes, specifically Actions, Events and Queries that match the capabilities and requirements of your system. For example, if you integrate into a 3D engine, you can query for player state or 3D positions of your scene graph, set scene graph properties and also react to overlaps, and player movements. Or if you want to integrate into an AR system, you can react to face-detected, tracking-loss.

Command Line Usage

Building

After cloning out this git project locally, run the following:

npm install
npm run build

Examples

The example behavior graphs are in the /examples folder. You can execute these from the command line to test out how this library works.

The main syntax is this one:

npm run exec-graph -- ./src/graphs/[examplename].json

Here are some example graphs in their native JSON form:

Hello World

Print out the text "Hello World!" as soon as the graph starts up!

/src/graphs/core/HelloWorld.json

Console output:

> npm run exec-graph -- ./src/graphs/core/HelloWorld.json

Hello World!

Setting, Reading, And Listening to Variables

In this example, we use set a variable and also listen to when it changes.

/src/graphs/variables/Changed.json

Console output:

> npm run exec-graph -- ./src/graphs/core/variables/Changed.json

391

Branching

This example shows how to branching execution works. The "flow/branch" node has two flow outputs, "true" and "false". The value of it's "condition" input determines the path of execution.

/src/graphs/core/flow/Branch.json

Console output:

> npm run exec-graph -- ./src/graphs/core/flow/Branch.json

Condition is false!

Polynomial Math Formula

This shows how to create math formulas in logic nodes. In this case the equation is: ( a^1 * 3 + a^2 + (-a^3) ), where a = 3. The answer is -9.

/src/graphs/core/logic/Polynomial.json

Console output:

> npm run exec-graph -- ./src/graphs/core/logic/Polynomial.json

-9

Asynchronous Execution

Behave-Graph support asynchronous nodes. These are nodes which will continue execution non-immediately but on their own self-determined schedule. This allows for things such as "Delay" nodes that can sleep for a period of time.

/src/graphs/core/async/Delay.json

Console output:

> npm run exec-graph -- ./src/graphs/core/async/Delay.json

Waiting...
One Second Later!

For Loops

Building upon waiting for downstream nodes to execute, you can also execute For Loops within Behave-Graph.

/src/graphs/core/flow/ForLoop.json

Console output:

> npm run exec-graph -- ./src/graphs/core/flow/ForLoop.json

Starting For Loop...
Loop Body!
Loop Body!
Loop Body!
Loop Body!
Loop Body!
Loop Body!
Loop Body!
Loop Body!
Loop Body!
Loop Body!
Completed For Loop!

Custom Events

You can register custom events, trigger then and listen on them.

/src/graphs/core/events/CustomEvents.json

Console output:

> npm run exec-graph -- ./src/graphs/core/events/CustomEvents.json

myCustomEvent Fired!
myCustomEvent Fired!
myCustomEvent Fired!
myCustomEvent Fired!
myCustomEvent Fired!

Performance Testing

Here is a test of 10,000,000 iteration for loop:

/src/graphs/core/flow/PerformanceTest.json

Here is the console output:

> npm run exec-graph -- ./src/graphs/core/flow/PerformanceTest.json

Starting 10,000,000 iteration for-loop...
1,000,000 more iterations...
1,000,000 more iterations...
1,000,000 more iterations...
1,000,000 more iterations...
1,000,000 more iterations...
1,000,000 more iterations...
1,000,000 more iterations...
1,000,000 more iterations...
1,000,000 more iterations...
1,000,000 more iterations...
Completed all iterations!

    30000013 nodes executed in 2.98 seconds, at a rate of 10067118 steps/second