Mod publishing rules

If you are reading this, you have decided to publish your mod on ForBlitz. Everything you need is here: how to present it, which files to attach, how to build the archives and which mistakes to avoid.

Mods without proper presentation, screenshots or with a wrong archive structure are sent back for changes or rejected.

How to publish a mod

1. 1Sign in and open My mods — the “Publish a mod” item in the site menu.
2. 2Press Add mod to create a draft. You can fill it in gradually; “Save draft” keeps your changes.
3. 3Fill in the title, description, game and category, upload images and archives. The checklist on the right shows what is missing.
4. 4Press Submit for moderation. While it is under review, you can take it back for editing or withdraw it.
5. 5A moderator approves the mod, sends it back with a comment or rejects it. You get a notification, and the status is always visible in “My mods”.

Once approved, the mod appears on the site. If it was sent back, fix what the moderator wrote and submit it again.

Title and description

• The title and description are required in two languages — Russian and English. Write clearly, without caps or heavy formatting, and check for typos.
• In the description, briefly explain what the mod does and what it changes in the game. Mention specifics: for example, that changes are visual only or that it conflicts with other mods.
• No need to explain installation — there are separate guides for that. What is new in a version goes into the changelog when you update the mod.
• Game — tick every game version the mod works in. If it is Lesta-only, tick only Tanks Blitz.
• Category is required. Set tags, tanks and maps whenever the mod relates to them: for example, tick the tank whose model or sound the mod changes. The administration may adjust them at its discretion.
• Authors — you are the main author and can add co-authors (up to 10 people in total). Co-authors can propose updates too.
• YouTube video — optional; it shows on the mod page.

Images

• Attach several screenshots that clearly show the changes. Up to 20 images in total.
• The recommended format is 16:9, for example 1920×1080. png, jpg, webp and gif all work.
• Mark the cover image with the star. If you pick nothing, the first image becomes the cover.
• Drag to reorder; on a phone, use the arrows.
• Avoid images that are too dark or blurry.

Proof screenshots and videos

Separately from the mod images, you can attach proof that the mod works in the game: screenshots or short videos (mp4, webm, mov, up to 50 MB). They never reach the site — only moderators see them, and they are deleted after approval.

• Show the mod on PC and on Android.
• If the mod supports both Lesta and WG, show it in both game versions on every platform.
• Optional, but without it the review takes longer and a rejection is more likely.

Mod archives

• If the archives are universal and work the same in Lesta and WG, you need two archives — for PC and for Android; do not duplicate them per client. If the files differ between clients, upload a separate archive for each.
• Up to 10 archives in total, 2 GB each.
• Formats: zip or 7z. Password-protected archives are not accepted.
• Pick the platform of every archive. The site detects it from the end of the file name — check that it is right.
• Drag to reorder archives — the mod page lists them in this order.

Name an archive with a short Latin mod name without spaces and a platform ending:

name_pc.zip           — PC
name_android.zip      — Android
name_tbfb.zip         — Android (Tanks Blitz FB)
name_pc_wg.zip        — PC (WG)
name_android_wg.zip   — Android (WG)

For a universal mod, name_pc.zip and name_android.zip are enough. Archives ending in _wg are only needed when the WG files differ.

Archive structure

The archive root is the root of the game’s Data folder. The archive should directly contain the folders that go into Data: for example, 3d, Gfx, UI, WwiseSound. The rule is the same for PC and Android.

name_pc.zip
├── 3d/
│   └── …
├── Gfx/
│   └── …
└── UI/
    └── …

Do not put the Data folder itself or wrapper folders like “mod” or “My mod v2” into the archive. Paths from older guides such as net.wargaming.wot.blitz/files/packs/ are not needed either.

name_pc.zip
└── Data/              ✗ extra Data folder
    └── 3d/

name_pc.zip
└── My mod v2/         ✗ wrapper folder
    └── Data/
        └── 3d/

Crew voice-overs

A crew voice-over archive must contain three folders — WwiseSound/ru, WwiseSound/common/ru and WwiseSound/common/ru_old, with a voice file in each:

name_pc.zip
└── WwiseSound/
    ├── ru/
    │   └── <voice file>
    └── common/
        ├── ru/
        │   └── <voice file>
        └── ru_old/
            └── <voice file>

Updating a mod

1. 1Open your mod on the site and press Update mod — or find it in “My mods”. The author and co-authors can propose updates.
2. 2Change what you need: text, images, archives. Old files can be marked for removal — they are only removed after approval.
3. 3Fill in What changed in both languages — it goes into the mod’s changelog.
4. 4Submit it for moderation. While the update is under review, the current version stays on the site.

A mod can have only one update in progress: if one is already started, the button opens it instead of creating another.

Rules

1. 1Do not use other people’s work without the author’s permission.
2. 2We do not accept mods built with mod constructors (BlitzInfo, BlitzHata and the like).
3. 3Do not upload malicious or suspicious files. Executables (.exe, .bat, .dll and the like) in a mod archive are grounds for rejection.
4. 4Test the mod before publishing so it has no bugs or crashes.
5. 5Violations can get you banned from publishing mods.

Finally

Following these rules speeds up the review and makes your mod more appealing to players. Happy publishing and modding!