Double dipping on this one. I coded up a simple Unity Tutorial and made a video... which per my normal style has a lot of doodles :P
So... Today I worked on making AI decide when to increase the population and when not.It went better than I expected - it seems to be working more or less fine. Only some minor changes in formulas or quotients should be made.
I also started to learn about neural networks. If everything goes well I might even try to implement them in the game. :)
Yesterday's update can be found here.
In a case of any questions or suggestions, don't hesitate to contact me here or on twitter. ;)
For more updates, you should follow my twitter account - @PeterLauris and the account of Crystal Kingdom - @CrystalKingdom_.
Today I worked on the initial unit movement, no transitions just pick up and drop. You can quick cycle through the units with the "." key. I did add a possible movements highlight but as you can see below this is entirely ignored. Also the world's bounds aren't adhered to...
Tomorrow I'll look into actually calculating tile type cost and distance cost. I'll need to calculate the cost to every tile on the map from the unit's current position. I think that would involve some dijkstra? Not sure, never done path finding.
Implemented around 9 more words for this Forth implementation. Again, I mostly focused on easy words, but that's about the last day I can do that. The rest are a bit more complicated, but are the last bits for really getting a working Forth. The other outstanding piece is serial output so things like TELL, EMIT, & KEY can be implemented.
Enums are now implemented! Unfortuantely right now they aren't evaluated so you can't do anything like:
enum Colors
{
primary = 30 + 10 + 50,
}
But static values single values work fine.
enum Colors
{
primary = #ff0000,
secondary = #00ff22,
tertiary = #2b00ff,
}
As far as variable scope goes, if you have a variable called 'Colors' then you won't be able to use the enum, and there is no special 'global' keyword or anything yet.
I've also just realized that you couldn't use enums within the layout due to it using a capital letter, so I think I need to rethink how component definitions work and possibly work towards components not needing to have an uppercase first letter.