[bomb3rman]

Hey guys, due to time shortage my plans of releasing a campaign have been interrupted... But I think I'm at the right point in the campaign to split it into two different parts (~ 20 missions are done and there's even some kind of Cliffhanger...).

Iirc, with one of the last updates, a new kind of variable was introduced that let's you carry over the information of variables from one campaign to another. So am I right if I just need to copy via Sexp all the information (money available, ships, ammunition available and weapons gathered) during the campaign into these new variables, so they can be used by the pilot profile when starting the 2nd part later on?

I hope you get what I'm talking about... Since the time shortage won't go away any time soon, it would be a shame to just let these missions rot on the hdd... The story works well until here and all the missions are nearly complete.

Greatings!

[wookieejedi]

Yes that is correct. In the variable dialog box there is a check box for eternal variables, which will carry between campaigns.

[Nightmare]

Wouldn't it be possible to save them as txts too? I think quite many use the 1-player-per-campaign rule, so it's quite likely that the progress won't be available if the rest will be released a couple years later.

[wookieejedi]

It's certainly possible to save as text (I've used that method before), but that requires a good amount of scripting knowledge and I wouldn't recommend that for this situation. I would imagine the player could just play through the first release again once the second release comes out.   

[Nightmare]

Sure (and I'm 90+% sure that this would be the best way to go).

Wouldn't it be possible to safe the stats via the checkpoint-script, than load them from another mission?

[wookieejedi]

Sure (and I'm 90+% sure that this would be the best way to go).

Wouldn't it be possible to safe the stats via the checkpoint-script, than load them from another mission?

Yeah, that could certainly be another route too, since the check-point script writes it's own save file

[0rph3u5]

Iirc, with one of the last updates, a new kind of variable was introduced that let's you carry over the information of variables from one campaign to another.

The feature existed since retail but the original descriptors were a bit misleading - the rework made it 99 percent more usable (give eternal thanks to the great Coder Gods of the SCP for that).

Note that any given mission can only referrence 258 (please verify) variables total - and I don't know what you are doing but I have noticed them piling up like crazy in campaigns with persistence

And there is a limit on the number of eternal variables, which I don't recall...

[karajorma]

I would strongly advise prefixing any eternal variables with the initials for your campaign. That way you don't get a situation where, for instance, a Blue Planet Hull-Strength variable gets overwritten by one from Between the Ashes.

[bomb3rman]

@0rph3u5

I think this won't be a problem since there are only around 50 variables until now....

@karajorma

The variables have their own names, so there won't be any kind of collision I guess...

But this sounds all very encouraging, thx for the replies. So expect the launch of my stuff around January, I guess 

[Cyborg17]

Just as a note, having separate pilots for separate campaigns or mods is no longer necessary since campaigns have independent saves now.  I just played through Diaspora, a Total Conversion, with the pilot I use for every other campaign.

[Nightmare]

Oh that's certainly nice. I actually already did before the new pilot code came, with err, bad results.

[AdmiralRalwood]

Iirc, with one of the last updates, a new kind of variable was introduced that let's you carry over the information of variables from one campaign to another.

The feature existed since retail but the original descriptors were a bit misleading - the rework made it 99 percent more usable (give eternal thanks to the great Coder Gods of the SCP for that).

Misleading descriptors I'll grant you, but it's not so much it existed since retail as everyone thought it existed since retail, because of the aforementioned misleading descriptors; no matter where the variable was stored, there was no way to share it between two campaigns. The fact that you eventually could in FSO was technically a bug.

[karajorma]

Well persistence itself is an SCP feature not a retail one. But it's a very old SCP feature. So it had been around a long time before the bug occurred.