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.

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

Too many Booleans in 1 event causing Error #5886

Open
1 task done
VegeTato opened this issue Nov 8, 2023 · 1 comment
Open
1 task done

Too many Booleans in 1 event causing Error #5886

VegeTato opened this issue Nov 8, 2023 · 1 comment

Comments

@VegeTato
Copy link
Contributor

VegeTato commented Nov 8, 2023

Is there an existing issue for this?

Describe the bug

When i add a lot of booleanse (around 100) in 1 event condition, the game works in gdevelop preview,
but when i publish it on GD.games or itch or any other platform, the game freeze and the entire events just break and nothing works, and i get the error Uncaught InternalError: too much recursion in the debugger log on browser.

Here is a complete empty project that only have 1 event with many boolenas, this scene events will not work at all until you disable that 1 event with multi booleans in it:
Test.zip

Update:
Problem Fixed ! 🥳
or i should say i just found a workaround,
so after subtracting booleans (157 by 157)
the error is gone at the number (314).
So i then divided the booleanse into separate events, each event now contains only 157 boolean variable x 5 = 785 variables in total but separated to 5 events with trigger once.

in conclusion:
events in GDevelop can't take more than 314 conditions in 1 event.

Steps to reproduce

1- Publish the scene to GD.games
2- Notice how the scene will not run any event at all in there.
3- Check the debugger in the browser.
4- You get the error Uncaught InternalError: too much recursion

GDevelop platform

Desktop

GDevelop version

Latest version

Platform info

No response

Additional context

No response

@4ian
Copy link
Owner

4ian commented Nov 9, 2023

That's an interesting error. Error being set aside though, should you rather use a repeat event to do a loop on an array/structure of booleans instead of manually doing anything that involves more than 3 variables? This will make things easier to manage and extend I guess :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants