I’m looking for tips or a tutorial that shows how to create a role and equipment selection system for an FPS game.
Explanation:
When you join a server, so you will get a page/menu where you can choose the squad and role (Rifleman, Sniper ect). Each role has a specific number of equipment and weapons you can choose from: Primary weapon, secondary weapon, armor, optics ect. Once you have selected the equipment and pressed Apply, you will spawn into the round with equips you have selected.
Is there such a tutorial out there with either C++ or Visual Blueprint Scripting? That describes how to create something similar, and how to get all of the equipment and weapons to be right aligned on the right socket.
Would be eternally grateful if someone could help me
I don’t know if there is a tutorial for what you want, but it’s easy to make…you need a good amount of time only.
I don’t know your Blueprints skill level, but IMO these are the steps:
1- Level BP: Begin Play > Make a Widget [UMG]
2- UMG: Classes, Weapons, Gadgets and Equiment Selection
3- Character BP: Attach/Detach Weapons, Gadgets and Equipment
4- “…how to get all of the equipment and weapons to be right aligned on the right socket.”: You can make a different socket for every single weapon. If you have 10 weapons, make 1 socket and duplicate it 9 times…you can call them “Socket Weapon x” where “x” is the Weapon number. Now you can align each weapon in the best way.
Let me know if you need more help.
I would make a prototype for you starting from my template but I don’t know if I’ve time to make it.
My knowledge of Unreal BP scripting is poor. I’m most familiar with java/C programming, even if it starts to get a while since last time.
I want to learn everything about BP scripting! I wondering if I should buy ‘The Ultimate TPS / FPS Template’, would be great if you could create a quick example in your template
I’m honest with you: my template is a good start only for what you need, because my template hasn’t what you want, but if you understand “my” BP, you understand how to make a role and equipment selection system.
Anyway, if your knowledge of BP is poor, I’ll try to help you with a free customized project or something like that. Give me some (2/3) days :o
Hi, I would love anything that would help to create an avatar creation system and this stuff seems to be exactly it. It would be awesome if you could share your results.^^
[=Diaval;177844]
Hi, I would love anything that would help to create an avatar creation system and this stuff seems to be exactly it. It would be awesome if you could share your results.^^
[/]
Tomorrow I share with you my Selection System Prototype and you can download it See you later
That is some pretty impressive work, have you implemented the melee system for your weapons?
[/]
Hi !
No. I’ve a roadmap for my first UE4 project and the weapons system is scheduled for December 2014.
ATM I don’t know if and how I’ll implement the melee system.
[=‘[aCe]
Total;178925’]What must I do to split your widget into two seperate widgets. One widget for the class selection and one widget for the rest.
[/]
The best way is:
1- Rename “MySelection” widget in “MySelection1”
2- Duplicate “MySelection1” and call the copy “MySelection2”
3- MySelection1 = Delete anything about the class selection and Save the rest
4- MySelection2 = Save anything about the class selection and delete the rest
Now you need 2 “Create Widget” nodes in Level BP and 2 Object Reference Variables. I hope you understand my spaghetti :rolleyes:
hm, I did as you wrote, Diat Funa, but for some reason I can’t get the Class 1 button to work.
How it should work: After pressing the Class 1 button from MySelection 2, then CL1 - PRIMARY 1, CL1 - PRIMARY 2, CL1 - SECONDARY 1 ect. from MySelection1 becomes visible for selection. I dont think the “button” reference names does work on cross over two Widgets? How to fix that?
i’m not allowed to return values from both widgets to the same “Set input Mode UI ONLY - In Widget to Focus”. Do I need to create 2x “Add to viewport” and 2x “set input mode” ?
See you later 
