> I don't understand the motivation behind this request. I can't think of a single game engine that renders svg in their runtime (the only exception is real-time text rendering, but that's not technically svg, just a similar process).
You're forgetting a pretty huge one, although pretty dead now. Flash... There was a LOOOOT of games made with flash back in the day. Pretty much every game online was made with flash.
Vectors was one of the few things I actually liked about it. Action script was pretty flexible as well, but now we're talking about vector itself.
Vector paths support in general in any engine is still very useful. For many reasons.... apart from graphics.
Here are some reasons
* A simple path can be used for an enemy or Npc to travel along. Or just in general for animating movement, from A to B. (I don't know how they going to solve making a competent animation timeline feature, without any kind of paths to control movement.)
* Paths and shapes can be used to define areas, a much better solution than placing a lot of useless dummy sprites with individual collision boxes all over your map just to block movement of where you can and can't go. Just draw or define an area with vector shapes directly on the layout, and use add it to the list of collisions boxes to interact with. Kill the old collission boxes and assign a simple shape instead.... and you can have perfectly round collision on balls for example.
* Simple Shapes and paths can be used for deformation purposes as well, much how like Spriter and Spine works, but that's another topic.
* Apart from these, there's the obvious advantage of using svg's for general graphics. Especially, UI, Icons, buttons, etc etc.
Pretty much every game engine I know has some implementation of paths, and shapes in some form, for things mentioned above.
My suggestion is to start from the ground up, starting to support basic shapes and paths for purposes other than graphics, later they can support loading more complex vectors.
Many developers forget to fix this.