The pains of game development in unreal engine 4. [Mini rant]

[anonymous_user_fd498a211 (anonymous_user_fd498a21)]

@swordfighter;518244

Yes I would be very much.

Well then, Let’s get the ball rolling! Do you know how to apply a zipped project file on top of the original multiplayer shootout? That’s the best way I can see giving you the updated, fixed version. Small download size that way. If not, I could upload the entire project.

I like that. I’m going to use it my self.
the first time I use it I’ll give you credit
the second time I’ll Say some one said.
the third time I’ll say I always said.

Go for it. I made the saying up, but I am sure I’m not the first to say it.

@Nazban

Im sure it’s a memory leak issue but I will give you some advice… Don’t use blueprints. They glitch out, cause memory leaks and can never tell you the source of the error. Let alone file hierarchy… Blueprints is a way to get new people into the unreal engine I believe. This is a big reason they only support blueprints because they know you can’t actually use them in a production environment. They are a cool concept and fun to play with but until we have something solid like programming I can’t even imagine blueprints in a large scale project rofl.

I don’t mind it though. As long as it doesnt wreck my project so I lose work. (which it is doing!) I kind of enjoy blueprints, I like to see how far I can go with them, and it’s pretty far, which makes me happy. I love coding too, don’t get me wrong, but it’s nice to get out of the IDE for a while and still get things done.

Honestly though, along with all the content on the unreal engine wiki, there should be a “THINGS YOU SHOULD KNOW BEFORE GOING STRONG WITH UNREAL ENGINE” page. little tidbits like, ignore construction scripts on gamemodes, check memory of your pc and keep an eye on the output log and get on git no matter what if you care about your project at all. That would have helped me immensely, knowing what I know now.