Ok, after many hours of taking a default config file, and making one change at a time, I have finally found the reason for the /racestart message not working in my 3.2 config.
If you delete this line :-
ScheduledAction =
0 0 0 * * * |/rcm Midnight warning to all working men!:/rcm_all|
0 0 0 1 1 * |/rcm Happy New Year!:/rcm_all
or you try and hash it out with # like this
#ScheduledAction =
0 0 0 * * * |/rcm Midnight warning to all working men!:/rcm_all|
0 0 0 1 1 * |/rcm Happy New Year!:/rcm_all
or this
#ScheduledAction =
# 0 0 0 * * * |/rcm Midnight warning to all working men!:/rcm_all|
# 0 0 0 1 1 * |/rcm Happy New Year!:/rcm_all
or this
#ScheduledAction = 0 0 0 * * * |/rcm Midnight warning to all working men!:/rcm_all| 0 0 0 1 1 * |/rcm Happy New Year!:/rcm_all
Then the race start message will no longer work in v3.2 or the newer exe available for download from this thread, basically you MUST have a ScheduledAction command of some kind, active in the config, or you don't get a race start message.
I have not noticed this problem on my demo server as I do use scheduled actions there, but I have no need for them on my S2 server.
This behaviour is not present in version 2.9 so it's appeared since that version.
Is this a new design feature ? or a bug ?