Bring up the World Properties menu by selecting View | World Properties from the menu bar at the top of the UDK interface. Type Game Type in the search bar at the top of the World Properties menu to bring up the Game Type menu and the relevant options for us. From there, change the drop-down menus for both Default Game Type and Game Type for PIE to UTDeathmatch. As we are in the Zone Info section, under Kill Z set the value to -1000.

Now let's make sure our player spawns in the correct position. Select the PlayerStart_0 object and press F4 to access the object's Properties window. From there, in the search bar at the top, type Location. Once you find the Location vector variable, set the X value to 0. Next, type Rotation. Make sure that the Roll and Pitch options are set to 0 and change the Yaw option to 90.

Also, note the numbers listed on the Y and Z values in the Location variable, as we will be using them in a future step.

From here we need to access the Actors Classes panel by selecting View | Browser Windows | Actor Classes. Inside, click on the CameraActor selection that is located under Categories | Common | CameraActor.

Go back to the editor menu, right-click, and select Add CameraActor Here. With the object placed, press F4 to go to the object's Properties menu. Change the value of X in the Location property to be -650, and the Y and Z values to the same position as PlayerStart_0, -1248, and 80.

With the necessary objects in place, we open up the Kismet interface by clicking on the K icon at the top of the UDK interface on the main toolbar. From there we first need to create a Player Spawned event. We then right-click anywhere inside the large area in the upper portion of the interface. Choose to create a Player Spawned event by choosing New Event | Player | Player Spawned from the menu that pops up. Click on the Player Spawned event's Sequence Event to have the Properties window come up and change the value of Max Trigger Count from 1 to 0.

Underneath the Player Spawned event, right-click under the Instigator output and select Create New Object Variable. You should see a line connecting the output to the new object variable. If not, click on the connector (the purple triangle) and drag until you select the new variable we created and let go. Click on the new object to open its properties in the bottom-left panel of the Kismet window. Under Sequence Variable, we change the value of Var Name to Player.

To the right of the Player Spawned event, create a Set Camera Target action by right-clicking and selecting New Action | Camera | Set Camera Target. Right-click under the Target input and select New Variable | Named Variable. Click on the variable to open its properties. In Properties under Find Var Name, type in Player and press Enter. You should see the red X change into a green checkmark. Connect the Player named variable that we created to the Target input.

Exit Kismet, click on the CameraActor_0 actor, and return to Kismet by clicking on the K icon on the main toolbar. Right-click on the Cam Target input (the pink square) and select New Object Var With CameraActor_0. Finally, connect the Out output from the Player Spawned event to the In input from the Set Camera Target action we created.

If we started the game at this point, we would notice that when the player spawns we can see the player from a third-person perspective that looks great as long as we do not move. You will notice that the camera does not move with the player and if we move our mouse, our player will turn around and allow us to move in ways that are counter-intuitive to what we are trying to create. Let's fix those issues now.

Create an Attach to Actor action by right-clicking and selecting New Action | Actor | Attach to Actor. Connect the Target input to the Player variable, and Attachment to the CameraActor_0 variable that we created in the previous section. In the properties for the Attach to Actor action, check the Hard Attach option and connect the Out output from the Set Camera Target action to the In input of the Attach to Actor action.

Create a Toggle Input action to the right of the Attach to Actor action by right-clicking and selecting New Action | Toggle | Toggle Input. In the action's properties, uncheck the Toggle Movement option and make sure that the Toggle Turning option is checked. Connect the Player named variable to the Target input. Connect the Out output of the Attach to Actor action to the Turn Off input on the Toggle Input action.

You can connect all of the targets to the same player, or create multiple Player named variables to house all of the things; it makes no difference, but one may make your code look more visually appealing.

Save your project (File | Save All) and start your game by pressing F8 or selecting Play | In Editor on the main toolbar.

With your current level saved, exit out of UDK and open up Windows Explorer. Go to the folder you installed UDK to—that is, to the UDKGame\Config folder. Right-click on the DefaultInput.ini file and select Copy. Then use Ctrl + V to paste a copy of the file into your folder.

Open the file and replace the following lines:

.Bindings=(Name="GBA_MoveForward",Command="Axis aBaseY Speed=1.0")
.Bindings=(Name="GBA_Backward",Command="Axis aBaseY Speed=-1.0")
.Bindings=(Name="GBA_StrafeLeft",Command="Axis aStrafe Speed=-1.0")
.Bindings=(Name="GBA_StrafeRight",Command="Axis aStrafe Speed=+1.0")

With the following:

