- 0
Restarting Arma3 dediserver 500 times during script development?
-
Similar Content
-
- 0 replies
- 1358 views
-
- 2 replies
- 2086 views
-
- 3 replies
- 1675 views
-
- 3 answers
- 1339 views
-
- 0 answers
- 1009 views
-
- Advertisement
Question
mgm
Hi All,
I have a question to seasoned scripters please. First a little background, I recently started writing a basic script, lots of pain with 'general error' / 'object is null' etc. errors but finally there is some progress, things looking up at least it is fun! :D
I now have some tools which I did not have on day0 - these help me save time suchas git setup on desktop+laptop+mobile and bat/cmd scripts to easily restart server and so on.
However there is one issue which still feels like I am doing something totally wrong: each time I change a file, however tiny, I still need to restart the whole dam server which takes a good 2-3 minutes.
2-3 mins doesn't sound like a lot but I need to test a lot of things as you can imagine so 500per day x 2-3 minutes quickly add up to serious numbers [i admit I exaggerate the number a little but you get the point!].
Potential solutions/improvement options I read about:
So the above is my problem, what do you guys do to quickly change files & re-test? Is there a utility or some clever hack to improve the development cycle massively?
Thanks in advance for any input!
P.S.: (don't get mad awol but) in my quest for quicker restarts, for the time being I even dropped 'epochmod' from startup options. Once I have less 'general error's I will add it back to test the relatively mature code under Epoch. I read about different classnames possibly being an issue and that some BIS_fnc's might not working with Epoch (info source: Vampire's blog) so will need to definitely test in Epoch - as soon as I have something to test!)
Link to comment
Share on other sites
19 answers to this question
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now