Thank you, I agree the proximity requirement for the mind control is quite annoying, I wish I cut that from the submission. There was supposed to be more around that in terms of gameplay and visuals to indicate where the boundary was. One of the functions I wanted to include, but couldn't, involved picking up and throwing the slug and the proximity thing was supposed to snap you back to the slugs perspective when you flew too far and that was going to be a puzzle solution. I had a few puzzle ideas involving the proximity mechanic/constraint and that's why its in the game but I neglected to take it out. I probably could have enhanced the experience much more if I had removed it especially since its one of the easier things to cut and not break everything else lol.

Thanks, originally there was but it was too much for myself to handle to implement the original premise in the time I had and I gave pretty much everything I had to get it out in this state. I had to make some hard decisions about what the bare minimum submission would be. Originally, there was the idea that you would try to achieve an objective and there would be obstacles that required you to think about what actions and context could get you past a barrier, the first would be the player controlling an NPC and throwing the player slug over a wall which was nearly in the submission but I had to cut it due to instability and being unable to resolve that instability in the time I had.  The major lesson I learned in that respect was that I need to implement a good finite state machine to handle action behaviour. It was essential and something I should have properly implemented instead of trying to cut corners to save time because the instability from that decision caused a large chunk of my time to go to debugging those problems that arised from that, particularly as the number of NPCs rose and those problems became unavoidable.