;-----------------------------------------------------------------
; Hotshot - Begin Changes
;-----------------------------------------------------------------
.Bindings=(Name="GBA_MoveForward",Command="Jump | Axis aUp Speed=+1.0 AbsoluteAxis=100");
.Bindings=(Name="GBA_StrafeLeft",Command="Axis aBaseY Speed=-1.0")
.Bindings=(Name="GBA_StrafeRight",Command="Axis aBaseY Speed=+1.0")
;-----------------------------------------------------------------; Hotshot - End Changes
;-----------------------------------------------------------------

Then replace:

.Bindings=(Name="Left",Command="GBA_TurnLeft")
.Bindings=(Name="Right",Command="GBA_TurnRight")

With:

;-----------------------------------------------------------------
; Hotshot - Begin Changes
;-----------------------------------------------------------------
.Bindings=(Name="Left",Command="GBA_StrafeLeft")
.Bindings=(Name="Right",Command="GBA_StrafeRight")
;-----------------------------------------------------------------
; Hotshot - End Changes
;-----------------------------------------------------------------

Save the file, and start up the UDK Editor once again.

Open up the Kismet Editor. Create a Console Command action by right-clicking and choosing New Action | Misc | Console Command from the menus.

Inside the Properties window type SetJumpZ 750 as the value for Commands[0]. Connect the Player variable to Target. Connect the Out output from the Toggle Input action to the In input of the Console Command action.

Next, create a Modify Property action by right-clicking and choosing New Action | Object Property | Modify Property from the menus. Expand Properties[0] by clicking on the + icon in order to create a new array entry. In the Property Name variable, type MaxMultiJump. Check the Modify Property option and change the value of Property Value to 0. Connect the Player variable to the Target input. Connect the Out output from the Console Command action to the In input of the Modify Property action.

Create a Toggle Cinematic Mode action by right-clicking beside the Modify Property action and selecting New Action | Toggle | Toggle Cinematic Mode. Uncheck all of the options apart from the Hide HUD option. Connect a Player variable to the Target input, then the Out output from the Modify Property action to the Enable input of the Toggle Cinematic Mode action.

Finally, create a Give Inventory action by right-clicking and selecting New Action | Pawn | Give Inventory. Check the Clear Existing and Force Replace options. Connect a Player variable to the Target input, then connect the Out output from the Toggle Cinematic Mode option to the In input of the Give Inventory action.

Save your project (File | Save All) and start your game by pressing F8 or selecting Play | In Editor on the main toolbar.

Open the Content Browser window in View | Browser Windows | Content Browser. Find the following static mesh: StaticMesh'FoliageDemo.Mesh.S_PavingBlocks_01'. Click on it and return to the editor's screen. Right-click on the ground of your level and add the mesh to your level (you may need to load it in first) by selecting Add Static Mesh: FoliageDemo.Mesh.S_PavingBlocks_01.

Delete the static mesh of the box that is currently in the level by clicking on it and pressing the Delete key. Select our new platform and change its location to 0, 0, 240 in the same way that we did in the first step. Duplicate the mesh three times and rotate it to face the three sides the camera can see. You can duplicate the object by either holding down Alt and dragging or by going to Edit | Duplicate. In order to rotate, you can use the translate tool or alter the properties.

Make another duplicate of the top platform by holding Alt and dragging along the y axis (256 units). Right-click on the newly created platform and select Convert | Convert StaticMeshActor To Mover. Inside the Properties window, change the Collision Type to COLLIDE_BlockAll and check Block Rigid Body.

Back in Kismet, create a new subsequence by right-clicking and selecting Create New Sequence : 0 Objs. When the naming dialog comes up, type in Moving_Platform_LR for the Sequence Name field and click on OK. Double-click on the sequence in order to enter it.

Create a Level Loaded event by right-clicking and selecting New Event | Level Loaded. To the right of it create a new Matinee sequence by right-clicking and picking New Matinee. Connect the Loaded and Visible output of the Level Loaded event to the Play action of Matinee. In the Matinee's properties under Seq Act Interp, check Looping and Rewind if Already Playing.

