There is some problems with the CUT feature. It seems to ignore some nodes, and even on nodes that were cut, the paste remove connections.

I would like to discuss the redefinition of shortcuts and general usability of the editor. I think the shortcuts could be better distributed, so I'm listing all commands and their respective shortcuts. Proposed new shortcuts will override old shortcuts.

This is not a priority, but it must be discussed for the next editor UI refactor, so I would like to hear the community opinion.

I add an additional base attribute with a default value on Node.js - I can see that the value here is applied to all the node. However, when I update value inside the code of each node, the value doesn't update (for example, in And.js, I change the value of this new attribute, but when I show the value on properties panel or when I export JSON, I see the default value from Node.js)

What am I missing here?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I build the editor and put it to web container like apache, nginx, but it looks like has error when access the web page from another computer,

The home page show below:

Behavior3 Editor
Starting application... Have Fun!

It would help a lot if one could import a custom nodes file (instead of re-adding it all the time). Sure you may add your custom nodes on a clean project and use this as a template for all your b3 files, but what if we need to add more custom nodes - you have to add them to all of your existing files. With a "Import custom nodes" option this would handle it. Another more elegant option would be a separate custom nodes file.

The zoom short cut seems to be reversed in chrome and firefox. ctrl + scroll up and ctrl + scroll down work fine in chrome but have the opposite effect in firefox.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Firefox is not rendering the node preview on the first time you drag a node from the left panel to canvas.

When exporting the tree or project as json, whilst the custom nodes is output as an array (which makes sense) all the contents of 'nodes' is flattened into attributes under respective ids.

Whether or not the json format were updated to reflect the tree structure (i.e. children within parents), it would be helpful to have the nodes reflected again as an array. At the moment it seems like it needlessly makes it more difficult for the export to be parsed?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I just had to install bower myself while in the process of installing locally.

I think thats confusing to non-dev end users, since if they run npm install + bower install they are gonna get an error on the latter.

Why not adding bower in package.json?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Top/Left to Bottom/Right. Similar to UE design. Not the features but the layout as an alternative to to the horizontal one.

Behaviour3.com is hijacked

Instead of forking the repo at https://github.com/renatopp/behavior3editor this repo just dumped code. That's a problem, because history was lost. Oh well. No use crying over split milk. However, this move leaves behind 3 or 4 unmerged forks:

https://github.com/Healthire/behavior3editor
https://github.com/knowrob/behavior3editor
https://github.com/benjycook/behavior3editor

all of which look like they've received significant development work, but are now orphaned. These need to be reviewed and either merged or cherry-picked as appropriate.

链接: https://pan.baidu.com/s/1Psx2Lp2PovEOPVDtNcAtkg?pwd=atew 提取码: atew

I downloaded the editor source and tried to get it to work with node-webkit but I get an error in index.html on the app.initialize() saying "Cannot read property 'initialize' of undefined.

At the top you have:

var loader, app;

But I can't see where app is created anywhere. The loader variables is of type createjs.LoadQueue() but 'app' doesn't get assigned anywhere.

Any help on getting this to work on nw.js would be huge! I'm trying to use this for the Leadwerks game engine for AI and I think having a desktop version of this editor would be nice and nw.js can help get that.

fs.js:39
} = primordials;
    ^

ReferenceError: primordials is not defined
    at fs.js:39:5
    at req_ (/home/ruben/dev/tools/behavior3editor/node_modules/natives/index.js:143:24)
    at Object.req [as require] (/home/ruben/dev/tools/behavior3editor/node_modules/natives/index.js:55:10)
    at Object.<anonymous> (/home/ruben/dev/tools/behavior3editor/node_modules/graceful-fs/fs.js:1:37)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

The current interface of the editor (not the dashboard, only the editor) is really annoying for any non-trivial project. So I would like to discuss what to do with it. Notice that I'm neither a designer or an UI/UX expert, thus, I would like to hear from people with more expertise on this.

I have some suggestions (they can -and should- be divided into other issues before implementing them):

