A game that continues after battle

DATA2073: Battle Deck is a tactical card game set in a post-apocalyptic universe of Automatons, featuring over 100 unique characters to build your deck. On the board, positioning, energy, drones and card synergy define the rhythm of every turn-based match.

Campaign, progression and retention

Combat is the center, but not the limit. Campaign maps, stage objectives, inventory, deck building and rewards lead players from one match to the next. The First Time User Experience (FTUE) was heavily optimized using deep drop-off analytics, introducing rules in stages to maximize player retention.

Quests, bots and the reward economy

My technical contribution included the recurring quest system and the flow that keeps matchmaking playable when no human opponent is available. Daily, weekly and monthly quests receive progress from gameplay actions, validate completion and return rewards through the same shared pipeline used by other product systems.

PvP and bot matches, however, do not need to follow the same economic contract. The system selects reward configurations for each context instead of treating every victory as an identical event.

To prevent that fallback from becoming an unlimited source of currency or XP, rewarded bot matches use a configurable daily allowance. After the limit, players can still choose to continue against bots, but without additional rewards. The central lesson is to separate two decisions that look identical: keep the core loop available and control the economy’s faucet.

LiveOps, Remote Content and Toggles

Screenshots preserved show the product changing in cycles: the DATA Pass launch, Halloween and Mecha Holidays. The entire operation relies on remote content delivery, allowing the team to enable and disable features in real-time via feature toggles, refreshing the operational rhythm without requiring new store updates.

Web3 and NFT inside the product loop

NFT booster packs, transaction confirmation, mint history and marketplace are part of the documented flow. Digital assets are not presented as an isolated promotional layer: card acquisition, ownership, collection and use connect directly to the metagame and deck building.

A systems case, not a single screen

The documented work crosses quests, DATA Pass, inventory, tutorials, maps, seasonal events, rewards and Web3 integrations. The technical challenge was keeping those layers synchronized without hiding the main action behind disconnected menus.

Public-product evidence

The case uses material from real builds and can be checked against the official website and Epic Games Store release. It focuses on Unity contributions and documented systems without individually claiming studio art or intellectual property.