I've been thinking about MoveCoT and wondering why it wasn't implimented, a few possibilities arose in my mind as to why, one was that what if an event tried to move a nonexistant CoT? Another was the possibility that it scrambled the CoT allocation terribly. Another possibility I thought of was it was just broken, and would be too much work to fix.
But how about this? How about a syntax of the following:
command = { type = movecot where = oldprovince value = newprovince }
If no CoT is in oldprovince, it makes a new CoT in the newprovince. This way if there's no CoT to move, it makes a new one. That is, if it's fixable.
Please? This is one command that would solve so very many problems....
But how about this? How about a syntax of the following:
command = { type = movecot where = oldprovince value = newprovince }
If no CoT is in oldprovince, it makes a new CoT in the newprovince. This way if there's no CoT to move, it makes a new one. That is, if it's fixable.
Please? This is one command that would solve so very many problems....