IT07 Posted March 17, 2015 Author Report Share Posted March 17, 2015 UPDATE! Code moved to GitHub. Link to comment Share on other sites More sharing options...
HackSaW_TM Posted March 18, 2015 Report Share Posted March 18, 2015 Hello Guys even tho i got the script working and i have changed my restart time as it is scheduled to 4 hrs but server warnings was given based on 3 hrs . any reason why? please see my init file thanks a lot ... Hardened you are awesome mate :D [] execVM "IgiLoad\IgiLoadInit.sqf"; [] execVM "wai\remote.sqf"; //Supply Drop Alert Event "SDROP_Alert" addPublicVariableEventHandler { hint parseText format["%1", _this select 1]; }; if (isServer) then { fn_getBuildingstospawnLoot = compile preProcessFileLineNumbers "Custom\LSpawner\fn_LSgetBuildingstospawnLoot.sqf"; LSdeleter = compile preProcessFileLineNumbers "Custom\LSpawner\LSdeleter.sqf"; execVM "Custom\LSpawner\Lootspawner.sqf"; }; // Status Bar [] execVM "scripts\fn_statusBar.sqf"; // Welcome Credits [] execVM "custom\welcome.sqf"; if(hasInterface)then{execVM "semClient.sqf"; // Time until next restart by IT07 private["_SC_restartIntvlHours"]; /////// CONFIG /////// // Please edit the 3 lines below to your likings _SC_restartIntvlHours = 4; // Change the number 1 into the number of hours your server will be up before it restarts _SC_restartWarnTopMessage = "== WARNING =="; // What the first line of the warning should say _SC_restartTimeHintSilent = false; // RECOMMENDED: false; If true, it will mess with debug monitor! ////////////////////// DO NOT CHANGE ANYTHING BELOW THIS LINE [_SC_restartIntvlHours, _SC_restartWarnTopMessage, _SC_restartTimeHintSilent] ExecVM "ScarCode\SC_restartTime.sqf"; }; //cmEARPLUGS CODE START ////////////////////////////////////////////////////////////////////////// call compile preProcessFileLineNumbers "cmEarplugs\cm_veh_fun.sqf"; //cmEARPLUGS CODE END ////////////////////////////////////////////////////////////////////////// [spoiler/] Link to comment Share on other sites More sharing options...
IT07 Posted March 18, 2015 Author Report Share Posted March 18, 2015 If you do not add -autoinit to the launch parameters of the server, then the mission will start only when the first player joins. Which will mean that the server was already running for a longer period of time. Sorry I should have mentioned it. arafinar 1 Link to comment Share on other sites More sharing options...
HackSaW_TM Posted March 18, 2015 Report Share Posted March 18, 2015 If you do not add -autoinit to the launch parameters of the server, then the mission will start only when the first player joins. Which will mean that the server was already running for a longer period of time. Sorry I should have mentioned it. Strange coz i belive i have added... -autoInit -mod=@Epoch;@EpochHive;@mas;@AllInArmaTerrainPack -name=A3E_Server -profiles=A3E_Server -config=A3E_Server\server.cfg -cfg=A3E_Server\basic.cfg -ip=217.23.11.160 -port=2302 Link to comment Share on other sites More sharing options...
IT07 Posted March 18, 2015 Author Report Share Posted March 18, 2015 To make it clear: you have the interval set in the config to 4 hours, but the first warning is given at 2:30 instead of 3:30? If so, then there must be something you've looked over because it should (and it does) work fine on any other server. I have tested this too often to doubt that there isn't an error in my script. Link to comment Share on other sites More sharing options...
arafinar Posted March 18, 2015 Report Share Posted March 18, 2015 Strange coz i belive i have added... -autoInit -mod=@Epoch;@EpochHive;@mas;@AllInArmaTerrainPack -name=A3E_Server -profiles=A3E_Server -config=A3E_Server\server.cfg -cfg=A3E_Server\basic.cfg -ip=217.23.11.160 -port=2302 I put the autoinit at the end and it works right Link to comment Share on other sites More sharing options...
fullaholes Posted March 18, 2015 Report Share Posted March 18, 2015 Does it matter where autoinit goes in the server parameters ? mine looks like this... start /wait C:\TCAFiles\Users\*******\7572\arma3server.exe -ip=69.197.31.179 -port=2300 -profiles=Arma3Config -name=Arma3Config -config=Arma3Config\config.cfg -cfg=Arma3Config\arma3.cfg -autoInit -loadMissionToMemory -mod=@allinarmaterrainpack;@Epoch;@EpochHive; Link to comment Share on other sites More sharing options...
IT07 Posted March 19, 2015 Author Report Share Posted March 19, 2015 Does it matter where autoinit goes in the server parameters ? mine looks like this... start /wait C:\TCAFiles\Users\*******\7572\arma3server.exe -ip=69.197.31.179 -port=2300 -profiles=Arma3Config -name=Arma3Config -config=Arma3Config\config.cfg -cfg=Arma3Config\arma3.cfg -autoInit -loadMissionToMemory -mod=@allinarmaterrainpack;@Epoch;@EpochHive; That looks fine to me. Try it. fullaholes 1 Link to comment Share on other sites More sharing options...
IT07 Posted March 19, 2015 Author Report Share Posted March 19, 2015 UPDATE: Added some more info the the main post. Link to comment Share on other sites More sharing options...
HackSaW_TM Posted March 19, 2015 Report Share Posted March 19, 2015 Hello Guys even tho i got the script working and i have changed my restart time as it is scheduled to 4 hrs but server warnings was given based on 3 hrs . any reason why? please see my init file thanks a lot ... Hardened you are awesome mate :D [] execVM "IgiLoad\IgiLoadInit.sqf"; [] execVM "wai\remote.sqf"; //Supply Drop Alert Event "SDROP_Alert" addPublicVariableEventHandler { hint parseText format["%1", _this select 1]; }; if (isServer) then { fn_getBuildingstospawnLoot = compile preProcessFileLineNumbers "Custom\LSpawner\fn_LSgetBuildingstospawnLoot.sqf"; LSdeleter = compile preProcessFileLineNumbers "Custom\LSpawner\LSdeleter.sqf"; execVM "Custom\LSpawner\Lootspawner.sqf"; }; // Status Bar [] execVM "scripts\fn_statusBar.sqf"; // Welcome Credits [] execVM "custom\welcome.sqf"; if(hasInterface)then{execVM "semClient.sqf"; // Time until next restart by IT07 private["_SC_restartIntvlHours"]; /////// CONFIG /////// // Please edit the 3 lines below to your likings _SC_restartIntvlHours = 4; // Change the number 1 into the number of hours your server will be up before it restarts _SC_restartWarnTopMessage = "== WARNING =="; // What the first line of the warning should say _SC_restartTimeHintSilent = false; // RECOMMENDED: false; If true, it will mess with debug monitor! ////////////////////// DO NOT CHANGE ANYTHING BELOW THIS LINE [_SC_restartIntvlHours, _SC_restartWarnTopMessage, _SC_restartTimeHintSilent] ExecVM "ScarCode\SC_restartTime.sqf"; }; //cmEARPLUGS CODE START ////////////////////////////////////////////////////////////////////////// call compile preProcessFileLineNumbers "cmEarplugs\cm_veh_fun.sqf"; //cmEARPLUGS CODE END ////////////////////////////////////////////////////////////////////////// [spoiler/] Found the solution :) I've just changed 5 instead of 4 in <_SC_restartIntvlHours = 4;> :D Link to comment Share on other sites More sharing options...
IT07 Posted March 20, 2015 Author Report Share Posted March 20, 2015 [ADDED] Dev-update to the main post. Link to comment Share on other sites More sharing options...
IT07 Posted March 21, 2015 Author Report Share Posted March 21, 2015 Good news! New dev update added to main post. Link to comment Share on other sites More sharing options...
R4ziel Posted March 21, 2015 Report Share Posted March 21, 2015 Looking forward to testing it IT07, will test it a soon as its released and give you feedback IT07 1 Link to comment Share on other sites More sharing options...
fullaholes Posted March 21, 2015 Report Share Posted March 21, 2015 Looking forward to testing it IT07, will test it a soon as its released and give you feedback It's already been released o_0 check the first page for download/install instructions... Link to comment Share on other sites More sharing options...
IT07 Posted March 21, 2015 Author Report Share Posted March 21, 2015 It's already been released o_0 check the first page for download/install instructions... You did not read it correctly. At the moment of writing this, it has NOT been released yet. Link to comment Share on other sites More sharing options...
IT07 Posted March 22, 2015 Author Report Share Posted March 22, 2015 Development has been delayed a little bit due to restructuring of the code for safety and performance reasons. The implementation of the schedule support is very demanding to run and should be scripted carefully to prevent CPU clogging. Thank you for your patience. Link to comment Share on other sites More sharing options...
IT07 Posted March 22, 2015 Author Report Share Posted March 22, 2015 UPDATE New version :) Scheduled restarts are now supported! Link to comment Share on other sites More sharing options...
IT07 Posted March 22, 2015 Author Report Share Posted March 22, 2015 - Updated the SC_restartWarnings.sqf on GitHub again. It fixes a leftover from testing. (hintSilent) Link to comment Share on other sites More sharing options...
IT07 Posted March 23, 2015 Author Report Share Posted March 23, 2015 UPDATE! New version: 02037_BETA See main post for details. Link to comment Share on other sites More sharing options...
spartan Posted March 23, 2015 Report Share Posted March 23, 2015 If I am using scheduled restarts should I comment out the dynamic restart interval line ? Link to comment Share on other sites More sharing options...
IT07 Posted March 23, 2015 Author Report Share Posted March 23, 2015 No you don't have to. The latest version has instructions in the file that tell you to ignore the _restartInterval if using schedule. Link to comment Share on other sites More sharing options...
Metalfoundry Posted March 24, 2015 Report Share Posted March 24, 2015 The script shows the message at the whole server lifetime for every player at different times?? Where´s the issue? Link to comment Share on other sites More sharing options...
IT07 Posted March 24, 2015 Author Report Share Posted March 24, 2015 Are you using schedule or dynamic? It could also be that players with bad connections don't get the serverTime synchronized correctly. EDIT: Make sure you run the latest version. Link to comment Share on other sites More sharing options...
Metalfoundry Posted March 25, 2015 Report Share Posted March 25, 2015 hm, no way, all players get warnings at different times.. i was using scheduled an used the standard times 0,4,8,12,16,20. Had to delete it, 50 players which get wrong warnings.. äh no ^^ Link to comment Share on other sites More sharing options...
IT07 Posted March 25, 2015 Author Report Share Posted March 25, 2015 I don't release scripts that do not work. You must have configured the schedule the wrong way. You say that you have 0,4,8,12,16,20. Does your schedule look like this: _restartSchedule = [[0,00],[4,00],[8,00],[12,00],[16,00],[20,00]]; Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now