• The left panel could show a simpler list organized in hierarchies, similar to any code editor (e.g., sublime text), where we could click on some category (e.g., nodes, or trees, or composite) and show/hide its content.
• The left panel MUST have a search field in order to filter the nodes and trees.
• The right panel could be completely removed. User could double click onto a node (or Edit > Node properties) to open a modal screen. This would remove the live update of the node and simplify A LOT the undo/redo logic.
• The right panel could be a small panel with fast shortcuts (pretty much like any vector or image editor like inkscape and photoshop). This would be a toolbar on the right side.
• Creating a connection to an empty space or right clicking on the canvas could open a simple popup to select a node (would be an alternative to dragging the nodes from the left panel). This popup would have a search field. This feature is based on the Unreal Blueprint editor.

I was thinking of forking this and migrating it to use React instead.
The idea was to make this "portable" to the point where you could pop up a browser in any environment, feed it a behaviour tree and connect it to the gameplay for debugging purposes.

But before I start, I was hoping to get your take on it!

After just a little bit of editing, accessing the various parts of the tree is difficult because portions are off the sceen.

see title.

well... All I want to do ,is make this web can be visit in my local. I guess it needs some like "MEAN" and "Angular", but I really don't know how them work.

It appears as though you can't remove properties from nodes once you've added them. After clicking the red "-" button, although the property disappears, if you deselect the node in question and reselect it, the property is still there.

The only way I've found to permanently remove the property is to manually edit the project file, which is a bit of a pain. The problem appears to be within the BlockManager, specifically the update function. I'd try and trace it further but I'm not that familiar with Angular so I can't currently pinpoint the source of the problem.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

so I can design small portions and then combine when running

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Wish to add parallel node into composite libs!

So, there is a real need for dynamic properties on node instances? (i.e., user should be able to add or remove properties of any given node instance?). Seems irrelevant to me, if you want to add a property, just add onto the node definition. The same is valid for removing a property.

This would simplify a lot the properties panel.

Notice that, this is related to issue #6, so it is a high priority.

First of all, congrats for this project. Looks very promising.

I am writing a BT library in Java and I would like to use behavior3editor as the graphical editor for the trees. However, I have not found any reference to a formal specification of the tree format. Is there any?

Thank you very much

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I wonder where this name came from.
There might be behavior1 and Behavior2？

This is actually related to all behavior3 projects.

My idea is to create a new repository (maybe behavior3/behavior3docs) with all documentation in markdown, so we could access it from the documentation (from web and desktop versions), keeping always updated, even when changing releases (specially for desktop).

This repository would have:

• Tutorials about behavior tree in general;
• Usability and interface guide for the editor;
• Reference about the JSON formats used in the B3;
• Reference about how to implement a client library in another language;
• Api and user guide for the client libraries, in special for the b3js;
• Application examples of behavior trees using the client libraries;

When open index.html, always show "Behavior3 Editor Loading..."

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

If you have a lot of custom nodes, the editor view gets messy with a plain list of custom nodes.
How about adding a "Parent" property to the (ui)-basenode, which would make it possible to have a (custom) nodes tree in the left pane of the editor:

Nodes

Actions
|-Default
| |-Failer
| |-Succeeder
|-Custom
| |-Player
| | |- Combat
| | | |- UseSword
| | | |- UseKnife
.....
with the option of folding/unfolding those trees..

There is a $10 open bounty on this issue. Add to the bounty at Bountysource.

Steps to reproduce:

1. Select a node.
2. Edit its title.
3. Select another node.
4. Click at the title field.
5. Press ctrl+z.

The same happens with other fields, but the title is more critical.

In some future release, I want to change the overall visual of the blocks and canvas. This issue is only for discussion until then, when I will break it into several small issues.

Using the figure above as reference:

• Block shapes: all blocks are homogeneous, categories are differentiated by color and an icon on the top-right side. This modification is useful for the addition of more complete block information and make things more readable;
• Block information: a block contains its title (with emphasis), its name (which is very important to show, and the current editor does not do), its description as tool tip; and all its properties; Blocks without properties (e.g., the root block) do not show the properties body;
• Selection Highlight: currently, the selection highlight is made by creating a shadow around the block, which is pretty heavy (try to select and move a hundred blocks). In the new visual, the highlight is a simple box behind the block;
• Grouping Notes: based on the unreal engine blueprint, would be cool to have some "group" feature. In this case, you can select the nodes you want and create a group, which will resize automatically with new rearranges;

