@Tupolov: First off, thank you for looking into the matter.

I tried that IP 46.228.195.171, but it doesn't belong to my gamserver; instead, it's the IP of an A3 Life Server named "KeksArmy Arma 3 Server Neu!!!"

Where in my logs was this IP? This smells of technical issues with the gameserver company if this IP was maybe given out twice on that January 2nd 2017...

But, alas, I still don't know exactly what to make of the fact that I could yesterday and can today join the gameserver with the "old" IP 46.228.198.108.

On the other hand, I'm very confident that eventually you WILL find the cause of those problems - I think I told you already last time you managed to help me, but I'll gladly repeat it that this mod has a constructive and helpful dev and user community that offers support on par with if not better than that of professional game publishers!

No luck; I tried it right after the above posting - and it did not work with a newly created entry in the group config and a newly created profile on my rented server's managing page.

I even, forgot to mention it, had deleted @ALiVE and @AliveServer folders from server and re-uploaded the EXACT working folders from my PC. Ya know, those very folders that make WarRoom access possible when joining a dedi opened on my PC.

I'm at my wits end - again...

:-( :-( :-(

Unfortunately, it's not going to be that easy this time. The IP of the rented server has NOT changed. It worked with this, according to hosting company, never changing external IP and ALiVE 1.2.2.

I had the correct IP set in the group config. But I will try and set up an entirely new server, name and all, just to be sure.

Hi Devs and helpful fellas all around the forum,

I have encountered a weird problem with mission persistence. Everything works fine when I host e.g. the ALiVE Quickstart mission or even any of my own heavily modded missions on a Dedi created with my home PC as server.

But when I try to set up a game with my rented Dedi, the logs claim that (depending which log you look at; find them at bottom of the post):

1) 14:39:43 ALIVE_SYS_DATA START PLUGIN: ["StartALiVE","ERROR","You are not authorized to access ALiVE War Room with this account. Check IP and Groupname."]

2) 14:39:48 Warning: This version of ALiVE is build for A3 version: 166.139494. The server is running version: 166.139586. Please contact your server administrator and update to the latest ALiVE release version.

It's true that the most current ARMA 3 stable build is at version 166.139586. I have this version received via steam and run it client-side. Same version is used at my rented server ofc. But using my PC as Dedi, I can connect to WarRoom and have persistence working nontheless!

So I'm not sure what to make of this errors about .exe versions mismatch, because it does not explain why I can't get WarRoom connection with the rented dedi whereas that worked finally and fully with ALiVE 1.2.2.

Here come the logs from the failed run of ALiVE Quickstart; please check them for other hints that might help find the cause of my failing WarRoom connection with the rented dedi:

https://www.dropbox.com/s/09g1aqf1thn25bp/tourist_persistence_problems_rented_dedi_ALIVE_v_1.2.3.7z?dl=0

Kind regards,

tourist

@HeroesandvillainsOS:

Since I play the majority of my ALiVE sessions either alone or with just one human buddy, I have looked for the same kind of script like you for pretty much the same reasons: I want to have AI medics doing their job and I want those tense gameplay situations where you yell: "Hold on, buddy, we're going to get you out of this alive!"

Besides ACE systems in conjunction with Bardosy's script+Davidoss improvements which I got to work, I have recently tried out alternatives to ACE because while I really like the realism oriented medical system, I don't want to be dependent on a mod that due to it's complexity and plethora of additional features might break a perfectly well running persistent ALiVE mission after the next update of either framework.

C2 is worth installation already for it's key purpose, the tactical commanding of AI - especially if you play your ALiVE missions alone. And it gets even better: C2 supports also the A3Wounding system from Psychobastard, which IMHO is the best compromise between BIS vanilla Revive and ACE sytems. But you can ofc use A3 Wounding System without/independently of C2.

A3 Wounding System:

- It works even in SP! Or MP with only 1 active player!

- It makes AI medics automatically heal their squadmates (including the player)

- It enables you to order them, even without C2, to heal any other wounded soldiers, including such miserable guys that are NOT members of your squad! (Those must've been set to playable units, though, but hey - that is a small chore to do, isn't it?)

- It offers you the possibility to set who and with what equipment is able to do the revive!

- But whatever setting you choose: ALL playable soldiers, first and foremost your AI squadmates, can temporarily stop the bleeding that A3 Wounding includes, by pressing on the wound! And you can even ORDER them to do so on any downed unit while you call in a medic! Remember, in ALiVE you can let some medics be inserted via logistics and have them join your squad temporarily...

- The ONLY real drawback is the fact that with A3Wounding active, your player unit will start to "shiver" when going closer than about 3 meters to an open fire like BIS or CUP campfires and burning metal barrels. In earlier versions of A3 Wounding System you took health damage, but that at least is fixed - just the weird "shivering" remains...

- Also if for some reason or another you are using the code snippet from AliVE WIKI that makes scripts wait for persistence initialization (most likely to be placed in the init.sqf) , you will have to perform the following circle once:

play - make a player save & then make a server save - quit client - restart server - load persistence mission&player data from WarRoom - play - enjoy!

- But after this, it works flawlessly in persistent ALiVE missions. Plus, note that the same cycle is necessary for other player-based (revive) scripts to work in a persistent ALiVE environment like Heros Survive (a primary needs + ambient temperature system for all player units working out of the box + LOTS of other features to pick, set & choose like an alternative repair system or lockable doors+quest items) or Farooq Revive; the two of them I also have tested & used & approved for ALiVE "MILSIM-Style Immersion" thoroughly...

- BTW, Farooq revive doesn't have the "campfire damages health" problem, but also is more simple and has no SP and AI automedic revive functionality.

- As you can imagine, I really really like both scripts, but A3Wounding has a tad more to offer! ;-)

