About this portfolio

SEO

100 words

  • Unity
  • Multiplayer
  • LiveOps
  • C#

Leonardo Lycan is a Lead Game Developer specializing in Unity game development, multiplayer architecture, gameplay systems, LiveOps, and technical production. This portfolio brings together published projects, playable prototypes, product studies, and articles on game engineering, applied AI, Web3, onboarding, and digital experiences. The work combines team leadership, C# programming, service integration, performance optimization, and clear communication across design, art, and business. For projects, consulting, or collaboration, Leonardo takes a practical approach: understand the problem, build a robust solution, and turn complex requirements into memorable experiences for players and digital products with measurable, lasting impact for teams, audiences, and product goals.

Skills · 08

Web3 & NFT

Ownership, transactions and digital assets integrated into onboarding, inventory and the core loop.

  • Player value before infrastructure
  • Wallet, transaction and recovery states
  • Inventory, economy and blockchain consistency
Web3 & NFT
EvidenceNFT booster packs, Mystery Boxes and rewards in DATA2073, plus on-chain equipment and fighters in CryptoFights.

Ownership needs a gameplay consequence

Web3 and NFTs become part of the product only when acquiring, claiming or owning an asset changes something players understand: build a deck, equip a fighter, complete a collection or enter another competitive decision. Infrastructure should not become the first obstacle in onboarding.

From digital asset to playable inventory

In DATA2073, NFT booster packs, Mystery Boxes, rarity, minting, marketplace, inventory and deck building belong to one product flow. In CryptoFights, on-chain equipment and fighters extend progression inside a competitive multiplayer RPG. In both, the hard problem is consistency across external confirmation, local inventory and the action the player expects next.

How I work

I introduce gameplay value before identity or wallet friction, model transactions as explicit states and keep recovery legible when services fail. Wallet, inventory, economy and game must tell one consistent story from acquisition to use. Web3 Without Blocking Onboarding and From Mystery Box to Playable Card document these two sides of the work.

Building something with this challenge?

Let’s turn the risk into a playable slice.

See related projects