> I'm really curious to hear where the pain points are Honestly, the biggest for me so far has been stability. Enu crashes from time to time. I've noticed this much likely to happen when I use prototypes.
* In general, working with prototypes is something I'm not digging yet. I like the idea but I'm having hard time working with them. For example, I tried using prototypes for the terrain generation first. I had a layer unit, hill unit, and terrain unit. When I built a number of hills and wanted to modify the algorithm, I noticed that I must find the original prototype to edit its code; clicking on any generated unit opens a blank editor. * Another problem with units is, I don't know what to do with the original prototypes. Should I just drop them somewhere out of sight? * Also noticed that sometimes my units would stop seeing each other. Like I got "undeclared identifier" errors out of nowhere. * I eventually switched to functions, which revealed a slight inconvenience: commands defined in one file aren't visible in the other. That means, all my commands now have to sit in the same file. * Another thing that I think is missing is explicit distinction between creator mode and play mode. After I've created the map, I want to give my some the gamepad and let him play. But I don't want him to start building walls and deleting monsters.
