Post a Reply

Manual Server save hangs

  1. 8 years ago

    Tupolov

    Show in context Administrator
    1. You can configure respawn however you want as long as respawn on restart is disabled
    2. The only way to save a game is to exit currently. The save script should do this... If it doesn't, something is breaking it.
    3. Quick start is a fully persistent mission. Auto init is irrelevant and to be honest something we haven't reallly tested and may not work. The expected use case is for COOP missions that run anywhere from 1-x hours that are "saved" once the session is complete. Sessions are started by an admin and saved by an admin.

    To your points about ACE, CUP, BAF - all work fine with persistence.
    To your point about Altis and larger missions, we have stress tested to around 2000 AI and large Altis missions, so it shouldn't break anything.
    Please do check your module settings, particularly player persistence settings etc.

    As you say, start simple and validate persistence is working before introducing other elements. Auto-init would be the last thing to test.

  2. T

    thebgpikester

    Show in context

    Hi Tupolev, reason for saving a state whilst 'in persistence' is so you can reboot the box on a schedule using Windows Scheduled Tasks and have it come up and load back into the same mission again, or if there is a crash (small chance but its been known) without any interactions at all. I can currently achieve this and I do - I don't touch the box all week, it loads an alive mission, reboots the box every night but cannot hold persistent maps. To do this I need to send a save state inside the mission on a scheduled time period. I've already asked for that enhancement and I understand that ALiVE can't do that currently. I could probably script something but I'm not sure how to either a) access the game scripting from outside in the Windows environment or b) access the Windows environment from inside the gaming scripting environment - I'm not sure these are possible as developers usually design safety mechanisms to prevent it as its a security risk.

    You can't use ALiVE persistence without a server admin initiating a save so we are looking at organised group play, with a start time and an end time. That's a completely different style of gameplay to running a server 24/7 with restarts scheduled. These are fundamentally different approaches and solve different problems, just in this case not mine.

    I hope this explains what i'm trying to achieve and why, i don't think anyone is really understanding it because they don't play in the same way. The benefit of this different style is leveraging persistence (proper persistance over days and restarts - unattended) with large scale conflict in order to have quite large ongoing full map campaigns that continue to play themselves out whether there is one player, a dozen players or no players. It allows a solo player to still do key things like moving supplies, setting up mortar pits and defences with ACE and marking the map with these new positions, then later perhaps the main group come on and log (after say a reboot) and then utilise whats been left behind. It allows reconnaisance and preparation to be done in a day/night cycle, sniper teams can attrit, we can have longer logistics resupply timings. And finally, it allows the admin (me) to take absolutely no part in it unless i want to, certainly not to have to turn up, save the map and close up the session when they are done.

    If you can see a way to make that happen we can leverage ALiVE to run outside the gameplay session and extend into a proper war with logistics lasting some time without having to be logged into every four hours to manually save and exit form the game and then reboot it, clear up memory, patch server, check security software has latest definitions etc.

    Now if I've missed something in my understanding on how to get this to work I would be delighted to be shown the way so I can achieve that.