Exception thrown by children.ChildContainers in VisualTask when calling AddDivider

[bianjingshiyi]

Describe the bug
As my title described.

To Reproduce
Steps to reproduce the behavior:

1. Create a C# MonoBehavior script.
2. Add a BehaviorTree field.
3. Build tree in Awake as the following script:
   new BehaviorTreeBuilder(gameObject).Sequence()
   .WaitTime(1)
   .ReturnSuccess()
   .End().Build()
4. Click ViewTree button in inspector, see error.

Expected behavior
Throw IndexOutOfRangeException, can be seen in console log.

Desktop (please complete the following information):

• OS: [Windows]
• Exact Unity Version [2022 LTS]

[ashblue]

Hmmm, so I think the issue here is ReturnSuccess is a decorator. The decorator isn't wrapping anything so this seems like an expected error. Take a look at the below link and let me know if adjusting to this format makes the error go away.

https://github.com/ashblue/fluid-behavior-tree?tab=readme-ov-file#returnsuccess

[bianjingshiyi]

No, this is not about behavior tree it self or its printer, it is just drawer can't get behavior tree reference in a array or nested struct, and I advanced the drawer in my PR so it can get reference in array now.

[ashblue]

Oh okay, so the error is that the divider is collapsing visually then? Do you have a screenshot of this if it's a visual issue lying around (if not no big deal)?

Also in the PR it looks like a large number of lines were reformatted so I'm not really sure what specific lines were adjusted to fix the reported bug.

---

No, this is not about behavior tree it self or its printer, it is just drawer can't get behavior tree reference in a array or nested struct, and I advanced the drawer in my PR so it can get reference in array now.

Okay so that sounds a bit different from the original issue you reported. The issue I'm having here is figuring out how to reproduce the reported bug as that block of code will error out or have issues, as a decorator requires child elements to not crash. All changes in the project need to be backed by tests to keep the code base stable (it's used by a large number of active projects) so I'd have to know exactly how to reproduce the issue step by step in order to add a bug fix.