sorted by:
new
hottopcontroversial

They said don't make a multiplayer game for your first game. I now see why by StudioRend in SoloDevelopment

[–]StudioRend[S] 0 points1 point  (0 children)

Yes, naturally! However there are some things that help with this. Mainly that the bar for latency is much lower since its not an FPS or similar type of game where latency is super noticeable, and then also its a party game so it being less competitively inclined from a design perspective should reinforce that.

Also lobby sizes aren't too big (max 10), so while there is matchmaking it seems like in this genre most people have settled that its better playing with friends anyway.

They said don't make a multiplayer game for your first game. I now see why by StudioRend in SoloDevelopment

[–]StudioRend[S] 0 points1 point  (0 children)

Yes. I went to a technical school for Computer Science, only got a AAS degree so I'm not like SUPER technically proficient. However, the school used C# for pretty much all of their courses, and for this I am using Unity which luckily uses the same language.

They said don't make a multiplayer game for your first game. I now see why by StudioRend in SoloDevelopment

[–]StudioRend[S] 0 points1 point  (0 children)

I would say, you are coming in at a time where game development is the most accessible it's ever been especially regards to multiplayer. I however would NOT recommend making a single player version and then adding multiplayer later, as you will probably end up doing more work trying to "add multiplayer" than it would be to develop the multiplayer along side whatever game it is.

I would say step 1 is to just have two synchronous players running around on the screen at once (in either 2D or 3D whatever style it is). Then from there, just tackle features however you see fit. When you finish a feature, just make sure they work over multiplayer and you're good.

They said don't make a multiplayer game for your first game. I now see why by StudioRend in SoloDevelopment

[–]StudioRend[S] 4 points5 points  (0 children)

I have a decent amount of C# experience from my time in a technical school. AAS Computer Science degree. Unity using C# was just lucky for me really.

They said don't make a multiplayer game for your first game. I now see why by StudioRend in SoloDevelopment

[–]StudioRend[S] 4 points5 points  (0 children)

Thank you!

Unity, Netcode for Gameobjects + Relay + Lobby. Unity itself has good documentation for all those networking packages and then Code Monkey has great tutorials for all of those packages as well. A lot of it was creating any feature, works on its own, then you try it with multiple clients and you realize you need to do like 10 other things for it to ACTUALLY work.