https://github.com/queenofsquiggles/bevy_htnp

Hierarchical Task Network Planning deeply integrated with bevy, which I use in my games :P
https://github.com/queenofsquiggles/bevy_htnp

Last synced: 2 months ago
JSON representation

Hierarchical Task Network Planning deeply integrated with bevy, which I use in my games :P

• Host: GitHub
• URL: https://github.com/queenofsquiggles/bevy_htnp
• Owner: QueenOfSquiggles
• License: apache-2.0
• Created: 2024-08-09T19:26:33.000Z (6 months ago)
• Default Branch: main
• Last Pushed: 2024-08-20T15:43:49.000Z (5 months ago)
• Last Synced: 2024-08-20T17:59:15.719Z (5 months ago)
• Language: Rust
• Size: 35.2 KB
• Stars: 18
• Watchers: 3
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE-APACHE.md

Awesome Lists containing this project

README

        
[![CI](https://github.com/QueenOfSquiggles/bevy_htnp/actions/workflows/rust.yml/badge.svg)](https://github.com/QueenOfSquiggles/bevy_htnp/actions/workflows/rust.yml)

> Note that CI currently tests against a matrix of (windows, mac, linux) \* (toolchain stable, nightly) \* (cargo build, test, clippy), which ensures validity on every possible desktop target. If you know of a clever way to add WASM testing as well I would greatly appreciate it!!!!

# Bevy HTNP

> Hierarchical Task Network Planning deeply integrated with bevy

## Main Conceit

Hierarchical Task Networks are characterized by having a concrete set of specific primitive tasks that can be compounded into a sequence that affects the world around them. Because of bevy using ECS, individual task primitives can be modelled with a simple, and standard, bevy system. This plugin handles the heavy lifting of organizing those task primitives, loading and unloading specific components associated with those primitives, and cleaning up if something goes wrong.

## Guaranteed Best Documentation

The best documentation will always be the examples and unit tests. The example `basic_htnp` should be an excellent way to show how to get started.

## Contibuting

(I definitely need better contribution guidlines someday...)

#### What I am doing to make this crate better

- Integrating into my own game(s)

- Fixing issues I come across wrt my games

- Adding features necessary to my games that are general enough to be applicable to other games

#### What you can do to make this crate better

- Report bugs (see issue templates)

- Create feature request write-ups (see issue templates)

- Submit PRs **for existing feature requests**

Overall, your contributions must not affect the licensing of this crate. 99% of the time this shouldn't be a problem. As long as you write your own code, your contributions should be fine.