| Search |
|---|
| ID | Rating | Category | Description | Screenshot | Date |
|---|---|---|---|---|---|
| 1703 | 😟 | Suggestion | While it's a solid start, I've got a number of suggestions re: behaviour programming The way many nodes operate is counter-intuitive: I would expect the move(range) node to take two inputs: the target and a number for range. Instead, it only has one input and you need to use some other nodes to enable it to do it's job. If I hadn't found a tutorial showing an example, I'd never have guessed how it functions. There are nodes with titles that aren't going to be mean much to a player who hasn't already had it explained to them, nodes with unlabeled outputs or unclear inputs, etc. I don't need a full tutorial on each, just enough info so that I can look at it and say "yes, i know how to make this do the thing it's supposed to do". Beyond that, confirmation dialogue to save changes, undo, the ability to save sub-sets of a behaviour as routines to make it easier to re-use code without having to reinvent any wheels. | 2023-08-28 06:39:50 |
| ID | Reply | Author | Date |
|---|