Conversation

Notices

1. Embed this notice
   The Seven Voyages Of Steve (sinbad@mastodon.gamedev.place)'s status on Monday, 04-Nov-2024 03:21:00 JST The Seven Voyages Of Steve

   A lot of my days are spent making something quite simple but which is rendered waaay more complicated because of multiplayer - and I’m not even making a competitive game so I don’t care very much about cheating (if you want to break the game you play co-operatively with friends, knock yourself out).

   It can be quite frustrating that everything takes longer, but when testing, just the act of messing about in the game with another person makes it feel worth it

   • Embed this notice
     Nikita Lisitsa (lisyarus@mastodon.gamedev.place)'s status on Monday, 04-Nov-2024 03:26:24 JST Nikita Lisitsa

     in reply to

     @sinbad I have a bunch of ideas of multiplayer games (both co-op and competitive) that I'd love to make some day, but the complexity inherent to multiplayer makes me horrified

   • Embed this notice
     The Seven Voyages Of Steve (sinbad@mastodon.gamedev.place)'s status on Monday, 04-Nov-2024 03:30:34 JST The Seven Voyages Of Steve

     in reply to

     • Nikita Lisitsa

     @lisyarus I’m lucky that UE does a lot of the heavy lifting and is well proven in this area, but even so - dumb little things trip you up

   • Embed this notice
     Tom Schultz (tom_schultz@mastodon.gamedev.place)'s status on Monday, 04-Nov-2024 03:54:09 JST Tom Schultz

     in reply to

     • Nikita Lisitsa

     @sinbad @lisyarus It's not so bad! I made a couple of small co-op games in Unity and I was working on another in Godot earlier this year. They were a mix of client and server authority.

     I think the first one kind of sucks as you learn the patterns and ways of thinking, but then it becomes easier. Also, if your networking library isn't polished and proven it'll be a headache. Netcode for GameObjects in Unity was occasionally a real PITA when I used it last year.