The intention was always to make an AI you can verse. I don't think making a multiplayer game for a jam is a good idea, since it actually requires several people (in this case 3) to be available at the same time (plus there are only 700 of you guys in this jam). I want everyone to be able to explore the full game, so in my mind an AI is always mandatory.
The real problem that I faced (aka why the house collapsed) is the fact that I didn't plan with the fields being such a pain to make. The actual collision detection to field conversion was tough on its own, but then the actual problem crushed me. You can't just put 'em in a neat 2d array (or a 3d or 4d array for that matter), because the space is overlapping. Basically I ended up with all field stored in a 1d array and no relation to each other. Can't make rules when you don't have info on the fields.
One might argue to make simpler games (to win or impress all the people), but I participate to push myself and learn new stuff. It usually fails, but as someone said "experience is just a fancy name for failure" and I am all about this.
I am writing way too much again. TLDR thank you for your feedback, I am working on improving.