Ok, I'm starting to see some logical action of Hs going from dark blue to the light blue squares I put down. I was hoping the Hs would choose closer crystal piles when I set them down but what fun would that be? Glad to see it moving from totally conceptual to slightly functional. Is there a way to see any stats on this crystal gathering process?

What I been doing for the last few days is just working on the terrain system. It's a hell lot more work than I thought.

I also built a primitive help page. It's not much but it's better than nothing. In addition, I worked on scenario reloading to help me test better. The game is now 3.5 Kloc!

Can you give us something to do while the H's are doing their crystal/wood collecting thing? Like maybe you can hide some items in the darkness or have us so some simple math or something? I think to have much more support, you need to give your users some satisfaction of having completed something.

I noticed a file about the base unit system is 145 LOC long. That trigger a MANDATORY rewrite. The remedy was code reorganization. The combat mechanic got a whole file dedicated to itself.  This took a significant chunk of my time out of what I am supposed to work on. The upside is that we get cleaner code which will save me time in the future.

Next, I continue work on the meta system for jobs so that stockpiles can assign several different type of jobs at the same time.

Who would think 145 LOC is awfully short?   Now, it's written in coffeescript and I only care about coffeescript. The output might be bizarrely complex for all I care.  
It is per my hacking policy that I slim down any file longer 100 LOC to take care of technical debt that accumulates. You don't want to spend all your time writing them up and making it clean only to mess them up with extreme code addition but you don't want to wait too long to the point that it slow down your coding to a screeching halt either.

Anyway, my output is too irregular lately, thought it's a normal considering that I have my up and downs in motivation.

Lately, the code been giving me hell as I come to grip with old code and try to understand it. I reorganized the map file once again(it exceeds 100 LOC regularly), consolidating collision check functions into the Collision class. That gave me a lot of errors in my code in which I have to jump around to find. Very frustrating since the environment don't produce useful stack trace to use.

I finally got the gatherer unit to look for timber, not trees. However, there's a bug in which it will pick up a timber at the stockpile location and drop it at the same location again and again, which took me a while to figure out.

I tried to use an untested collision function that unsurprisingly doesn't work. I'll have to figure out how to make it work.