62
edits
Scheduling: Difference between revisions
Said more about life/inter keywords
Commando950 (talk | contribs) (Created a page talking about scheduling. Included basic trivia, introduction, and example.) |
Commando950 (talk | contribs) (Said more about life/inter keywords) |
||
| Line 23: | Line 23: | ||
life sleepytime | life sleepytime | ||
</nowiki> | </nowiki> | ||
<code>inter <script></code> sets what interaction script you are running while <code>life <script></code> sets what life script you are running. | |||
Setting either <code>inter</code> or <code>life</code> with no parameters will make them unload any currently loaded script. Essentially setting there to be no script for this time of day. | |||
An important thing to note about these scripts is how these time statements work. Each <code>>time</code> statement is essentially checking if the current time is '''''greater than''''' the time we are comparing to, if it is true it will load the scripts you have under it. Another thing of importance is how time activities actually wrap around. The scheduling system knows that 19:00 to 6:00 with this example script is still bedtime, waiting until bedtime is over. Since the script can't find any mention of <code>>0.00</code> in your schedule it simply uses the <code>>19.00</code> statement instead. | An important thing to note about these scripts is how these time statements work. Each <code>>time</code> statement is essentially checking if the current time is '''''greater than''''' the time we are comparing to, if it is true it will load the scripts you have under it. Another thing of importance is how time activities actually wrap around. The scheduling system knows that 19:00 to 6:00 with this example script is still bedtime, waiting until bedtime is over. Since the script can't find any mention of <code>>0.00</code> in your schedule it simply uses the <code>>19.00</code> statement instead. | ||