I agree. I was thinking of using numerical attributes internally for smaller storage and efficiency, combined with a global string to attribute map. So map designers could use any name, and the name would transparently be translated into an ID for the purpose of storing attributes inside Map_Objects.
#7: The tree is implicitly linked to the worker right now, which should be more or less the same thing :)
I agree. I was thinking of using numerical attributes internally for smaller storage and efficiency, combined with a global string to attribute map. So map designers could use any name, and the name would transparently be translated into an ID for the purpose of storing attributes inside Map_Objects.
#7: The tree is implicitly linked to the worker right now, which should be more or less the same thing :)