The Choicer Voicer ships as close to an empty shell as a game can get — practically everything you actually see and hear comes from content packs you install yourself. Once you understand the underlying folder structure, though, every pack type follows a similar, predictable pattern. Here’s the full map.
Inside the game’s local data directory sits a set of dedicated folders, each holding one type of content pack. Every folder is reachable directly from the main menu, so you never need to dig through your operating system’s file browser to find them manually. The main content folders are:
packs_voice — voice packs and dub packs (dub packs are simply an upgraded voice pack, so they share the same folder)packs_player — contestant (player) packs, covering the character you play aspacks_judges — judge packs, covering the five-judge panelpacks_studio — studio packs, covering the 3D environment the show is staged inpacks_chatter — chatter packs, the Twitch-exclusive audio-by-keyword content typeHost packs and menu packs are also confirmed as their own customizable content types, though a dedicated official folder-and-file breakdown for those two hasn’t been published yet.
Regardless of pack type, the pattern is always the same: create (or drop in) a subfolder inside the correct packs_ directory, and that subfolder’s name becomes the pack’s default display name in-game. The game reads the folder’s contents at the pack-selection screen and only fully validates individual files — flagging things like corrupted or oversized clips — once it actually generates a batch for gameplay, not at the moment you browse the list.
A few structural rules repeat across almost every content pack type in the game:
player; a judge’s images must be named judge1 through judge5; a dub pack’s video must be named dub_video. Get the filename wrong and the game won’t find the asset._pack_filler_image as a fallback image for a voice pack, or _backing_track as the ambient audio underneath a dub recording.play_voices_with_blips off in a judge pack’s config JSON.| Pack Type | Folder | Core Purpose |
|---|---|---|
| Voice Pack | packs_voice |
The audio clips players perform in the standard studio |
| Dub Pack | packs_voice |
An upgraded voice pack with an OGV video and timestamps, used in Dub Mode |
| Contestant Pack | packs_player |
The character the player performs as |
| Judge Pack | packs_judges |
The five-judge panel’s look and reactions |
| Studio Pack | packs_studio |
The 3D environment, music, and score-screen visuals |
| Chatter Pack | packs_chatter |
Twitch-only, viewer keyword-triggered audio |
| Host Pack | Not yet officially documented | The show’s emcee character and dialog |
| Menu Pack | Not yet officially documented | Menu theming and music |
Because every pack type is self-contained in its own folder with its own expected filenames, you can freely mix and match packs from different creators — a voice pack from one source, a judge pack from another, a studio pack from a third — as long as each one is placed in its correct folder. This is exactly how the community’s most popular themed bundles work: a matching voice pack, judge pack, contestant pack, and studio pack, each built to the same folder conventions but distributed and installed independently.
Since pack folders map directly to display names, avoid nesting one pack’s folder inside another by accident during extraction — a common issue is a ZIP file unpacking into a folder that itself contains another folder with the same name, which stops the game from recognizing the pack correctly. Always confirm the actual audio and metadata files sit directly inside the top-level pack folder before dropping it into the matching packs_ directory.