I just want to add that after a whole day wasted of trying to solve this problem without using the extremely complicated ‘add ons’ suggested here, I’m also giving up on defold. It is completely insane that a 2D-first engine has no built-in solution for getting world x and y coordinates in the on_input lifecycle, it only provides screen x,y and some useless “x,y” which will break as soon as the window is resized in any way. It also appears zoom messes with it, making this even more of a nightmare for pixel art games. Just mind boggling how the simple stuff is not addressed at all.
Perhaps all of this could be solved in a simpler way using a GUI overlay of buttons, it seems overly complicated and of course there is no hint of this in the manual, or this years old post. Everything in defold seems to be done from the perspective of making things unnecessarily vague. Too much freedom means your software is not user friendly. Make a clear path of the best way to handle common problems, and leave a ‘free way’ to do things for those that really want to. Don’t leave people in the dark, it’s just a sign of you don’t actually have solutions to common problems.
The process for installing those third party plugins is about the most hacky non-step by step process I’ve ever seen. You pretty much have to open the examples in the defold editor and scrutinize the code to figure out how they did things. For example there is a require statement in the orthographic add-on script which is nowhere to be found on the github how-to. There’s also hidden ‘problems’ like adding library dependencies doesn’t seem to always work until you re-launch defold. WTF.