├── .github └── ISSUE_TEMPLATE │ ├── bug_report.md │ └── feature_request.md └── README.md /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | 15 | Provide a list of steps to reproduce the issue. 16 | When applicable, please send the file that triggers the faulty behavior. 17 | 18 | **Expected behavior** 19 | A clear and concise description of what you expected to happen. 20 | 21 | **Screenshots and videos** 22 | If applicable, add screenshots to help explain your problem. 23 | Consider using a screen-recording application (for instance, https://www.screencapture.com/) 24 | 25 | **Desktop (please complete the following information):** 26 | - OS: [e.g. iOS] 27 | - Version [e.g. 22] 28 | 29 | **Additional context** 30 | Add any other context about the problem here. 31 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Describe alternatives you've considered** 17 | A clear and concise description of any alternative solutions or features you've considered. 18 | 19 | **Additional context** 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Groot2 2 | 3 | Hi! 4 | 5 | This repository contains updates about the release of [Groot2](https://www.behaviortree.dev/groot) 6 | and (in the future) tutorials and learning material. 7 | 8 | You can use submit issues here: https://github.com/BehaviorTree/Groot2/issues 9 | 10 | ## Changelog 11 | 12 | ### 1.2.0 (2023-09-11) 13 | - [Bugfix]: fixed crash when renaming a Subtree 14 | - [Bugfix]: Prevent Model editor when double clicking a Subtree. 15 | - [LogReplay]: add filter-in/filter-out to the Transitions table. 16 | - [LogReplay]: add the ability to export the result of the query into a JSON file 17 | 18 | ### 1.1.1 (2023-08-12) 19 | 20 | - [Bugfix]: fixed crash when inserting a node during the Creation of a Node connection 21 | - [Bugfix]: fixed crash when pressing the button "Play" on an empty Log Replay 22 | - [License]: when activating the PRO license, user is asket to agree with the EULA. 23 | 24 | ### 1.1.0 (2023-07-23) 25 | - [Visualization]: improved layout for Pre/Post Conditions boxes. 26 | - [Editor]: Adding the ability to save XML files using the same syntax used by Groot1 (disabled by default in Preferences). 27 | - [Editor]: Added `ParallelAll` and `ScriptCondition` to the built-in nodes. 28 | - [Editor]: allow files that only contain **include** tags, but not **BehaviorTree** to be loaded. 29 | - [Monitor]: Breakpoints can now be saved/loaded from file. 30 | - [Monitor]: Add compatibility with the Groo2Publisher in BT.CPP 3.8+. 31 | - [LogReplay/Monitor]: Log parsing will now use plugins. Users will be soon able to create their own plugins to save/load logs. 32 | - [LogReplay]: the range of the log can be changed; in other words, you can zoom on a particular section of the timeline. 33 | - [Licensing]: append license key to offline activation file. 34 | 35 | 36 | --------------------------------------------------------------------------------