Why might the AI kill its own Forgekeeper if it can't stop yours from holding the center? Also, how do you get runes? As far as I can tell, all tiles are stone
Ah good question. The tiles on the board are face-down. When you mine a tile, it gets added to your hand and its type is revealed. Similar to a card game, you can see what's in your hand, but you can't see what's in your opponent's hand (only how many tiles your opponent has).
| Stone tile | Rune tile |
 |  |
I'll update the description with that info.
Also, as far as the distribution, Rune tiles have the same probability of finding a face card in a standard deck of cards (Stone tiles = 2-10). I tried to make it so you could theoretically play this game with a standard deck of cards and a set of chess pieces (you'd need something for a 7th piece though since chess only has 6).
I'm not sure I understand your question about the AI killing its own Forgekeeper.
94 days ago(+1)
I moved my forgekeeper onto the forge and the enemy could not take it. In response the enemy used 'cave-in' on the space with its forgekeeper. I was wondering why it'd do that.
94 days ago(+1)
Oh hah I think you found a bug lol (or a feature?)
I'm new to writing game AI so you can just chalk it up to that :) I added a line to make the CPU favor quicker "checkmates" if it found multiple so my guess is it saw both outcomes and went with the quicker one. That's really funny to me that it just yeeted its own forgekeeper.
94 days ago(+1)
Makes sense, I was wondering if it was something like that :) In general, the AI on 'normal' seems pretty good; I would not have guessed it was your first time trying to code something like this!