It's funny, but I hadn't thought about defining a faith component, just as there is a health component.

The "Convert" order will be processed by an "Order.Convert" handler that must be added in "UnitAI.prototype.UnitFsmSpec".   And what is the thing? According to what I saw it defines finite state machines (FSM) for unit behavior.   https://en.m.wikipedia.org/wiki/Finite-state_machine   "mathematical model of computation. It is an abstract machine that can be in exactly one of a finite number of states at any given time. The FSM can change from one state to another in response to some inputs; the change from one state to another is called a transition".   It was hard for me to understand that.   So this defines how a unit will behave depending on the variants it encounters in the terrain, basically a series of mathematical and circumstantial variables, which dictate the behavior of the unit on the battlefield.   It is not the whole set, but it is the elementary one.   For example if the unit encounters allies or enemies you will see how it will behave although it seems to me that the allies or enemies is in another file.

awesome seems like a good way to play can apply these to download games on aploky            

->  

The Work in Progress is a remnant of the Trac milestone that we had put into place when we used Phabricator in parallel. Currently it's used roughly as Stan describes (including Phabricator differentials that are still lying around) but I agree it's a bit awkward.

Hi, @Dunedan I have read in discord that you can help with this. In this game the user Haddl has disconnected when i clearly won the game. Can u help me? commands.txt metadata.json