Our game involve armies slowly moving from node to node on a map. I'm trying to use the scheduler to move an army from a node to another, look for enemy at destination, and if there isn't, move the army further to another node (if the player had order a longer travel). 

Is there something preventing a scheduled module from scheduling itself again? Apparently my module is not able to schedule itself more than once. 

Also, is there a way to debug line per line a module executed by the scheduler?

And the last question which may make the previous ones irrelevant: Is the scheduler the good tool for this?

Thanks for the feedback

Thanks Gabriel:)

I tought about doing all this from the every minute script, but that meant quite a lot of useless server execution time to check everything when nothing was in-fact happening. The hybrid solution (using the scheduler, but doing the recalling from "Every Minute") does feel a bit clunky but I'll think about it some more.

I completely understand the need to avoid infinite loop but could there be any way to make this a default setting while having a way to allow the scheduler some looping before shutting it off? Maybe by allowing us to set by a parameter in the Spark.getScheduler() function the maximum amount of time it is conceivable that our application make it loop.

I'm also looking forward to that debugging method on the Scheduler!