Lessons Learned from Developing a Multiplayer Arena Brawler
summary
A free to play arena brawler built in Unreal Engine 4 then migrated to Unreal Engine 5 ships a soft launch in the Philippines, centers on a two‑character swap mechanic and three‑player free‑for‑all modes, and finds 90% preferred landscape controls after player testing. Development uses an off‑the‑shelf backend (Play) for auth, matchmaking and scaling, adds multiple dev servers so live fixes are testable, automates QA to cut full test cycles to about two days, and discovers progression systems take far more content and time than expected.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 2:38Publisher alignment lessons
- 3:43Multiplayer technical challenges
- 5:08Arena brawler misconceptions
- 6:36Free-to-play competition
- 10:41Mobile controls design
- 12:48Player feedback and combat visibility
- 15:37Early community building
- 18:18Matchmaking strategies
- 22:15Live service challenges
- 23:42Anti-cheat and backend
- 26:20Progression system complexity
- 27:27Automation testing
- 29:14Multiplayer sync testing
- 31:44Server version management
- 33:33Local multiplayer necessity
- 36:09Funding options
- 38:43Publisher vs VC funding
- 41:28Monetization strategies
- 42:33Early marketing impact
- 44:06Game modes analysis
- 47:07Q&A
related talks
49mMultiplayer Misadventures - Tales from making our first PvP multiplayer game in Unity
43mImplementing Team-Based Matchmaking without a Matchmaking Server
22mLessons from triple-A game development applied to blockchain games
27mFulfilling your multiplayer game’s potential
33mMultiplayer Design in VR Gaming
31mTentpole Game Design: How to Make a Competitive Multiplayer Experience that Drives Deep Engagement
24mMultiplayer Mastery: Key Considerations for a Successful Start
47mPanel: Mastering Multiplayer: The Super Session