Allow the creation of recursive HTNs

[osjarw]

About the PR

Added a limit to the maximum amount of tasks a plan can consider.
Gave the developers a way to exclude their compound tasks from being checked for recursive tasks by the integration test.

Why / Balance

Recursive tasks make the creation of longer plans a lot easier, and solving multiple problems in a single plan becomes more viable.
However, allowing the creation of recursive tasks may lead to cases where the tasks misbehave and continue extending a plan indefinitely. I solved this problem by setting a limit to how many tasks can be considered, and upon exceeding the amount, the NPC will be disabled, alongside throwing an exception to make the developers aware of the existence of a misbehaving NPC.

Technical details

Added AllowRecursion to HTNCompoundPrototype, setting this to true makes the integration test ignore this task being recursive. This being opt-in ensures that unintentionally recursive tasks aren't merged.

Made HTNPlanJob.Process keep track of how many tasks have been considered, and throw an exception upon exceeding the limit set in HTNPlanComponent. If for some reason 1000 tasks isn't enough, it can be overridden on a per-entity basis.

I guess I could've done this a lot better if I had better understanding of how the yml serialization works.

Media

• I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog