Quote:
Taqwus said:
Actually, we already know that the movement order could store an associated destination in the turn file because it already does in the event that the movement takes just one turn. The only differences, if we ignore the above suggestion about times, are that the destination be interpreted as take the fastest route to this province even if we can't reach it in one turn instead of move to this province; and that the movement order be preserved for the next turn if not preserved. *shrug*
|
That makes sense. At the moment it does things in a pbem way. I put my "I want to" into a .2h file (to host file) which is then absorbed, processed, and the results are kicked out to a .trn file (turn file). Any changes to the map are written to the fthrlnd file (fatherland) on the host server. Alot of that is invisible to any that isnt running a server but it defines the pbem starting basis of the game.
So far we have gotten some nice benefits from the game being changed to save an order that it got in the .2h file and send it back as a pre-set order of the same unit or province in the .trn file (monthly casting, queues, etc). I suppose the "where I move next" might be restored to the same unit as the default "where I move next" if the game is set to refigure the path each time. It might even turn off the "if move is possible" check which would allow me to say "move to 495" even if no route is available when I give the command. The army would continually try to go there until eventually it becomes available.
Id LOVE to see real multi-turn memory be written into the game. Many of my dreams are involved with the game being able to store a command for the future.
At the moment the maps and mods commands are all "set it up at the beginning of the game" stuff. It would be a blast if we could get turn recognition or time-passed recognition into some of the commands. Such as "on turn 30" or "after 10 turns".