Start with shooter example or not?
I'm planning on creating a FPS game which has the same basics as the shooter example game you can download from the marketplace, but I'm not sure if it's best to simply look on the project and do everything myself or create the game from that project. The reason I ask this is because I noticed that alot of headers and stuffs still had the name shooterproject (even though my project was named something else) and if I have to remake the GUI and change weapons etc I don't know if it will cause me more trouble then good to start from the shooter game.
asked Jul 26 '14 at 10:41 PM in Using UE4
I was faced with this same exact question for my own project. I soon realized that I wanted to start from scratch and code everything myself. However, i do have the shooter example and and several others as guides. The main 3 reasons I chose this path:
1) To truly understand whats going on in the fundamental classes, you need to get your hands dirty. I felt a straight copy and paste of the code didn't gain much overall depth of the engine.
2) I wanted my own naming convention. I didn't want "Shooter" in front of everything.
3) When you need to upgrade Engine versions, many things can be deprecated. If you have a good idea where everything in the base classes are supposed to work, you can easily shift from lets say 4.2 to 4.3 and any future versions.
However, to each their own style. I felt the Shooter example was more of a tutorial to follow for your own project than actually start as your base. I'm very happy so far that I did this approach as I have a deeper knowledge of the Engine.
That's just my thought and what I did, hope it helps. ;)
Follow this question
Once you sign in you will be able to subscribe for any updates here