[L. Duke]

Obsolete

Chron is a mms plugin that allows you to schedule commands/configs to run at any time (can also be limited to a certain day of the week).

Chron by L. Duke www.LDuke.com Installation Download and install Metamod: Source Start the server and type meta. If you receive an error because the command is unknown, go back to Step 1. Open addons/metamod/metaplugins.ini and add the following line: addons/chron/bin/chron_mm Save any cfg files you want to execute in the cfg/chron directory Add you chron jobs to cfg/chron/!chronjobs.cfg (see the file for examples) type chron_help in the server console to see all the commands and options Notes: Chron_job cfg files will only run once during the specified time period, so if you have a command in server.cfg it will be reset when the map changes. For example, if you have sv_gravity 800 in server.cfg and a lowgravity chron job that sets sv_gravity 400 for three hours, the gravity will reset to 800 when the map changes even if the three hours is not over. To work properly, you need to remove any setting from server.cfg that you are changing the cfg/chron/*.cfg files. Chron_job2 cfg files will run once per map. Any settings defined in a cfg file executed using the chron_job2 command will overwrite settings in server.cfg for the remaineder of that map. The server.cfg settings will not be restored when time is up, but they will be restored on the next map change after the time is up.

Download chron_0.2.zip

[tcviper]

Nice job LDuke!

[FlyingMongoose]

Okay, can there be a cvar to have the chron execute on mapchange? Because personally I would find that very very useful. (We have a custom maps only day on our server and each map runs for about 20 minutes, but we also run different configs from normal, every wednesday, having it execute every mapchange would be very nice), otherwise awesome job!

[Rebell]

cool

would be nice if a job can be planned that Restarts xx seconds like this:

chron_job saychron R180

so all 3 minutes this will be done...

[Ace Rimmer]

This is going to be sooo useful. I can ditch half of my scripts and use this instead.

Any chance of adding a couple of readable server_vars that can be read from es?

[L. Duke]

I'm going to be adding a new "job type" that executes on every map change during the specified time in addition to the "excute once" type job in the beta release.

I would consider adding some the server cvars you're talking about if you could give me more information about both what's required technically and what info you want exposed.

[FlyingMongoose]

Awesome to hear duke, I can't tell you who extraordinarily useful this is!

out of curiosity, where do chron configs execute? before or after the server.cfg? if before can there be a way to make it after? or before or after the autoexec?

chron_job saychron 19:00 19:01 0 = exec before autoexec
chron_job saychron 19:00 19:01 1 = exec after autoexec
chron_job saychron 19:00 19:01 2 = exec after server.cfg

[Ace Rimmer]

Hi L. Duke:

Well I haven't looked closely at this yet but it would be very simple. Something like a cvar for Date Hour Minute Second and possibly a total time since 1970 (I don't know if you're familiar with that concept but it is basically a count in seconds since 1970).

So it would be:

server_var(cron_date) or day or whatever you can add
server_var(cron_hour) -would report the server hour
server_var(cron_munute)
server_var(cron_second)

This way we wouldn't have to add recurring counters in ES or wait fro round starts etc. to check the time.

The server_var(cron_count) could be a a progressive number of seconds as mentioned above.

For example in my clan practise script I have to convert the start time to a number of minutes and the end time to a number of minutes so that I can find the difference between the two.

I hope this makes sense.

I am sorry that my knowledge in this area is limited to event scripts only so what I am asking may be ridiculous.

I must add that I haven't thought this though completely so please don't rush ahead and do it, only for me as it were.

Thanks for your hard work anyway.

:-)

[Rebell]

cool ideas !

[FlyingMongoose]

Duke man, I'm anxiously awaiting a new release of this! I could definitely use it soon. Not gonna force ya to do anything...I just don't want things to fall out of your scope of projects!