Jakub Dóka

I see so you have 2 quadtrees for each team, one for static things and one for dynamic. > Entities does not change quadrant very often and update does mostly...

@Anuken I conducted a benchmarks and here are results: ```nim # current implementation CPU Time [old] 7.625s # current implementation but optimized by me CPU Time [optimized] 6.240s # updating...

The quadtree can still be improved. Currently we are relying on arc and storing references to quadtree all over the place. My plan is to change the tree structure. Replace...

[here](https://github.com/jakubDoka/mlok/blob/main/logic/spatial/quadtree.go) is one. Its optimized to play with gc, there isn't any other reason. Current implementation also creates reference cycles, that can be avoided.

Numbers for new macro |behaviours|iters|protocols per behaviour|-|per iter|-| |-|-----|--|---------|---------|---------| |1|10000|10|5.0441 ns|5.0892 ns|5.1472 ns| |1|10000|100|7.8285 ns|8.0366 ns|8.3113 ns| |1|10000|1000|19.439 ms|19.568 ms|19.731 ms| |5|10000|2|6.1172 ns|6.2539 ns|6.4356 ns| |5|10000|20|14.192 ns|14.835 ns|15.676 ns| |5|10000|200|270.12...

Feature flag sounds very reasonable (since I want to use this in my project), In that case, I can introduce a required field in the behavior that can store the...

@dhuseby sorry, I missed the last one, I'll hopefully show up on the 16th

Well that was an accident