Nice list! Thx!
Re 1.2: Strange, I thought we had fixed that. I just tested this too, and got the same result. We’ll create a ticket for that (if we don’t have it already)
Re 1.6: Have you tried setting the “extrude borders” in the .tilesource file? This feature makes the tiles extra large, which allows for non aligned coordinates (such as when moving the camera around smoothly). This will remove the need for extra .render_script fixes. I’m not sure how other engines do this, but this is a feature where different games will have different needs with respect to texture size, thus we won’t try to automatically guess one good value for everyone.
Re 1.7: This is a known issue that haven’t been fixed yet. It’s good to hear that it’s needed, it will make it easier to prioritize. @sven or @jakob.pogulis, could you see if we have a jira ticket for this? (ask Ragnar)
Re 1.8: We have had such discussions recently in the team, and it’s something we want as well. In the meantime, the best option is to use a tool such as Tiled, and load/parse data yourself. @pkeod has an example here..
Another option is to put special tiles in your tilemap (in a non visible layer), and parse them out during init, and convert them to whatever data they represent (e.g. waypoints). It’s crude, but it works.
I just answered on those (high prio) items I know something about, and as I don’t have access to our ticket system, I currently can’t create new ticket for the issues listed here. I’ll leave that for the team tomorrow 