Hey apoisonedgift,
Good template, however I’ve encounter some bugs here and there on widgets, it seems like it wasn’t tested enough. They are very simple to fix, takes less than 10 minutes to figure it out if you know what you are doing. Just be mindful of widgets next time apoisonedgift, they are very easy to screw up.
for example, Hit inventory key and then Main Menu key, both widgets will appear causing input bug on earlier opened inventory widget. Meaning, it will stay with input of the Main Menu, rather than going back to input mouse setting of inventory widget. If you hit destroy button inside inventory and hit Main Menu key (Esc), then user gets stuck with no other solution than ALT + F4. These have two workarounds. Close inventory widget when Main Menu is called, or return to current widget after one is called. Third one takes longer time to implement, possibly requiring to change a lot of logic. Just go with option 2, since it seems that after you hit resume in Main Menu widget it goes back to game.
Also, encounter a few logic errors in game multiplayer hosting logic and also logic (errors/miscalculations) MATH or better … Few more testing required to find solutions, you might have to do some few calculations…
For example: (standalone game) If you host a match (only tested in LAN), go to main menu widget (Esc), try to host a match again, you will encounter (log assigned message error) when creating the match again[it wont allow you to host match]. Easily fixable.
Another Example: (of course you can have player die and drop all inventory for this, but for the heck of a custom game why not point it out.)If you die when weapon equipped and ammo left, when re-spawned, weapon doesn’t fire, so for the logic of your blueprint to pick up, you have to drop ammo and pick it right back (get it?) should be easily fixable :P, I’ll give you 2 minutes to find it. A LONG TIME… haha
Overall, good product. Really like the fact that it takes a month or two out of work. Hope we get good support to fix these bugs.
Suggestions so far, only tested this template for 20 minutes and nearly 20 seconds, I had seen the code logic of the previous version so I know how the logic was going. I basically became apoisonedgift’s brain , so I do know what to test for 
:
Fake loading widget, just to give time to textures/materials to get compiled.
Key remapping
Take a look at widgets and test them like if you are looking for ants in a room, any possible breach. Specially, avoiding programmers widget issues if the template is going to be used for expansion.
When player dies, drop all inventory
fix those simple bugs
Bool DidYouGetIT = 1; ? 
// I might have to look more into the template, but I have a short time to take a look at other programmers’ code and test games, since I’m working on one now. SO…
Sorry, If I was no much help on this post, I wrote this in a rush. Also, not even time for grammar fix, thank you very much!! 
Best lucks,
Akalovemaker