- Voxalike publish Dub Pack workflow: build assets, package the mod, test a full session, then release it on the Workshop.
- Required assets: scene video, character roles, dialogue captions, line timestamps, reference audio, metadata, and cover art.
- Lock timing early: finalize the scene video before setting timestamps, or every line can drift.
- Test before release: run a complete Solo session so every line, role, and media file loads correctly.
- After launch: push updates through the Workshop so players can reinstall the latest version.
What a Dub Pack Contains Before You Publish
A Dub Pack is the playable content unit at the center of Voxalike, the browser dubbing party game from yours1 that runs directly at voxalike.com and on its official itch.io page. Each pack supplies the scene, characters, roles, and dialogue that a session runs on, whether one performer records everything in Solo or a full room splits the lines. Before starting the Voxalike publish Dub Pack workflow, confirm your project includes every component the game expects to load, because a single missing piece can break sessions after release.
| Component | What It Provides | Publish Impact |
|---|---|---|
| Scene video | The visual scene players dub over | Must stay in sync with dialogue timing |
| Character roles | Defines who speaks each line | Drives Solo and multiplayer line assignment |
| Dialogue and captions | Text players read and perform | Should closely match the spoken lines |
| Line timestamps | Start and end timing per line | Controls when each line becomes active |
| Reference line audio | Original dialogue playback | Helps players hear how the line fits |
| Metadata and cover art | Title and Workshop identity | Required for discovery and listings |
| Backing track (optional) | Music under performances | Must remain synchronized with the scene |
Solo Sessions
- One performer records every role
- Best format for testing a new pack
- Simplest way to verify line flow
Co-op Rooms
- Up to 12 players share the dub
- Lines rotate via Round Robin or Claim Mode
- Packs need enough roles for the group
PVP Rooms
- Up to 8 players compete
- Competitive results on performances
- Works best with clearly split roles
When planning a pack, decide early whether it targets Solo performers, small friend groups, or large Co-op rooms of up to 12. Role count is the single biggest factor in whether a published pack works for a given session size.
Prepare Every Asset Before Packaging
Publishing problems are usually preparation problems. Finalize each asset in order, because later assets depend on earlier ones: timestamps depend on the final video cut, captions depend on finalized dialogue, and the package structure depends on all media being ready. Treat asset preparation as its own stage instead of something you fix during packaging.
| Asset | Finalize First | Watch Out For |
|---|---|---|
| Scene video | Lock duration before any timing work | Re-editing shifts every timestamp |
| Character roles | Consistent names and identifiers | Duplicate or vague role references |
| Dialogue text | Lines paired with the correct character | Captions players cannot read in time |
| Line timestamps | Start and end points for every line | Drift against the final video |
| Reference audio | Files matched to the correct lines | Formats the browser cannot play |
| Metadata and cover | Title and artwork completed | Missing covers weaken Workshop listings |
| Backing track | Optional, synced to the scene | Music overpowering recorded takes |
Never set timestamps against a rough cut. If the scene video changes length after timing work, every line can fire early or late, and you will re-time the entire dialogue list before you can publish.
Publish a Dub Pack Step-by-Step
The creation flow mirrors the official Dub Mod maker guide: prepare media, define the playable data, package everything in the required structure, test, then release. Follow these five stages in order and the publishing step becomes a formality instead of a troubleshooting session.
Prepare the Scene Video
Choose the scene players will dub and treat it as the main video asset of the pack. Lock the final duration before moving on, because every timestamp you set later must match this exact cut of the scene.
Define Roles, Dialogue, and Captions
Create a role for every speaking character, then assign each dialogue line to the correct role. Write captions that closely match the spoken dialogue so players can read and record directly from the game without guessing.
Set Timestamps and Reference Audio
Give every line start and end timing that matches its position in the scene. Attach reference line audio in a browser-compatible format so players can hear how the original delivery fits before recording their own take.
Add Metadata, Cover Art, and Optional Music
Fill in the pack title and package metadata that identify it inside Voxalike and on the Workshop, and add a cover image that represents the scene. If the scene benefits from music, include a synchronized backing track that stays underneath the performances.
Assemble, Test, and Publish
Place the video, audio, captions, timestamps, character data, metadata, and artwork into the required Dub Mod package structure. Run a full test session so every line, role, and media file loads correctly, then publish the tested package to the Workshop with complete metadata.
A pack that passes one complete Solo test session—every line triggers on time, every role records, every audio file plays—is ready for the Workshop. Publish with finished metadata and cover artwork so the listing looks complete from day one.
Test Your Pack Before It Goes Live
Testing is the stage that protects your Workshop rating. A pack that reaches the Workshop with broken lines or missing audio collects negative feedback quickly, and first impressions are hard to recover. Work through this checklist in a real session, not just in the editor.
Pre-Publish Testing Checklist:
- Scene video plays through without errors
- Every dialogue line is assigned to a character
- Timestamps align with the final video cut
- Reference audio loads for each line
- Metadata and cover art are complete
- One full Solo session completed successfully
| Symptom | Likely Cause | Fix |
|---|---|---|
| A line never appears | Missing or incorrect timestamp | Re-check start and end timing |
| Wrong player records a line | Line assigned to the wrong role | Correct the character assignment |
| No reference audio plays | Missing file or unsupported format | Replace with browser-compatible audio |
| Scene and dialogue drift apart | Video re-edited after timing | Re-time lines against the final cut |
| Pack fails to load | Broken package structure | Rebuild against the required structure |
| Title or cover missing | Incomplete metadata | Fill all Workshop-facing fields |
Editor previews can hide problems that appear in real sessions. Record at least one full take as a player would, including retries, so you catch timing and audio issues before strangers find them.
After Publishing: Updates, Multiplayer, and Discovery
Once your pack is live on the Workshop, three systems determine its success: how players install it, how it behaves in multiplayer rooms, and how the community rates it. Understanding the difference between subscriptions and installations matters most, because subscribing to your pack does not make it playable on its own.
| Aspect | Workshop Subscription | Browser Installation |
|---|---|---|
| Tied to | Your Voxalike account | The browser you are using |
| Purpose | Tracks content you want to reuse | Makes a pack actually playable |
| Another device | Follows the account | Requires a fresh local install |
| New versions | Marks updated content available | Reinstall to match the latest release |
In multiplayer, the host selects the Dub Mod for the room, and every participant needs that mod available locally before the session runs correctly. Recent versions of the game streamline this by automatically installing the host's mod for joining players, but you should still note in your pack description which player counts it supports. Workshop ratings and download activity then drive how easily new players discover your content, which is another reason pre-publish testing pays off. Players who run into installation trouble will usually consult the Workshop mods install guide, so keep your metadata accurate.
When you push an update, say so in the pack description. Subscribers see the newer version on the Workshop, but each browser still needs its own updated local copy, and clear version notes help rooms avoid mixed-version errors.
Dub Pack Publishing FAQ
Most publishing questions come down to one of four situations covered below. If your issue involves scoring visuals rather than scene content, you likely want a Judge Mod instead of a Dub Pack.
Q: What files do I need to publish a Dub Pack?
A finalized scene video, character roles, dialogue text with captions, per-line timestamps, reference line audio in a browser-compatible format, package metadata, and a cover image. A backing track is optional. Follow the official maker guide at voxalike.com/guide/make-dub-mods for the required package structure before publishing.
Q: Do other players need to install my pack to use it?
Yes. Workshop content is installed browser-locally. In multiplayer, the host selects the Dub Mod and every player needs that mod available locally before the session runs correctly. Recent versions of the game can automatically install the host's mod for joining players to reduce setup friction.
Q: Can I update a Dub Pack after publishing it?
Yes. When you release a new version on the Workshop, players update or reinstall their local copy so installed content matches the current release. A subscription identifies the content on an account, but each browser still needs its own updated installation.
Q: Is publishing a Dub Pack the same as making a Judge Mod?
No. Dub Packs define the playable scene, roles, and dialogue that players perform. Judge Mods only customize the result screen—judge artwork, names, score labels, feedback lines, and reaction sounds—and do not change how Voxalike scores performances.