Dennis Waldherr

If "normal" units are affected, they sometimes get a "onUnitHide" at regular intervals. If buildings are affected, nothing seems to "betray" them.

One could use i128, but I see the problem. Removing integers: You mean for `distance_2` or generally? Btw. maybe my issue is invalid? After all, I could have used i64...

The problem with using even f64 for internal calculations is, that there's a loss of precision: `println!("{}", 499999999000000001_u64 as f64);` yields `499999999000000000` I can imagine that for some use cases...

"error reading benchmark list" - this might be caused by a running gradle daemon still having the JAR opened. When rebuilding the jar it sometimes won't be reopened and causes...

Could be caused by aliasing? All artifacts seem appear on the same corner tile.

Yeah, I'm using egui-macroquad so I had to do a bit more, but egui-miniquad seems to work fine for me (although I really only use a small subset of egui)....

I think we should either leave it private, or make `onUnitDestroyed` *not* handle buildings. I'd vote for keeping it as is.