All workSetonix
Ultimate TNT key art

Add-on · with Novasoft

UltimateTNT

About 60 craftable TNT, each with three levels. I took it through Marketplace review and directed the redesigns that got it approved.

Role
Producer
Studio
Novasoft
Focus
Marketplace review
Platform
Minecraft Bedrock Marketplace
01

Overview

About 60 kinds of TNT, each with three levels.

Ultimate TNT is a scripted TNT add-on built with Novasoft (scripts in TypeScript). There are four groups: Destruction, Combat, Utility and Gimmick. Every TNT can be upgraded twice, so each one has three levels.

My job was producing, not coding: Novasoft's developers built it, and I got it through Marketplace review. The first submission came back with flags. I worked through the feedback with the team and directed redesigns of four TNT until the pack was approved.

4TNT groups
3Levels per TNT
4TNT redesigned in review
v0.6.1Build sent to review
02

The roster

Every TNT has to do something different.

The main rule was that a player can tell what a TNT does from its name, its look and what happens when it goes off. Pick a group, then a TNT, to see its effect and how its blast grows from level to level.

03

Level system

Learn the recipe once, use it everywhere.

Level 1 is a block you place like vanilla TNT. Levels 2 and 3 are items you place on any surface. The upgrade recipe never changes: put the same ingredients around the previous level. Once you've upgraded one TNT, you know how to upgrade all of them.

8 Dirt + TNT→ L1 · r10
8 Dirt + L1→ L2 · r20
8 Dirt + L2→ L3 · r30

Example: Dirt TNT. Radius doubles at Level 2 and triples at Level 3.

Exceptions I kept on purpose

Giant

9 TNT in a 3×3 grid, then 9 of the previous level.

Ultimate

Level 1 needs a Mega TNT in the middle, not vanilla TNT.

Overload

Gunpowder at Level 1, Blaze Powder at Levels 2 and 3.

04

Marketplace review

Turning reviewer flags into better TNT.

Microsoft's reviewers flagged TNT that gave out too much, too easily. Golden Path flags are about rewards that skip normal progression, like random loot from one cheap block. Resource balance flags are about giving more than the recipe costs.

Submitted

Build v0.6.1 goes to Marketplace review.

Flags

Golden PathLucky, Battle
Resource balanceHarvest

Redesign

Lucky, Harvest, Witch's Brew and Radiation Cloud reworked, not just tweaked.

Approved

Pack approved for the Marketplace.

The fixes weren't always obvious. For Harvest, the reviewers suggested making the recipe cost mid or late game materials, so it pays out only once you've earned it. My rule was simple: if a TNT is flagged, we redesign it. We don't ship it as it was and hope.

05

Configurable TNT

Two TNT that players set up themselves.

Clockwork and Tunnel TNT have settings. Right-click Clockwork to set its fuse. The longer you wait, the bigger the blast. Tunnel lets you set how deep and how wide it digs.

20s

Illustration of the rule, not in-game values.

06

Under the hood

Built to stay stable at a 70-block radius.

The biggest TNT clears a huge area, so performance was part of the brief. Novasoft's developers built the scripts in TypeScript, one feature per file, plus an internal chunk-loader entity. I set the performance target and tested against it; I didn't write the code.

Presentation

Custom block models, textures and sounds for each TNT, plus 15 particle groups, from disco lights to a mushroom cloud.

Onboarding

A Spawn Guide is handed out on first join, with its own structure at the player's feet. Fuse Sticks and Fuse Bundles light TNT from a distance.

07

Thought process

  1. 01

    One recipe rule for every TNT

    The same ingredients around the previous level. Players learn it once and can upgrade anything.

  2. 02

    Distinct beats bigger

    With this many TNT, each one needed its own effect and look, not just a larger explosion.

  3. 03

    Redesign flagged TNT

    Changing a number to slip past review just gets flagged again. We changed what Lucky, Harvest, Witch's Brew and Radiation Cloud do.

  4. 04

    Write it up in the studio template

    I documented the shipped pack the same way as newer projects, so anyone picking it up later has the same reference docs.