DrawRect2D and DrawRect3D

[NicEastvillage]

In v4 we can draw rectangles in 2d and 3d. These have not been implemented in v5 yet - probably due to their hacky implementation. Internally the rectangles are made drawing strings with transparent text and colored background. Those with closed-source access can search up Rendering::makeFakeRectangleString().

For v5, we need to decide whether to add two new RenderMessages for Rect2D and Rect3D, or reuse the String2D and String3D types and move the makeFakeRectangleString() to the interfaces. The advantage of creating new rendering message types is that we get parity between the interfaces and no code duplication. So I suggest the former.

[VirxEC]

I dropped them because I didn't know of anyone that used it, and it wasn't a part of the Psyonix API. That being said, it's not like it would be hard to implement.

[NicEastvillage]

This one is mine. I will implement it!

[VirxEC]

Just one thing, I saw in https://github.com/RLBot/flatbuffers-schema/commits/rectangles/ that String2D's x & y was converted into an integer instead of a float. Was this a mistake?

[NicEastvillage]

That is intentional since the 2d functions use pixel coordinates which is obvious when the type is integer. Do you think otherwise?

[VirxEC]

They do not use pixel coords, that was a limitation of the v4 api

[NicEastvillage]

I don't think that was a limitation, but a feature. It is possible to convert back and forth, so we really just need to pick what people prefer to work with in user space.