Making my own Multiplayer FPS Game, where to start?

[Rayhaan Jiwani]

Hello Forum,

Some of you guys who hang out in this section or saw my post when it was made will know that I want to make my own multiplayer FPS game. Now after many suggestions which told me to make my own assets and use the latest version of UE4, I've reached somewhere with my planning but I still want to know where should I start.

Should I start making my own assets or learning the Blueprint system in UE4? And since I'm a noob to all of this, I'll definitely get confused if I do a lot at once. Now please don't tell me to not make my own game 'cause that's my dream and instead answer the question above.

Thanks!

[Venomz1337]

Hello Forum,

Some of you guys who hang out in this section or saw my post when it was made will know that I want to make my own multiplayer FPS game. Now after many suggestions which told me to make my own assets and use the latest version of UE4, I've reached somewhere with my planning but I still want to know where should I start.

Should I start making my own assets or learning the Blueprint system in UE4? And since I'm a noob to all of this, I'll definitely get confused if I do a lot at once. Now please don't tell me to not make my own game 'cause that's my dream and instead answer the question above.

Thanks!

 

Good luck is all I will say.

[multifrag]

Assets is near the end of the pipeline. You want to make the groundwork first. So blueprints in UE4 Is a must. UE4 has a huge library of assets so just try to use them and you can modify them to not look like unreal tournament.

[Rayhaan Jiwani]

SNIP

Thanks, got my bearings, shall start work from this weekend, 'cuz studies are first.

[cluelessgenius]

if you have no clue about programming a good point to start is AntMe.

 

also if you have a dream about something im not gonna tell you not to do it. those big dreams are the only thing driving me forward. but for this thread a good start would be telling us where you stand knowhow wise. i mean 13 is a little young but hey if you are serious about this and start know with baby steps you could be great when it the year of your first application letter.

[burnttoastnice]

Hello Forum,

Some of you guys who hang out in this section or saw my post when it was made will know that I want to make my own multiplayer FPS game. Now after many suggestions which told me to make my own assets and use the latest version of UE4, I've reached somewhere with my planning but I still want to know where should I start.

Should I start making my own assets or learning the Blueprint system in UE4? And since I'm a noob to all of this, I'll definitely get confused if I do a lot at once. Now please don't tell me to not make my own game 'cause that's my dream and instead answer the question above.

Thanks!

 

Best of luck to you.

 

I'd probably start off with making a small test map, and probably 2 characters, and then weapons, then add in the code to be able to shoot. After that, maybe test it with a demo server running on your pc, then have someone else connect to it and try it out. If you know people into web programming/creating APIs you should get them to help you with the server side of things.

 

Looking forward to seeing a demo in a several months' time

[trag1c]

Start by creating a game design document so that the scope of your project is clear. You should also try to create a minimum viable product. This is where you would create and test core features without any assets.

[as96]

 Now please don't tell me to not make my own game 'cause that's my dream and instead answer the question above.

No one here is going to tell you not to make a game, but if your project is basically impossible to realize they will try to bring you back to the ground.

 

Should I start making my own assets or learning the Blueprint system in UE4?

If you want to make a game the most important thing is programming, you can make a game just programming knowledge and basically no modelling skill but not the opposite.

 

Start learning Blueprint, use placeholders (I'm sure you've heard the term "programmer art" before, we tend to use whatever we can make/find in the least amount of time and then change them later) then after you have everything working correctly you can start learning 3d modelling.

 

Have fun, and good luck