Once more it's time to cite the famous quote you have in your BIS Forums sig, SavageCDN:

"IT WORKED. FINNALY. THANK YOU FOR HELPING I SEARCHED FAR AND WIDE IN THE INTERNET AND I FOUND YOU. GOD BLESS YOUR EXISTANCE MR.SAVAGE"

The server_console.log stated loud&clear that the game was (unsuccessfully) looking for the ASR AI userconfig. I had uploaded the new ASR modfolder to the rented dedi server, but had forgotten to update the userconfig folder there - so the new cfg file from the most recent ASR AI version was missing.

That was all I had to do; thanks to your suggestion to check server_console log I could find that out and played on my rented dedi the very same mission that before didn't work!

THANK YOU!!! (Topic can be marked as "Solved" ofc)

@marceldev89: thx for the first tips!

1) How can I access the server console output?

2) With the upload going via FTP and my rather slow upload speed, it might very well be possible that something's corrupted - but then again, why does the RPT referr to some ALiVE files missing and doesn't list another dependency as missing?

3) Mission design might of course play a role... I'll upload the PBO here - even if no-one wants to dl all the mods (understandable ;-) ), maybe it can be found a problem in mission.sqm, init.sqf or description.ext:

https://www.dropbox.com/s/rvsawoppaqb6u1a/BW_COIN_FATA_BETA_2.fata.pbo.7z?dl=0

@Sternum: You can combine both saving methods. I do that in the sense that I do first a player save from the ALiVE interaction menu, then a server save&exit from the menu accessible via esc key. I have full player persistence AND overall mission progress persistence that way. Works every time recently ;-)

Hi folks, as the title says I'm generally happy with my rented dedi after Tupolov and others have helped me to overcome the basic setup problems. Generally happy means I can e.g. play any official ALiVE mission with persistence and all works fine.

If, however, I fire up a few mods with, read carefully, server and client featuring the EXACT identical modline that lists the mods alphabetically, I can join and choose the mission just fine - but once I have a slot selected and click on continue in the lobby (being logged in as admin), I get a "crash to lobby" throwing me out of the loading screen at the point where you often see "waiting for host" displayed.

Here come the server client RPT hinting some ALiVE-related problems:

https://www.dropbox.com/s/0gn1syhh2inbv2n/Tourist%20Gameserver%20Bugreports.7z?dl=0

The PBO's labelled with -1 are definitely there on server and client! And have same size!

I need help...

EDIT:

I forgot to add that the very same mission CAN be started if I open a dedi on my own PC and that when playing there also the persistence works. Only, well, the FPS performance... I mean, why would I want a rented dedi after all, LOL!

I did, of course, rename the mission description in the description.ext and also renamed the PBO before trying it on the rented dedi xD...

So hopefully someone can tell me why ALiVE believes to be not there as the RPT's claim :-(

UPDATE:

Whatever the cause for this bug, I could NOT reproduce it with the ALiVE Insurgency Demo mission on Stratis. I made AAF as insurgent force, and it worked, and the roadblocks were manned by AAF, not anyone else like FIA.

So maybe it IS map related somehow... Did you test it on your map/in your mission?