It was requested that feedback be split up a little, so here's a new thread for the new update, focused on builders.
I want to commend what I've seen of them so far. I expected builders to be tough to implement, but you've knocked it out of the park already. I did find some quirks, but some of them turned out to be L3D accurate ones. Talked about those on the discord.
- If you quickly assign a builder to a shrugger, they'll place the next tile directly above the last tile from their previous build, resulting in the double step shown here. They should instead walk forward and place the next tile, extending the bridge along the same trajectory.
- As seen in the first pic, building into a ceiling in Loap causes the builder and all subsequent lemmings to get stuck in the ceiling until the top tile is destroyed. In L3D, as shown in the second pic, once a builder is one block away from a ceiling, they will attempt to place the next tile but fail and turn around. A 1 block wide gap is left there and lemmings can freely walk through.
- In the first screenshot, you can assign a lemming to be a blocker after they've placed the next tile but before they step up onto it, creating the situation shown. This is not necessarily a bad thing, but I'll note you can't do this in L3D, as trying to assign a blocker at that moment will be met with an "uh uh!". Intended?
- The second screenshot shows that if the edge of a tile is in the middle of a block rather than the edge, assigning the builder as a blocker/turner will cause them to cancel their build and walk off. You can't do this in L3D, as trying to assign a builder that is in the "first half" of a block as a blocker/turner is met with an "uh uh!". I actually like the L3D behavior, because it acts as a failsafe to prevent you from wasting blockers/turners, because eyeballing the exact alignment of a builder can be quite difficult at times. Also, this new behavior may create backroutes, since it's a new and relatively cheap way to cancel a builder early.