If I have a project where a tree references another tree that is below it in the list on the left of the editor, I save the project, and then attempt to reopen it, the editor fails with an error message.

After taking a bit of a look at the source, this appears to be because the trees in the serialised JSON are stored in an array, and if a tree refers to a nested tree which exists after it in said array, it won't have added it within the NodeManager, and hence will fail.

I would either suggest changing the JSON format so that the trees are stored as key-value pairs (much like the nodes), or having an additional processing phase before attempting to load the tree, so that the node manager is aware of all the nodes that exist within the project file. The latter approach wouldn't invalidate existing projects files, and is probably the preferred one from my point of view.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I could not test in other computers or distributions, but when we drag a node from the left panel to the canvas, the node preview have a white background. This is happening on chrome/ubuntu 14.04.

What is your development environment(IDE) when you develop this editor? I need a deep modification of the editor to support behavior tree runtime visualization.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Consult: renatopp/behavior3editor#12

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

This thread discuss how to handle multiple trees in the editor and the client libraries.

Motivation

You can use multiple trees in some different ways:

• You may use one or more independent trees (they don't have tree nodes).
• You may want to create a main tree which calls other trees as util functions. For example, a SoldierTree that uses CombatUtilTree, HealingUtilTree and CoverUtilTree.
• You also may want to create several "main" tress that calls other trees as util functions. For example, CommanderTree and SoldierTree using the same utility subtrees.
• In a worse scenario, you may want to use two trees recursively. For example, tree A calls B and tree B calls A (I don't know any case where this would be useful, but I don't see why and how to avoid it).
• Worse yet, you may use the same tree recursively, e.g., tree A calls tree A.

Given that you may use the same subtree several times and the case where you use the trees recursively, I want to create a single object instance for each tree.

So, I'm thinking in something like that:

var behaviorCollection = b3.load(behavior3_data);

var soldierTree = behaviorCollection['SoldierTree'];
var commanderTree = behaviorCollection['CommanderTree'];

and then you use the trees as usual.

Editor

If we follow this behavior collection thing we:

• can't allow trees with the same name.
• could change the JSON format to make easier to read these trees (maybe similar to how nodes work). This also would help with #5.

Client

In the client libraries we can create an empty BehaviorTree for each tree in the JSON, and then create their nodes (we can't create nodes together with the trees because nodes can have reference some tree).

Moreover, we need to update how BehaviorTree.tick method works, maybe breaking it in several internal methods. To understand that, consider the following situation:

• a SoldierTree have two differences references to CombatTree (let's say C1 and C2);
• in the client we only have two objects, one for SoldierTree and other for the CombatTree (for both C1 and C2);
• if the SoldierTree calls C1 and then C2, everything will explode right away because both C1 and C2 are the same object, thus sharing the same IDs, nodes and node IDs (i.e., blackboards uses trees and nodes IDS to store information).

The same would occur if the CombatTree were referred by SoldierTree and CommanderTree.

So, before calling the subtree, we need to change temporarily its ID.

I'm not sure if this issue is barely understandable by anyone but me. I've been thinking a lot about this feature lately, so the description may lack some more contextualization.

I want to finally (officially) release a new version of Behavior3. Which I think it could be the 1.0.0, since it has been through a lot of changes since 0.1.0. To accomplish this, there are some important bugs that must be fixed and some features that weren't finished yet.

So this is my TODO list to the next release:

• #10 Undo/Redo is having problems with properties
• #9 Cut with problems
• #8 How to handle Multiple Trees (also related to #5)
• #7 Unable to remove properties from nodes (also related to #12)
• #14 Building for desktops

Of course, we need to update the site and the client libraries, but the editor is the most important right now.

There are some issues with the desktop buildings:

• Saving/Loading files must be better tested;
• Must work at least in windows and linux (I couldn't test it yet);
• We must have a better distribution process in gulp.
• We could test electron instead of node webkit.

Hello, is this project no longer maintained? It hasn't been updated in years, and the website is gone. I want to see your blueprint.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

if it’s a browser, I can clear the cache, but I don’t know how to deal with the client, even if I clear the data in AppData.
And it can work on other computers.