willow meteor
Hi everyone,
We're SufficientlyRoasted, a two-person dev team, and after over two years of development, we just released our game on Steam! We finally hit the launch button and are excited to see where this goes.
For the technical side: the game is made in Unity using Netcode for GameObjects and features a fully host-authoritative architecture.
Our two biggest challenge during development were playtesting and general multiplayer (server-authorative development).
Playtesting
Since the game is designed for 5-10 players, validating things with just the two of us was incredibly difficult. Tools like ParrelSync and Unity's new Multiplayer PlayMode definitely helped, but properly testing the core gameplay loop was near impossible without annoying our friends every few weeks.
Fellow indie devs: how have you playtested and validated your multiplayer games in the past? We'd love to chat and hear your strategies.
Multiplayer and server authorative games:
Right behind playtesting is making server authorative games in general with unities Netcode for gameobjects(NGO). We've found it incredibly difficult as the learning resources out there are limited, and NGO has no out of the box support for client-prediction, interpolation, lag compensation or other more high-level multiplayer features.
Again, how have you guys dealt with this? Our take-away is that our next game will likely not be a multiplayer game at all or at least only feature 2-3 players and be fully client-authorative.
If you have any other questions, ideas, or criticism, we'd love to hear it all in the comments!
Check out our Steam page here: https://store.steampowered.com/app/2670810/Candy_Bandits/
Hope to see you in-game!
Best,
SufficientlyRoasted
