MakeScreenShot()

[Matt]

For those of us whose screenshot folders are kinda tucked away where we don't normally look, what is there to stop someone from maliciously (or accidentally) creating a loop that floods someone's drive with useless* data?

*Or worse - disguise a map as something legit, but it contains a script that shows a bunch of things and screenshots them all, of a nature one really, really would rather not have files of on their hard drive...

[phantombeta]

The fact that it's requires you to set an opt-in CVar. It only does anything if the enablescriptscreenshot CVar is set to true.

[Matt]

But what if:
1. someone opts in (or, if this is noarchive, gets used to opting in as a matter of course) because
2. 999 out of 1000 wads use this feature reasonably and in good faith, but
3. 1, unbeknownst to them, doesn't

[Kinsie]

I don't even think one wad uses MakeScreenshot(), let alone 1000. And even then, I'm pretty sure JPL is the only person who's even expressed interest in using it, and he's not exactly the Terrywad kind.

Sorry, you'll probably have to find another excuse to give to your significant other when they find your folder of "special" Beetle Bailey fanart.

[NeuralStunner]

I would think a simple internal cooldown of some kind would solve this issue. I can see an edge case for 5-10 consecutive captures for a "burst photo" type of deal, but beyond that, there's really not a lot of reason to be constantly producing shots even for legitimate uses.