ZDoom

Well, some people seem to be intent of abusing such stuff.

Well, too bad. Since its use is actually rather limited I might as well outright 'no' it and stop this nonsense. Soulpriestess is correct when saying that loading a savegame should be transparent to the game simulation.

Ok.

Variable: sv_CallLoadACS

true or false, default ... well that would be up in the air. But it should definitely be menu settable.

But setting this to false would disable any loadgame script. And it could be saved on a per-mod basis. Game creator's setting of course would override everyone else's, especially since it's a sv_ variable. And setting it before loading a game overrides the savegame's setting (in fact, it wouldn't even be saved into the game).

This would completely mitigate any potential for abuse of this feature.

[quote="Worst"]Imo this feature would only really be needed for some [url=http://forum.zdoom.org/viewtopic.php?f=18&t=21776]special gameplay experiments[/url] :P
[code]Script 1 LOADGAME
{
Teleport(lastCheckpoint);
}[/code][/quote]
I contemplated how possible this would be. Depending on the mod, it could either be as simple as this (like use for a jump maze), or be rather complex beyond the point of any [i]sane [/i]person realistically doing it (say, a mod based off Zen Dynamics).

Bind F7 "quicksave; quickload"

Script 1 LOADGAME
{
  Teleport(lastCheckpoint);
}

but just what kind of information do you need to show ONLY when loading a game, but not at any point in the game?

If you can do it with a button, which does not require you to save at all, why not go for it? I dont really see any reason why you couldn't show that information at anypoint, but rather only when loading.. This feature imo would make loading savegames a part of the game in a way or another. Whatever you do there it's only available when loading the game. :?

If it would be anything important, this would indeed force the player to save the game, whenever they want to see this crucial information..

[code]Bind F7 "quicksave; quickload"[/code] I'd have to use a bind like this whenever i'd want to see this important information.. rather than just pressing some key that pukes a script that shows the information etc. And if the information is not important, I dont think you really need to show it when loading a savegame. :|


Imo this feature would only really be needed for some [url=http://forum.zdoom.org/viewtopic.php?f=18&t=21776]special gameplay experiments[/url] :P
[code]Script 1 LOADGAME
{
Teleport(lastCheckpoint);
}[/code]

The mod designer would, in that case, do well to provide a button for the stats to be shown during the game as well. Rejecting a feature suggestion because it might lead to poor design decisions on the part of a modder using it is grounds for rejecting the entire ZDoom feature set, as far as I'm concerned.

What's the need to have a script run on loadgame? The first post mentions that it could be used to remind the player of stats or objectives. Why not just make a button do that? I can imagine a player who wanted to see that information have to save the game and reload it just to trigger the script if this plan was followed.

I fail. I missed the savegame part.

You sound a lot like you haven't actually read this thread. 8-)

This sounds a lot like LOADACS.

I think its like one of those things where you can abuse it, but as soon as you did, it would make your mod [i]extremely unpopular[/i]. Under no circumstances would I think anybody would uses this to kill a player or anything that would dramatically change the game in any-way because you loaded your game.

Not possible.

I think the LOADGAME block should be restricted - to only re-enable HUD items, or other uses that someone can think of. No variables that "track" the fact the game has just been loaded would be saved, and any other attempted functions would be blocked. The code would be audited by the loadgame code itself, so that you don't have to go through each and every ACS function to detect whether the game has just been loaded. Similar to the method used by the KEYCONF code, which checks each and every command and only allows certain commands to pass.

^? isn't made significantly harder by this script, no. :P

Indeed, it makes sense.

Ironically, however, if someone did implement a script such as posted above, it would be harder for an end user to circumvent compared to a mapinfo option for no saving.

script 1 LOADGAME {
  print(s:"Trying to load your saved game, huh? I don't think so!");
  Thing_Destroy(playerTID,1);
  Thing_Damage(playerTID, 10000, 0); // just in case you have God mode.
}

[code]script 1 LOADGAME {
print(s:"Trying to load your saved game, huh? I don't think so!");
Thing_Destroy(playerTID,1);
Thing_Damage(playerTID, 10000, 0); // just in case you have God mode.
}[/code]

Sarcasm aside, I do support this feature, even if it can be abused like I just pointed out.