Publishing guidelines

These guidelines apply to any scene you publish that uses Voxta. They keep the community safe, the scenes high-quality, and your release process predictable.

Content rules (non-negotiable)

• Illegal content — none. No minors, no non-consensual acts, no content unlawful in the US, your country of residence, or any demographic your scene targets.
• Hateful / discriminatory speech — none. No content promoting hate or discrimination on the basis of race, ethnicity, religion, gender, sexual orientation, disability, or any other characteristic.
• Licensing — only ship assets you have the rights to. This includes likenesses, voices, textures, and other copyrighted material.
• Misleading content — don't oversell what the AI can do. Don't manipulate users into thinking the AI is more capable or more aware than it is.

Quality bar

• Polish the AI integration. Test the conversation flow, the triggers, the lipsync, the animations. Broken triggers and bad transitions reflect on Voxta as much as on you.
• Avoid low-effort or repetitive characters. A character with a one-sentence personality and stock animations isn't worth shipping.

Characters

• Character card — include a detailed background and personality. Voxta lives or dies on character depth.
• Portrait — image must be in 2:3 format, original or properly licensed.
• Voice — specify the TTS service and exact voice used. If possible, ship the voice file with the scene assets.

VaM Hub release rules

• Category — Voxta-required scenes go in Free Voxta Scenes or Paid Voxta Scenes. Scenes where Voxta is optional (e.g. you provide a fallback) can use the regular categories.
• Voxta tag — add the voxta tag so users searching across categories find you.
• Credit — state that the scene is powered by Voxta AI. Link to the Voxta Patreon.
• Instructions — give users clear setup steps and call out any special interactions in your scene.

Packaging

• Bundle all the things. Characters, scenarios, memory books — package them inside the .var. See VAR Packages for the full bundling guide.
• Reference the plugin, don't ship it. Add the Voxta plugin as a Hub reference in Package Builder (Voxta plugin Hub page) — never copy the plugin files into your .var.

After publishing

• Test on a clean install. The only reliable test is: delete the bundled resources from your own server, then open the scene from AddonPackages (not from loose Saves). See the round-trip test in the VAR Packages guide.
• Update as Voxta evolves. Voxta is under active development and breaking changes happen. Keep your scene current.
• Communicate with your users. Note plugin versions you've tested against; post update notes when you rev.

Legal terms

Follow the terms of every dependency:

• Virt-A-Mate terms
• Voxta terms
• Plus any third-party assets you've licensed.