Timothée
HUGUES
Junior Game/Level Designer
Magic Forge Tycoon
Become the ultimate fantasy arms dealer. Forge enchanted weapons, fulfill contracts, influence wars, and shape the fate of kingdoms! Master the astral forge, upgrade your gear, use alchemy, dominate the resource market, and rise as the realm’s mythic weaponsmith.
Genre: Management, Casual
Number of players: 1
Target platform: PC
Team Size: 10+
Duration: 10 months
Core mechanics :
-
Forging System
-
Improvement
-
World Influence
Play the game on steam!
My role and project progress
I joined Magic Forge Tycoon during the final phase of production, where I contributed primarily as a QA Tester and Game Designer.
My work focused on playtesting and evaluation of existing systems, identifying issues related to gameplay balance, progression, UI/UX clarity, and overall pacing. Based on this testing, I proposed improvement directions across multiple aspects, including forging mechanics, tutorial flow, visual readability, and player feedback systems.
I also contributed feedback on graphical elements and presentation, helping highlight inconsistencies in UI, readability problems, and visual elements that impacted player understanding or comfort.
Through structured testing and clear reporting, my contributions aimed to improve polish, coherence, and player experience, supporting the team in stabilizing and refining the game ahead of release.
Organization
The project was developed within a small and remote team, relying on structured workflows and production tools to ensure clear communication and efficient collaboration. We used project management and versioning tools such as GitLab and HacknPlan, along with shared drives, to centralize information and track tasks and progress.
To simplify QA and communication, standardized issue templates were used when reporting bugs or improvement suggestions. These templates included key information such as the current game version, reproduction steps, expected behavior, and screenshots when needed. This made issues faster to understand and easier to address for developers, especially during the final phase of production.
Thanks to this organized workflow and clear documentation, the team was able to communicate issues efficiently, prioritize fixes, and maintain stability and polish toward the end of development.
