Austin East

I'd like to suggest just deprecating `FlxPoint`, not sure why we even need both! All of `FlxPoint`'s functionality could be moved into `FlxVector` and `FlxPoint` could become: ``` @:deprecated("FlxPoint is...

Yeah, in a mathematical sense they are different, but practically they just represent the same data (X and Y) with a different set of functions available. In the end Flixel...

I think you may be looking for this? https://austineast.dev/echo/api/echo/Echo.html#check It can be used like so: ```haxe world.check(body_a, body_b, my_collision_options); ```

Definitely reasonable request, I'll be looking into it!

If you just want to stick to image previews, one option would be to display the image in some kind of tooltip when hovering over links with metadata. That way...

Interesting! Hadn't thought about using the macros to add primitive data types 😄 It was intended for Classes, but I think its worth supporting.

~~@MSGhero is correct, you need to specify at least 1 component when defining your nodes~~ ~~So instead of this: `@:nodes var nodes:Node;`~~ ~~You need to do something like this: `@:nodes...

Are you sure your "Entity" class (from `node.entity.components.get(Position).body.x;`) has it's `components` field assigned correctly? For example: ```haxe class Entity { public var components:Components; public function new() { // Make sure...

Whoops, completely forgot to reply to this! But yes, I agree with you here. Hopefully I'll have some time to come up with a good solution soon 👍