when are u gonna throw some nanos at us in crysis wars
Posts by NecessaryEvil
-
-
We'll get back to you soon.
-
You have to be invited by another member and then receive enough votes to join. Try joining us on teamspeak first.
-
you can usually find a map in the convenience stores
-
Re-installed battle company...good thing for ripley's post...had to refresh my memory on the house names
-
you're welcome 1 year later lol
-
welcome aboard bladey
-
-
Quote from "MistaD"
Yea I retired man. Computer died and I figured that buying a new one was the same as a semester at a university.
so what are you using now? an etch-a-sketch with wifi?Quote from "MistaD"I figured the university was a better investment.
incorrect. lol -
Yep, hacking has unfortunately gotten out of control but it was fun while it lasted :wink:
-
lol wtf. how have u been mistad?
-
All hope for c3 is dead
-
I agree with rip. Four restarts per day was fine until the heli began respawning on the island everytime. It would be simplest to go to 2 restarts per day because it would only mean deleting some schedule lines, but if every 12 hours isn't enough we can try 8 hour restarts after that.
-
Only one player would see the restart messages before because there is supposed to be a hyphen before each 1 in the line <cmd>say -1 message</cmd>
And de-sync doesn't seem to be as big of a problem when the server has 25 as opposed to 50 players.
-
The server was originally only sending warning restart messages to one player because of a syntax error in scheduler.xml, but all players should be seeing the messages as of 10:00 server time 8/23/2012. This could be why a lot of players didn't come back after the restart. If not, it's better to not have 50 players anyways because desync is awful when the server is full even after a fresh restart.
-
2:00, 8:00, 14:00, and 20:00 should be fine, and there shouldn't be any surprises with countdown messages each hour, plus the standard 10, 5, and 1 minute warnings.
-
I think it's time for the recommended 4 restarts per day. Every 6 hours after the current 2:10am restart should be fine with the standard warning messages ahead of time. If we really want to get carried away, we can warn when the next restart is coming each hour. I'll get started on the schedule and of course submit for approval before implementing any changes.
XML
Display More<?xml version="1.0" ?> - <Scheduler> - <!-- INTERNAL COMMANDS --> - <job id="0"> <time>01:50</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 10 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="1"> <time>01:55</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 5 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="2"> <time>01:59</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 1 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="3"> <time>02:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>#shutdown</cmd> <cmdtype>0</cmdtype> </job> - <job id="4"> <time>03:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 5 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="5"> <time>04:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 4 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="6"> <time>05:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 3 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="7"> <time>06:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 2 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="8"> <time>07:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 1 hour</cmd> <cmdtype>0</cmdtype> </job> - <job id="9"> <time>07:50</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 10 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="10"> <time>07:55</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 5 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="11"> <time>07:59</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 1 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="12"> <time>08:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>#shutdown</cmd> <cmdtype>0</cmdtype> </job> - <job id="13"> <time>09:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 5 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="14"> <time>10:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 4 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="15"> <time>11:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 3 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="16"> <time>12:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 2 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="17"> <time>13:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 1 hour</cmd> <cmdtype>0</cmdtype> </job> - <job id="18"> <time>13:50</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 10 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="19"> <time>13:55</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 5 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="20"> <time>13:59</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 1 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="21"> <time>14:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>#shutdown</cmd> <cmdtype>0</cmdtype> </job> - <job id="22"> <time>15:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 5 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="23"> <time>16:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 4 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="24"> <time>17:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 3 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="25"> <time>18:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 2 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="26"> <time>19:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 1 hour</cmd> <cmdtype>0</cmdtype> </job> - <job id="27"> <time>19:50</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 10 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="28"> <time>19:55</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 5 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="29"> <time>19:59</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Server will Auto restart in 1 min</cmd> <cmdtype>0</cmdtype> </job> - <job id="30"> <time>20:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>#shutdown</cmd> <cmdtype>0</cmdtype> </job> - <job id="31"> <time>21:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 5 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="32"> <time>22:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 4 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="33"> <time>23:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 3 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="34"> <time>00:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 2 hours</cmd> <cmdtype>0</cmdtype> </job> - <job id="35"> <time>01:00</time> <day>1,2,3,4,5,6,7</day> <loop>0</loop> <cmd>say -1 Next scheduled restart in 1 hour</cmd> <cmdtype>0</cmdtype> </job> - <!-- EXTERNAL COMMANDS --> - <job id="36"> <time>02:00</time> <day>1,2,3,4,5,6,7</day> <loop>1</loop> <cmd>C:\BEC\Config\restart_server.bat</cmd> <cmdtype>1</cmdtype> </job> - <job id="37"> <time>08:00</time> <day>1,2,3,4,5,6,7</day> <loop>1</loop> <cmd>C:\BEC\Config\restart_server.bat</cmd> <cmdtype>1</cmdtype> </job> - <job id="38"> <time>14:00</time> <day>1,2,3,4,5,6,7</day> <loop>1</loop> <cmd>C:\BEC\Config\restart_server.bat</cmd> <cmdtype>1</cmdtype> </job> - <job id="39"> <time>20:00</time> <day>1,2,3,4,5,6,7</day> <loop>1</loop> <cmd>C:\BEC\Config\restart_server.bat</cmd> <cmdtype>1</cmdtype> </job> </Scheduler>Hopefully I saved you some time commie but I'm not sure if the last part is right under external commands
-
Adding a scheduled restart won't have an impact on server popularity as it crashes at least once per day as it is. DayZ recommends four restarts per day, but I think once every 12 hours might be enough.
-
LOL. Awesome did u steal it or repair it fresh?
-
The instance ID part is no problem, I already got another one when I tried to sign up for the server-related emails for server administrators. Actually, I filled out the form with the specifications of teabag's server and got an email saying the request was not approved because the uplink speed must be at least 100mbs so I re-did it but just said uplink speed is 100 because I was only interested in being added to the mailing list and not a new instance id, but they sent one anyways.
Hopefully fps won't be a problem if we restart the server at more frequent intervals like the recommended four per day. We can also run the servers with opposite times of day so peak hours are offset.
