Cvar Replacement?

[TXTX]

Is there a way to save strings and data that will be saved in game without using cvars? Using too many of them will end up crashing the game and I want to know if there's a workaround.

[Apeirogon]

Everything saves in save. Well, almost everything, but those that not saves are very specific edge cases.
Or you mean saves between different game sessions?

[TXTX]

Everything saves in save. Well, almost everything, but those that not saves are very specific edge cases.
Or you mean saves between different game sessions?

Like if you decide to save a game but come back to it later. Not sure if everything saves that way.
For example having a string saved to a static event handler or something.

[3saster]

Like if you decide to save a game but come back to it later. Not sure if everything saves that way.
For example having a string saved to a static event handler or something.

In this particular case, the string saved in the static event handler is NOT saved, since the static event handlers are created on startup, and exist outside the scope of the playsim.

Is there a way to save strings and data that will be saved in game without using cvars? Using too many of them will end up crashing the game and I want to know if there's a workaround.

Anything that is part of the playsim (actors, etc.) will have their properties serialized and saved into the savegames. Thus, if, say, an actor stores some data on themselves, when the game is reloaded from a save, that data (at the point of the save) will be restored. If, however, you want persistant NON-playsim data (for example, a flag that says whether you beat the final boss before), CVARs are currently your only option. There have been discussions about this being implemented (can't find them atm), but I don't believe it will happen anytime soon. For now, you must rely on CVARs for persistant non-playsim data.

[TXTX]

In this particular case, the string saved in the static event handler is NOT saved, since the static event handlers are created on startup, and exist outside the scope of the playsim.

Anything that is part of the playsim (actors, etc.) will have their properties serialized and saved into the savegames. Thus, if, say, an actor stores some data on themselves, when the game is reloaded from a save, that data (at the point of the save) will be restored. If, however, you want persistant NON-playsim data (for example, a flag that says whether you beat the final boss before), CVARs are currently your only option. There have been discussions about this being implemented (can't find them atm), but I don't believe it will happen anytime soon. For now, you must rely on CVARs for persistant non-playsim data.

Thank you for the helpful reply. Suppose I can't do much about it unless I find some hacky way of implementing for now.

[gwHero]

Is there a way to save strings and data that will be saved in game without using cvars? Using too many of them will end up crashing the game and I want to know if there's a workaround.

There are global variables https://zdoom.org/wiki/ZScript_global_variables

[TXTX]

There are global variables https://zdoom.org/wiki/ZScript_global_variables

I'll have to take a look at that. Should be helpful.