Sure if you want!

What I was planning on doing was loading the updated ALiVE download Spyder linked: https://www.dropbox.com/s/w43u8v3dy7z8864/ALiVE_testVersion.zip?dl=0

And then running the profile counter:

https://gist.github.com/SpyderBlack723/87b4552ed9da8ee298ff21289ad9d6e1

And look to see if the profiles are relatively consistent in numbers upon mission restarts.

Then I was going to try adding a "mission complete" trigger because that isn't working on the released ALiVE version either (not with the mods I use, at least. It did work before 1.60 but not now).

Trigger Condition: if (isServer) then {count ([getposATL thisTrigger, 15000, ["EAST","entity"]] call ALIVE_fnc_getNearProfiles) == 0 && {count ([getposATL thisTrigger, 15000, ["EAST","vehicle"]] call ALIVE_fnc_getNearProfiles) == 0}} else {false};

Trigger Activation: if (isServer) then { ["end1","BIS_fnc_endMission",true,true] call BIS_fnc_MP};

@SpyderBlack723

I'm sure you don't want to hear this, but the civilian interaction module in Spyder Addons is causing the \author is not a value error and also triggering the mission complete trigger.

It's odd. I've been building a vanilla test mission working my way up. I tried the Ambience module and that was fine. Once I reached the Civilian Interaction module the error popped up and the trigger fired.

Now whether or not it's responsible for my larger issues I have no clue. I'm testing now. But figured I'd pass along what I'm already seeing with that one module.

I'm still leaning towards the error itself somehow firing the trigger (it never fires when the author error isn't present) and not the mod but I'm still working on it.

Yes I know, since I can't repack the pbo I can't fix that error for that moduke. The rest are good to go.

The error in general, regardless of which mod is causing it (some CBA objects shoot this error too, such as burning campfires) definitely interferes with the mission complete trigger. That's 100% confirmed as I can duplicate that every time the error pops up.

This error also causes an 'extra load screen' when an ALiVE mission starts. That I can confirm too.

But for my larger issues? Nah I don't see it. I can't duplicate that. Because of course I can't. :( So I now agree this error is relatively harmless, unless on the off chance having lots of objects and your civ module all shooting this error simultaneously is the cause. I like my CBA objects. :)

EDIT: ^^^

Removing every object from CBA with the error (which was one journalist and one burning fireplace), removing the civilian interaction module from Spyder Addons and using the ALiVE test version has fixed my units spawning issue.

Well I'll be damned. Having multiple things causing this author error simultaneously was breaking ALiVE's initialization. The error I guess can be harmful if happening multiple times all at once.

CBA has already fixed the issue for their next release.

That's great. Thanks for the update on that.

BIS should really allow for the old way to be valid. For instance, FATA itself causes this error by just loading the map and FATA isn't being updated anymore.

It's sucks they didn't allow the old way to be acceptable. This error can really mess up ALiVE and obviously triggers under certain circumstances.

@DLEGION

I detailed the issue in this post. The ALiVE update only sort of fixes the problem.

@marceldev89

I just wanted to update you. So I made a vanilla mission on Stratis, slowly adding my mods and scripts in one by one until I could duplicate my issue with the large discrepancy of profile spawns on mission start.

Long story short, once I introduced this \author is not a value error in, I was able to consistently repro the problem.

But here's the catch. I could only duplicate it when more than one object or mod that has this error was present.

Example, Spyder Addons has this error. With just that being used the profile initialization was fine. So I added a CBA object (which has this error too) and BAM, the problems started.

So I messed around for a while trying to see if it was the specific object and over and over, this profile problem would only occur if 2 or more instances of \author is not a value was present. So if someone is using two mods that both have this error, they will very likely encounter issues with ALiVE. I spent a good amount of time with this and feel pretty confident what I'm seeing is accurate.

Also, even one instance of this error is enough to delay ALiVE's initialization. Example: I use a trigger to detect once all East profiles are dead to give me a "mission complete" screen. Anytime this error occurs, the trigger fires on mission start because the trigger is beating ALiVE to the punch. Without this author error, the trigger works and always has worked in the past.

Anyway, I figured you guys should be aware of this, in the event someone else asks or sees this thread.

No

@marceldev89 suggested I try running the missions on a dedicated server to see if the issues still occur because apparently, the author is not a value pop-up only shows up in SP.

I have not tested it but it's worth a shot.

Otherwise, we just need to be patient.

What I did for now is remove any object (such as CBA objects) and modules (such as Spyder's Civilian Interaction) from my missions that cause the error so as of right now, I'm ok(ish) if I use the test version of ALiVE. But for the stuff you absolutely NEED, no, I can't think of anything we can do but play the waiting game.

You need to be using the dev version of ALiVE for this to go away. The released version still has this error.