pb_sv_load pbsvmsg.cfg
to the bottom of the pbsv.cfg file located in /pb/ of your COD4/WaW dedicated server files.
Don't have the pbsv.cfg file within the /pb/ folder of your COD4/WaW dedicated server files?:
No need to worry, if you have access to the FTP of your COD4/WaW dedicated server files i'm assuming you have access to rcon.
Update:
A lot of reported cases where you edit he /pb/ configs or generate the config via rcon but doesn't get put into /pb/ check to see if "/.callofduty4/pb/" or for WaW "/.callofduty5/pb/" exist. If it does then put the message file in there and edit he pbsv.cfg file within that folder!
If you don't I CANNOT help you, sorry!
Step 1: Log into rcon from either a 3rd party application or COD4/WaW itself from console.
/rcon login rconpasswordStep 2: Create the pbsv.cfg file within the /pb/ folder of your COD4/WaW dedicated server files.
/rcon pb_sv_writecfgStep 3: Go back to the top of How-To include the pbsvmsg.cfg and start again.
wait 5 exec pbsv.cfgto the bottom of the config.cfg file located in /main/ of your COD4/WaW dedicated server files.
server.cfg dedicated.cfg etc...Save it & upload it your COD4/WaW server.
Lets say you have 5 messages to display and you want 30 seconds between each message and that you want the first one to start 10 seconds after you start the server.
Right, the X value in the first task statement is 10 (as you wanted) and the successive X value for the tasks is 30 more than the last (so the second is 40, the third 70, etc).
The Y value never changes and must include the 10 second offset of the first message, so the Y value for all messages (from the equation above) is (30*5) + 10 = 160 seconds.
So your task list will look like this:
pb_sv_task 10 160 "say Message1" pb_sv_task 40 160 "say Message2" // 30 second delay + the 10 second X value above pb_sv_task 70 160 "say Message3" // 30 second delay + the 40 second X value above pb_sv_task 100 160 "say Message4" // etc pb_sv_task 130 160 "say Message5"
In this example, the messages will repeat 160 seconds after the first message. Your first message will repeat at 160 seconds (not 170!), which is 30 seconds after the last message appeared at 130 seconds. So you have 30 second gap between all messages.
Thats only applies if you want your messages to display evenly spaced. If you want them all jumbled up and looking random, make the Y values all different.
Ultimately, regardless of how you set this up, the last 'X' value should be less than the Y values, otherwise the messages will mix up.
A variation on this is if you want a number of messages, 'A', to display evenly over 'B' number of seconds. In this case, the difference between the 'X' values in the pb_sv_task statement is:
Your 'Y' values, again never change, can be calculated by:
For example: You want 5 messages to display over 240 seconds (4 minutes) and you want the first message to display 10 seconds after server start (ie, the first task X value is 10). The difference between the 'X' values must be 240/5 = 48 and all 'Y' values must be 240 + 10 = 250. So your task list will look like this:
pb_sv_task 10 250 "say Message1" pb_sv_task 58 250 "say Message2" // 48 second delay + the 10 second X value above pb_sv_task 106 250 "say Message3" // 48 second delay + the 58 second X value above pb_sv_task 154 250 "say Message4" // 48 second delay + the 106 second X value above pb_sv_task 202 250 "say Message5" //etc
Add the delay of 48 seconds between the last message and the first message repeating and the total is 250 - your 'Y' value.