Mission Object Set Up: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
##Mesh## | ##Mesh## | ||
Take a prop that is going to represent your hack-able object and place it in your scene. | Take a prop that is going to represent your hack-able object and place it in your scene. | ||
Line 8: | Line 9: | ||
##Add the Hackable component## | ##Add the Hackable component## | ||
Decide how you want it too behave in it's different states, as explained on the [[Devices]] page. | Decide how you want it too behave in it's different states, as explained on the [[Devices]] page. | ||
##Add the MissionObject component## | ##Add the MissionObject component## | ||
This is explained in more depth in the [[MissionObjects]] page, but essentially in this example we just need to add the MissionObject component and set it to 'Hackable'. | This is explained in more depth in the [[MissionObjects]] page, but essentially in this example we just need to add the MissionObject component and set it to 'Hackable'. |
Revision as of 14:14, 14 December 2018
- Mesh##
Take a prop that is going to represent your hack-able object and place it in your scene.
It can be anything really, but to to make full use of the options available either:
- Choose from the Hackable Devices Collection scene in LevelKit.
- or follow this guide to Modeling your own Hackable Devices
- Add the Hackable component##
Decide how you want it too behave in it's different states, as explained on the Devices page.
- Add the MissionObject component##
This is explained in more depth in the MissionObjects page, but essentially in this example we just need to add the MissionObject component and set it to 'Hackable'.