Simple question:
Are there any downsides or security issues with setting a character’s archivable property to true? I need to use viewport frames instead of thumbnails since they’re somewhat unreliable and the prompt system already relies on viewport frames.
Not really, the only thing that might cause issues are if you are using the AssetService:SavePlace method because then the Character model will get saved into the place as well.
Adding onto what @CodeJared said,
Archivable, if set to true, just means that the method of instance :Clone() can be called on the object. All parts and instances will usually be Archivable by default.
There are no performance or security issues, other than perhaps an exploiter saving the character without XML.
But that doesn’t matter xd