Scam With Your Friends supports custom personalities through JSON files, but a verified current Caller JSON schema is not available in this guide. There is no supported list of required keys, file location, accepted value types, or complete import procedure to copy.
Do not treat a plausible-looking JSON example as a working caller template. Valid JSON syntax and a caller file the game accepts are two different checks. The safest useful reference is a file actually produced or accepted by the current game, when you have access to one.
Start from the current caller interface
Character Creator now opens directly into creating a caller. Existing callers are edited through Daily Callers. Those are the confirmed current entry points following Hotfix 2.
Use the interface to understand what you are editing before constructing an external file. A personality description, a voice reference, and a caller's selection state are not interchangeable simply because they may all appear in a custom-content workflow.
If your current game exposes an existing caller file or offers an export control, examine that actual output as a reference. This is conditional advice: no export button, export location, or exact sequence is verified here. Do not assume a file can be exported just because another modding system provides that feature.
Earlier gameplay interface shown for orientation; current caller controls may differ.
Separate syntax from the game's schema
| Check | What it tells you | What it cannot prove |
|---|---|---|
| JSON syntax check | Whether text follows the JSON grammar | Whether the game recognizes its fields |
| Match against a verified current caller structure | Whether your fields follow that known structure | Whether every value or external asset will work |
| Load the caller in the game | Whether that specific file is accepted in that situation | Compatibility with every future version or other caller |
General JSON syntax uses quoted property names, correctly paired brackets, and appropriate separators. A plain JSON parser can report syntax errors such as an unmatched bracket. It cannot know the game's undocumented caller requirements merely from the file extension.
For example, fixing a missing comma only addresses that syntax error. It does not prove that a field name is supported or that a value has the meaning you intended. Avoid “repairs” that add guessed keys just to make a file resemble a generic character profile.
Preserve a real reference before making changes
If you have a caller file already accepted by your current build, keep an unchanged copy before editing. Change a small part at a time so you can identify which change preceded a new error.
This is general editing practice, not evidence of a particular save directory, naming convention, or supported mod-folder hierarchy. Do not move the file into a guessed path based on instructions for a different game.
Keep the original property names and types unless you have a verified reason to change them. Renaming a key to something more readable can stop an application recognizing it even when the file remains perfectly valid JSON.
The same caution applies to values. A string that looks like a personality prompt may have constraints that are not visible from the JSON grammar alone. No maximum length, special placeholder syntax, or guaranteed behavior for a particular personality instruction is established here.
Keep voice assets separate from personality format
The game also supports voice cloning through WAV files. That confirms an audio format category; it does not establish how a personality JSON points to a voice, whether a path is relative, or which field would contain the reference.
Do not insert a guessed voice filename into a guessed JSON key. A separate Localize Voice button is also no longer part of the current documented interface, so older instructions using that button cannot establish today's file structure.
Use the controls and file relationships actually exposed by your current game. This guide does not provide a sample JSON because the required structure has not been verified.
Distinguish a file error from a caller-selection error
Launch fixes addressed uploaded custom callers losing their Daily Callers connection after restarting. That problem concerns the relationship between uploaded content and the caller selection; it does not establish that the JSON itself is malformed.
Workshop upload failures are another separate category. A fix addressed stuck uploads blocking other caller uploads. Changing brackets or rewriting a personality is not an established solution to that upload condition.
When reporting a problem, include the exact error and the point at which it occurs: parsing a file, opening a caller, loading a voice, appearing in Daily Callers, or uploading to Workshop. Remove private material before sharing a file publicly, and retain the original so that an attempted repair can be reversed.
Do not rely on an unverified game-specific validator
A tool can truthfully validate basic JSON grammar without understanding Scam With Your Friends. To claim that it validates caller compatibility, it would need the real current schema and the relevant game rules.
No such schema has been established here. A green “valid JSON” result is therefore a syntax result, not permission to assume the caller will appear, speak correctly, or upload successfully. Use an actual current-game caller file and the game's own response as the reference for the next step.