Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Function state of running BTNodes resumes on destroyed instances. #1

Open
kagenash1 opened this issue Mar 8, 2021 · 3 comments
Open

Function state of running BTNodes resumes on destroyed instances. #1

kagenash1 opened this issue Mar 8, 2021 · 3 comments
Labels
bug Something isn't working
Projects
2.0
Milestone
2.0

Comments

@kagenash1
Copy link
Owner

kagenash1 commented Mar 8, 2021 •
edited

A lot of BTNodes and BBServices suspend execution through yield() calls. This is good as it avoids running things at each frame and allows more control over the flow of the script. However, if we destroy an object, a lot of errors will be thrown because those function states are resumed after a script/class instance has been destroyed (as in the example below).

Screenshot 2021-03-09 005449
@kagenash1 kagenash1 added enhancement New feature or request good first issue Good for newcomers labels Mar 8, 2021
@kagenash1 kagenash1 added this to the v1.0.4 milestone Mar 8, 2021
@kagenash1 kagenash1 assigned kagenash1 and unassigned kagenash1 Mar 8, 2021
@kagenash1 kagenash1 removed this from the v1.0.5 milestone Mar 12, 2021
@MadFlyFish
Copy link

Will these errors cause crash?

@kagenash1
Copy link
Owner Author

Godot is able to handle this error so it won't crash. This will probably be fixed in the 1.2.0 update!

@kagenash1 kagenash1 added this to the 1.2.0 milestone Mar 19, 2021
@kagenash1 kagenash1 added this to To do in 2.0 Mar 19, 2021
@kagenash1 kagenash1 added bug Something isn't working and removed enhancement New feature or request labels Mar 19, 2021
@kagenash1 kagenash1 removed the good first issue Good for newcomers label Apr 30, 2021
@ATHellboy
Copy link

Is there any workaround for fixing or disabling this error ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
2.0
To do
Milestone
2.0
Development

No branches or pull requests
3 participants
@ATHellboy @MadFlyFish @kagenash1