Where is alive.cfg? Mission working, but no persistence.

  1. 7 years ago
    Edited 7 years ago by Shamorshin

    So I've downloaded ALiVE, added it and the ALiVE Server folders to my server's mod list, ensured that they're loading in, and I'm getting the error that the server is unable to open alive.cfg.

    For the life of me, I can't find alive.cfg anywhere. Where do I get this file? Do I need to just create an empty alive.cfg in my server's root directory?

    If not (and I assume not), where can I find this file? Googling the issue isn't helping find out where it is, and I don't see alive.cfg anywhere in the downloaded mods.

    I've been running ALiVE well with everything going fine on the mission side, except persistence is totally non-functional, despite all modules with the option to enable persistence enabled, and database saved to local. Where am I going wrong? I hope it's just that I'm missing this.

    Also, is there a way to clear out old database saves? I've changed the server name with every updated version (adding in what the players have done throughout a mission via EDEN after the mission is complete and then re-uploading the mission file as a newly named .pbo to avoid conflicts). For a few updates, we had persistence working at least for vehicles, but now there is none whatsoever following an admin-logged server save and exit.

  2. Edited 7 years ago by Shamorshin

    Update: As it stands right now, we have persistence of AI-controlled units, vehicles, and I'm testing object placement. Objects placed via fortify without activating player logistics actions are not persistent.

    I don't know what was going on before. I've disabled player saving between sessions, so I respawn appropriately after server save and exit, and vehicles stay where they were. testing objects.
    ----------
    Update:

    • server save and exit saves some objects when picked up and dropped via player logistics actions
    • server save and exit saved player position data as appropriate, but did not do this last time. will test again.
    • player backpack with very limited supplies also dropped on the ground where player respawned. ???

    So, object permanence on server-save-and-exit is established as long as player logistics is enabled, and the object is placed, picked up, and dropped by a player. EX: I used my fortify tool to spawn an H-barrier wall segment (guess that's enabled through a mod we're using)....and just placing it does not allow it to persist. BUT -- placing it, then picking it up with the scroll wheel player logistics action, and then dropping it, allows it to persist through server-save-and-exit. Is this working as intended?

    It sucks because that means that player logistics needs to be constantly enabled, which means players can conceivably destroy the carefully made compositions I've placed for them as bases.

    Is there a way to enable and disable player logistics actions mid-mission?

    -------

  3. Edited 7 years ago by HeroesandvillainsOS

    Lol I think Chernarus is fine. I suppose it’s always best practice to setup a quick test and run around for a bit just to see, if you’re ever not sure on a map, but yeah lots of people use Chernarus.

    No War Room is not required for persistence. Neither is @aliveserver if saving locally. Just set the Data module to local saving instead of cloud and the mission will save to the server’s profile.