Outside the editor, click on the soon-to-be-moving platform and then go back to Kismet, and double-click on the Matinee sequence to enter the Matinee editor. Right-click inside the Group List (the dark-gray column below all the tabs with text and to the left of the timeline. From the context menu that appears, click on Add New Camera Group. When prompted for a name, type in Platform.

To create our moving platform, create two keyframes by clicking on the Add Key button at the beginning of the Movement track with the first at the 0:00 spot and the second one at the 1:00 spot. Then create another at the 6:00 spot. These keyframes won't be moving at all, so do not change their positions. Create two more keyframes at the 3:00 and 4:00 spots. At each of these keyframes move our platform along 640 pixels along the y axis. Once the first one is completed, you will have to adjust the second one to the same placement as well. Be sure to make the Location values match exactly.

Now that we have a single platform already created, exit out of Matinee and exit this sequence. Copy and paste the sequence. Right-click on the newly created one and rename it to Moving_Platform_UD. Double-click on the new subsequence and enter its Matinee sequence. In this Matinee, change the 3:00 and 4:00 values to change on the z axis 256 units down.

The point of going from a higher value to a lower value is to make the moving platforms meet up in such a way that you can jump on them for a period.

Make sure that the platform is selected in the editor. Exit out of the Matinee editor and click on the Matinee that you just finished editing. In the Matinee's properties, check the Force Start Pos option and set the Force Start Position value to 0.2.

Select the three sides of the first platform that we created (the static one) and hold Ctrl + G in order to group them together. With our platforms created, let's remove some of the elements that are no longer needed and the default floor by selecting it with the left mouse button and hitting Delete. In its place, duplicate the group that we just made and position it on the same Z value as the floor that was there previously. In the same way as we created the group of the static platform, we can also use this same mesh to create a staircase. Have each stair only be 16 units above the previous one and create a staircase leading up to the initial static platform.

Click on our initial static platform and duplicate it to create floors for the moving platforms section, so that if the player falls they will not die so early in the level. Take the same group and duplicate it to the left of the player's starting position twice. Ungroup the groups we created by holding Shift + G and remove the inner parts that aren't required, then hold Ctrl + G to recreate the larger group as a whole. Delete the unused sections.

The stairs work, but the camera moves jaggedly as we walk up or down on it. Thankfully, we have an easy solution, the BlockingVolume brush.

Click on the builder brush (the red square in our initial level) and open up Geometry Mode by either selecting it on the right side on the top row of the Modes toolbar, or by pressing Shift + 2. With it selected, create a shape like the following screenshot, by first extending the left side of the brush outward, then grabbing the top-left points and dragging downwards until it is only 16 units above the original. Right-click on the brush and select Add Volume | Blocking Volume. At this point if you would like to select all of the stairs, change their Collision Type to COLLIDE_NoCollision, though it will not change what the player interacts with.

Duplicate our large left sidepiece twice on the right-hand side with the tallest section being the jump height from the up and down moving platform's peak. From there, create another duplicate object around 864 units apart and in the middle, place a duplicate of our initial static platform to use.

Click on the LightmassImportanceVolume option (the yellow box), and use Geometry Mode to extend it to the space that we are using in the level.

Build your project by selecting Build | Build All. Save your game using File | Save All and run our game by selecting Play | In Editor.

Go to the Content Browser window by going to View | Browser Windows | Content Browser. In Content Browser, find the following particle system: ParticleSystem'WP_ShockRifle.Particles.P_WP_ShockRifle_Ball' and click on it. Exit Content Browser and find a platform, right-click on it, and select Add Emitter: P_WP_ShockRifle_Ball. Hit the Real Time visualizer circled in the following screenshot or by pressing Ctrl + R to get a view of what our collectible will look like. Position the item in the air in a place that the player can reach by jumping, such as one of the previously mentioned positions the moving platform is travelling on.

Create a trigger around our new particle system by clicking on the builder brush. Right-click on the box selection on the Brushes toolbar and set the size of our builder brush to 64 in the X, Y, and Z positions. Drag the box to fit around the emitter that we created in the previous step, by using the translate tool or by holding Ctrl and dragging it to where we want it to be. Keep in mind to have it positioned along the axis so that the player will actually be able to touch it.

Back in the Content Browser window, find the particle system ParticleSystem'WP_ShockRifle.Particles.P_WP_ShockRifle_Explo' and add it slightly away from the first particle system. Inside its properties in Particle System Component, disable the Auto Activate option.

Open up the Kismet Editor and create a new subsequence by right-clicking and selecting Create New Sequence : 0 Objs. When the naming dialog comes up, type in CoinPickup for the Sequence Name field and press OK. Double-click on the sequence in order to enter it.

Outside Kismet, click on the trigger volume we created, then go back into Kismet. In our CoinPickup sequence, right-click and select New Event Using TriggerVolume_0 | Touch to create a Touch event for the Trigger. Create a variable under the Instigator output.

Next, create a Play Sound action on the right-hand side of the Touch event we just created by right-clicking and selecting New Action | Sound | Play Sound. Connect the Target input to Instigator from the TriggerVolume_0 Touch event that we created in the previous step.

Open up the Content Browser window and select the Sound Cue that you would like to play when you collect this item; I used SoundCue'A_Pickups_Powerups.PowerUps.A_Powerup_UDamage_SpawnCue'. With that Sound Cue selected, exit out of the Content Browser window and go back into Kismet to our subsequence. Click on the green arrow to the right of the Play Sound variable called the Use selected object in Content Browser button and it should be filled with the sound we want to use.

Create a new Toggle Hidden action by going into New Action | Toggle | Toggle Hidden. Connect the Out output from the Play Sound action to the Hide connection of the Toggle Hidden action.

Exit Kismet and in the UDK Editor click on the first particle system that we created (Emitter_0) and go back into Kismet. Right-click under the Target input and select New Object Var using Emitter_0.

Now create a new Toggle event by selecting New Action | Toggle | Toggle. Connect the Out from the Toggle Hidden action to the Turn On connection on the Toggle action.

Close Kismet and in the UDK Editor click on the other particle system that we created (Emitter_1) and go back into Kismet. Right-click under the Target input and select New Object Var using Emitter_1.

At this point, we should have a single collectable that will hide our coin and will then play a sound as well as a particle system to inform the player what has happened. Now that we have created a single coin, let's make it extremely easy for us to create new coins with the same functionality. To do that, we will be using prefabs.

Rotate your screen so that the sky is in the air and you can clearly see the objects of our collectable without touching anything else. Move your mouse to the top left, slightly away from where the top left of the collectible's objects are. Hold Ctrl + Alt and drag down, right until the red rectangle is completely covering our collectable. This should select everything within the collectable. Alternatively, you could hold down Ctrl and click on each of the elements to select them.

Right-click on the objects and select the Create Prefab... option. In the dialog box that comes up, put in Hotshot01 for the Package field and Coin for the Name section. After filling this out press the OK button. It will say that it found a sequence for the prefab. We say Yes to make the sequence part of the prefab and No to make the object an instance of the prefab. As soon as this happens, go to the Content Browser window and save our Hotshot01 package in the same folder as your level.

Take time to place some of these prefabs into your levels in areas that players may want to visit or entice players to travel a certain way. Be sure to build your game before you see if they work by selecting Build | Build All from the menu.

Note that some of these coins are obtainable with the player's default jump height. With that in mind, let's take our original actors to modify them for this new purpose.

Select the first emitter that we made on the collectable that is not currently a prefab. Press F4 to access its properties and change the Particle System Component's Template property to be ParticleSystem'CTF_Flag_IronGuard.Effects.P_CTF_Flag_IronGuard_Idle_Red'. Have the other emitter use ParticleSystem'VH_Scorpion.Effects.PS_Scorpion_Gun_Impact_Red' as its template.

Right-click on one of the two emitters and select Select Find Emitter_X in Kismet. To the right of our Toggle action, we want to create a Modify Property action by right-clicking and choosing New Action | Object Property | Modify Property from the menus. Expand Properties[0]. In the Property Name variable type in MaxMultiJump. Check the Modify Property option and change the value of Property Value to 1. Connect the Player variable to the Target input. Connect the Out output from the Toggle action to the In input of the Modify Property action.

Back in the UDK Editor, select all of the objects that make our "Double Jump" power-up and press Ctrl + G to create a group of it. We only want to have one of these in our level and we want to make it somewhat skill-based in order to get it as it opens new areas for people to explore.

Build your project by selecting Build | Build All. Save your game using File | Save All and run our game by selecting Play | In Editor.

Click on the Landscape button under the Modes section of the left toolbar; this should cause the Landscape Edit window to open for us.

Once the Landscape Edit window comes up, it will have many options listed. We want to create a Heightmap, which we can now use within our level. In the Heightmap Size section, put in the values 64 x 64, and in the Component Size section select put 7 quads per component. Then click on the Create Landscape button.

After waiting for a period, you should see a large checker board-looking plane, which is our landscape. All the tools in the Landscape Edit window have tool tips telling you what they are, but to get the general feel of it in order to raise the level of whatever you are currently selecting, you can hold Ctrl down and click. To lower the size of something, you can hold Ctrl + Shift and click. To change the brush's size, there is a variable under Brushes called Brush Size.

Create hills in the background of our level and lower the value of the areas that are actually part of the platforming section of our level. Be careful that the edges are not visible on the far left or far right of the level.

Exit the Landscape mode and enter Camera Mode, and then click on our landscape. Press F4 to access the object's properties. Under Landscape in the Landscape Material variable, fill it with Material'PivotPainterExamples.Materials.ground_Material'; feel free, however, to fill it with whatever material would be best for your particular level.

Build your project by selecting Build | Build All. Save your game using File | Save All and run our game by selecting Play | In Editor.