One problem I have noticed in playing on-line games is that the player who is on-line constantly will generally rip those of us who have to go to work. It became more evident to me today when I fired a rocket at a province my opponent was 20 minutes out from and he immediately reversed course. In todays military, maybe. In 1942 not a chance.
One possible solution that would make the game more reflective of the time period and solve several problems including air plane tick timing, rocket avoidance, and somewhat level the playing field between the constantly on-line and the more casual gamer would be he introduction of "orders delay". This reflects the time lag from the time an order is issued to the time it is received and executed. Programming should be simple as we have "delay" available with most unit type movement commands. This delay reflects the time delay between a general issuing an order and the time it is received in the field.
How it would work, is when a player issues a command, the unit will execute the command in x amount of time. I suggest 15 minutes, but it could be shorter or longer. The command could be cancelled prior to implementation and the unit would just contiue with the action it was preforming at that time. Construction would not be affected as there is already a long time lag between the building command and final production of the unit or improvement.
One possible solution that would make the game more reflective of the time period and solve several problems including air plane tick timing, rocket avoidance, and somewhat level the playing field between the constantly on-line and the more casual gamer would be he introduction of "orders delay". This reflects the time lag from the time an order is issued to the time it is received and executed. Programming should be simple as we have "delay" available with most unit type movement commands. This delay reflects the time delay between a general issuing an order and the time it is received in the field.
How it would work, is when a player issues a command, the unit will execute the command in x amount of time. I suggest 15 minutes, but it could be shorter or longer. The command could be cancelled prior to implementation and the unit would just contiue with the action it was preforming at that time. Construction would not be affected as there is already a long time lag between the building command and final production of the unit or improvement.
"A good plan, violently executed now, is better than a perfect plan next week." - General George S. Patton, Jr.
"Do, or do not. There is no try" - Yoda
"Do, or do not. There is no try" - Yoda