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 · 07

LiveOps

Cadence, onboarding, analytics and remote operations that renew the game without fragmenting the player journey.

  • Permanent, seasonal and social cadence
  • FTUE, funnels and retention
  • Remote content, rewards and feature toggles
LiveOps
EvidenceDATA Pass, recurring quests, seasonal events, staged FTUE, drop-off funnels, remote content and feature toggles in DATA2073.

Operations need to change the next session

LiveOps is not only about publishing content frequently. It coordinates the permanent, seasonal and social clocks of a product so players understand what persists, what changes now and how each reward prepares the next decision.

Connected rhythms inside the product

In DATA2073, the DATA Pass, daily, weekly and monthly quests, events such as Halloween and Mecha Holidays, staged tutorials, drop-off checkpoints, remote content and feature toggles form one operating loop. The strength lies in connecting battle, progression, inventory, onboarding and rewards instead of optimizing each system in isolation.

How I work

I structure calendar, transitions, remote configuration and outcome reading around the player journey. Every event needs a function, every reward should point to another decision and every metric must lead to a change the team can test. The method is documented in LiveOps Runs on Three Clocks, FTUE Optimization, Drop-off Analytics and Remote Content and Feature Toggles.

Building something with this challenge?

Let’s turn the risk into a playable slice.

See related projects