Do comparison tasks in LimboAI handle floating point inaccuracies?

[FelixSeKett]

while exploring LimboAI, I was wondering how the built-in tasks that compare values (such as conditions checking floats or Vector2s) deal with floating point inaccuracies.

From what I can tell, comparisons are done using direct operators (e.g. ==, <, >), without any epsilon tolerance for floats or vectors. This could lead to unexpected results when working with movement vectors, distances, or other continuous values that are inherently imprecise.

So my questions are:

• Do any of the existing comparison tasks in LimboAI account for floating point precision issues?
• If not, is the recommended approach to write custom tasks (e.g. FloatAlmostEqualCondition) with a configurable epsilon?
• Or is there already a utility/helper in LimboAI that I might have overlooked?

Thanks in advance for clarifying!