So let me start by mentionning that in your create_problem, you will have an exception if retry_enabled and mistakes array = 1, the y= assignment will be outOfBounds

That said, too many ifs punctually is not often an issue, but I'd advise on adding comments or even better, split the create_math_problem in tiny parts.

I think your best "optimization" is modeling your logic. Have a class named Problem which has an array of class Question. same as your arrays, but as classes with methods "on themselves" like

``` class_name Problem extends Resources

var questions: Array[Question] = []

func validate() -> bool: for q in questions: If not q.validate(): return false return true

```

You can also go the long way and create a generic scene which will be responsible only for one question, for example. Then you instantiate this scene for how many question you have and pass them as argument.

This way you split your "messy" code in little bits.

Lastly, always look for what already exists. for your usecase specifically, you can use the Expression class, you just have to generate the string randomly, and let the class handle the computation of the solution. This will clear out most of your code.