Sidescrolling 2.5D Shooter

Transcription

1 Sidescrolling 2.5D Shooter Viking Crew Development

2 1 Introduction Support D or 3D physics? Multiple (additive) scenes Characters Creating different looking characters Inventory AI Who s behind the wheel? What does Seeker do? Guns Procedure for creating a new weapon Bullet manager World Pathfinding Planned features Introduction 1

3 1 Introduction This system aims to be a base project for anyone who wants to create a 2.5D gun n run game. The scripts follow SOLID-principles as closely as possible in order to make it easily extendible. For example, where possible UnityEvents are used to communicate between scripts so that the scripts do not need to reference each other. If you have suggestions for further improvements in this regard let us know! 1.1 Support There is a thread for support questions at: If you prefer support through the address is: mike@vikingcrew.net There is also a thread for ideas, suggestions and feature requests at All ideas are most welcome, regardless of whether you own the package or not! We would also love to hear about your projects. If you have a plan for something you want to make, please do not hesitate to let us know. We can probably give valuable advice on how to get the most out of the package. Note that you are currently reading the first version of this manual. Any and all feedback on it would be most welcome! 1.2 2D or 3D physics? In this package we have implemented 2.5D in two versions: One uses 2D physics for all game logic related physics (characters, bullets etc.) and uses 3D physics only for visual effects (particles, ragdolls etc.). The other one uses 3D physics for everything. Which one you choose to use is up to you and your project requirements. 2D for logic is better performance wise. It might also be easier to separate the logic and the visual effects. In a future update however, we plan to integrate a voxel engine for destructible environments and there is no real high performance 2D equivalent to the 3D mesh collider which makes integrating a voxel engine using marching cubes very hard in 2D. If this is of no interest to you then we recommend you go with 2D physics. 1.3 Multiple (additive) scenes You do not have to use multiple scenes, the two scenes 2D demo scene and 3D demo scene are complete scenes ready to be played, using 2D and 3D physics respectively. In case you prefer to work with additive scenes instead these are included in the scene subfolder Additive scenes. Usage of these scenes is described below. The basic level is a simple level built to work with both 2D and 3D logic. To get a scene playing load the scenes basic level and one of 2D logic or 3D logic scenes. Introduction 2

4 Additive scene management is a new feature as of Unity version 5.1 so if you need to brush up on what it means read more here: 2 Characters The character is controlled through one script, CharacterController2D.cs. The ai (AIControls.cs) or the player (PlayerControls.cs) both call methods in that one script to interact with the world or their equipment. Character controls are entirely physics based and thus do not use root motion at all. Figure 1 The important child objects of the character prefab In Figure 1 the important child objects of the character prefab are displayed. Their main responsibilities are: Character - Parent object, contains most of the logic scripts Character model - Display the character EthanSkeleton - Contains the ragdoll and the skeleton hierarchy Blood 1 - Particle system for splashing blood when getting hit Minimap marker - A sprite renderer that displays the character on the minimap Character data canvas - A world space canvas that displays meters for health and reload progress Characters 3

5 Figure 2 The components of the character parent object. Some of their responsibilities are described in further detail below. 2.1 Creating different looking characters There is a prefab for characters in the prefab folder called Character. If you want to change the character model, then you should copy this prefab and change the child object Character model to look the way you want. Note that some manual work will be needed, you will need to set the variables of the script IK Control to the hand and head of your new character skeleton in order to have the character grab the weapon properly. You will also need to create a new ragdoll for the character model you are using. How to do that is further described here: Example: Polygon Blacksmith has a couple of cool soldiers that would work great in a sidescrolling shooter. Here we will demonstrate the steps needed to import one of those models and use as a playable character in the game. For a list of recommended assets to import see this link: Run 'n Gun asset list Steps The general steps are to import a new prefab, create a ragdoll for it and make sure that its animator and some other variables are assigned to the player logic. The order of the steps is not important. Characters 4

6 1. Duplicated the prefab of Character2D or Character3D (select it and press cmd+d or ctrl+d) 2. Import the prefab you d want to use 3. Create ragdoll for the new prefab ( see manual for instructions: ) 4. Fine tune ragdoll if needed 5. Translate, scale and rotate the new character to fit the existing character 6. Replace the Character model transform (child of the CharacterXD prefab) with the new character 7. Assign the variable Ragdoll Parent in the Take Damage Behaviour script to contain the parent transform of the ragdoll 8. The Character Model needs to have two scripts attached, IKControl.cs and FootstepSounds.cs, attach these (or copy from old character model) 9. Assign the variable Controller in the Animator script to contain the SideScrollAnimatorController. 10. Make sure the animator has Apply Root Motion set to false 11. Assign the variable Body Animator of the script CharacterController2D to contain the animator of your new character. This will make the script animate the correct model based on its running speed, jumping etc. 12. Set the variable IK in the script Inventory Behaviour to the new IKControl script you added. This will make the hands go to the handles of the weapon and the head turn towards the aiming direction when wielding weapons. 13. Set the variable Gun Parent Bone in the script Inventory Behaviour to a proper bone of the bone hierarchy. It is recommended to use hips or spine but you could also add a new child transform to any bone you like. The gun will be held at this bone and the IK script will make the hands move to the weapon handles. 14. Select the Hitboxes transform and check in the editor view that the hitboxes are ok in size. Also check them in game when crouching and jumping. The size and position of the colliders will be changed when jumping and crouching based on the variables in the script Body Part Collider that is assigned to each child of HitBoxes. They should not require much editing if the character is about the same size as the original one. If you decide to use other animations than the supplied ones then they may need more editing. The AI Controls scrip and the CharacterController2D scripts draw their detectors (detecting obstacles, ground and such) in the editor view. In order to better see the colliders it might be preferable to turn this drawing off by setting their respective dodebugdrawdetector variables to false in the inspector. 15. Assign the variable Eyes of the AI Controls script. This is use to do raycasting from the character s point of view to determine visibility. If your character does not have a transform for eyes then set it to its head transform. You could also create your own child transform for the position you want to raycast from. 16. Test playing with the character. Sometimes the IK-script will make the hands and arms a bit jerky when the IK can t make the hands reach the handles of the weapon. In those cases you may need to adjust weapon handles or the transform used as Gun Parent Bone. If the front hand can t reach the handle then move the bone backwards etc. If you get stuck then it is recommended not using unity default IK but a professional IK solution, such as Final IK by RootMotion on Unity Asset Store. It will allow you to fine tune the IK settings to make sure arms don t intersect with the body etc. while the standard Unity IK has no such specialties. Characters 5

7 Figure 3 The WW2 soldier we will import Figure 4 Step 3 completed, ragdoll generated. Note that the chest and hips colliders need adjusting Characters 6

8 Figure 5 Step 4: Ragdoll has been fine tuned. Note the hips and chest colliders have been changed Figure 6 Step 5: The new character scaled and rotated to fit the old character. Next step is to set them to the same position Characters 7

9 Figure 7 Step 6: replace the "Character model" with your new prefab, in this case "ToonSoldier_WW2.." Figure 8 Step 7: Replace ragdoll parent with the new one Characters 8

10 Figure 9 Steps 8,9 and 10 Characters 9

11 Figure 10 Step 11: Set body animator Figure 11 Step 12 and 13: Set Ik script and Gun Parent bone of the inventory behaviour Characters 10

12 Figure 12 Step 14: Check the hitboxes in the editor view (green thin outline). There is one collider each for feet, body and head. Figure 13 Debug detectors drawn. These can be turned off. Characters 11

13 Figure 14 Colliders ok Figure 15 Chest collider too high and head too low in left image. Fixed in right image. Characters 12

14 Now that we have set up working prefabs we can simply change the Character Prefab of the Team Behaviours in a scene and these will be spawned instead of the old ones. Note that teams can have different materials by setting the variable Team Colors to a specific material. If you do not want different materials just leave this variable empty and no materials will be changed. If you are using the WW2 soldiers of Polygon Blacksmith then it is now trivial to create the American version. Just duplicate the prefab and change the material and the mesh. All other settings can be left unchanged. 2.2 Inventory The InventoryBehaviour.cs script handles all things regarding inventory for the player. Note that it also is responsible for handling some interactions with the current weapon such as reloading. 2.3 AI The AIControls class represents a pretty simple minded state machine based AI. It does two things, it thinks in Think() and determines what actions to take and it acts in Act() where it send signals to CharacterController2D.cs to make the character move the way it planned when thinking. As thinking is a costly operation which may require pathfinding lots of ray casting and such Think() is put in a coroutine and only runs a few times per second. For more information about pathfinding see chapter 5. If you want the AI to tell you what it is thinking as debug messages in the console, then set the Verbose Debug variable to true in the inspector. 2.4 Who s behind the wheel? The player can be given control of a character by the TeamBehaviour.cs script. Currently this happens when the controlled character dies. You could edit the script to allow for changing characters through some other measure if you like. 2.5 What does Seeker do? Seeker is the component that finds a path in the pathfinding graph that should span the world. Read more about it in chapter 5. Characters 13

15 3 Guns You want more guns, right? A weapon needs to things: A prefab and a data scriptable object that describes it. The prefab is responsible for things like how the weapon looks and sounds and the scriptable object is responsible for pure data like how many bullets does it have in a mag and how much damage does it cause. The idea here is that you could reuse the prefab for different types of weapons if you like where you could have the same prefab but have it cause different amount of damage depending on weapon quality or something like that. 3.1 Procedure for creating a new weapon Right click in the project view, select Create -> Firearm data. This will create a new Firearm Data scriptable object. Figure 16 Create Firearm Data scriptable object Guns 14

16 Figure 17 Edit firearm data Next, duplicate one of the already existing weapon prefabs or create your own. If you create your own, then assign the same components and children as the existing prefabs. Make sure to assign the prefab in the firearm data scriptable object. Figure 18 Hierarchy of a firearm prefab We use inverse kinematics (IK) to determine the position of the character s hands. This way we do not need a specific animation for every weapon we create. The Firearm Behaviour script needs a reference to the hands if you want their position to be controlled. If you do not, then leave the references to null and the inverse kinematics will ignore them and let the normal animation run its course. This way you could assign the right hand only if you want the character to only hold a weapon with one hand. The muzzle offset forward is used to make the character point is head a few meters in front of the barrel to make it look like he is aiming. If you do not want this behavior, then just do no assign that variable. It should be pointed out that the IK of the Unity Engine are not fantastic. If you want better IK it is strongly recommended that you have a look at the package Final IK by Root Motion ( in the asset store. The principle will still be the same, the end result will just look a lot better. Guns 15

17 Figure 19 Example of the components of a firearm prefab Guns 16

18 3.2 Bullet manager As there will be tons of bullets flying in this type of game it is important to keep down garbage generation. If we created and destroyed game objects for every time a trigger was pulled the garbage collector would be up in its neck in just bullets. Therefore, when a bullet disappears for some reason (maybe entering a body or striking a wall) it is recycled by the Bullet Manager and will be reused next time someone fires a weapon. Note that if you want to add a new type of bullet, like exploding rockets, arrows or thrown axes, then you should add a new object pool to the bullet manager for that type of bullet. If this is a new concept to you then you may want to read up on it: 4 World Pathfinding for jumping platforms is more complex that one would think. In this system we have tried to create as simple a system as possible for this. In order to allow for pathfinding, we must build the world in such a way that it can be interpreted by the pathfinder. Specifically, you should have a look at the building blocks in the Prefabs/LevelConstruction-folder. Note that the Viking Prototype Cube-prefab has a script called GenerateWaypoints.cs. This script uses the two variables Start Point an End Point and places waypoints along a line between these two points for the pathfinder to use. This is to let the pathfinder figure out where there are platforms that characters can run on. If you want to place something in the world that the ai should not run on, then you do not need this script. You could instead manually place Waypoint-prefabs anywhere you want the AI to be able to run but this becomes tedious fast Make sure that the waypoint intervals are shorter than the Max Distance variables set in the Jump Graph of the A* pathfinder or they will not be connected. Don t make them too short or there will be too many connections in the graph to make it efficient. Note that the shader used by the material for the construction prefabs allows you to rescale the objects and maintain texture uvs in world coordinates. You can probably use this using your own prefabs and textures as well. World 17

19 Figure 20 A Viking Prototype Cube placed in the editor Figure 21 The same cube with the scale along x-axis increased. Note how the texture adapts according to world coordinates. World 18

20 Figure 22 The same cube now during gameplay. Note how waypoints have been automaticlly placed along its walkable surface. If you look closely you can see how the red lines show traversable edges in the graph. 5 Pathfinding Aron Granberg has kindly permitted the free version of his awesome A-star Pathfinding Project to be included in this project. If you own the pro-version of that asset and want to use it instead, then read the instructions in the JumpGraph.cs-script. For more information about the A-star Pathfinding Project check out or A* pathfinding project on Asset Store If you replace the pathfinding asset included then you must make sure that AstarData.cs look like this around line 50: #if ASTAR_FAST_NO_EXCEPTIONS UNITY_WINRT UNITY_WEBGL /** Graph types to use when building with Fast But No Exceptions for iphone. * If you add any custom graph types, you need to add them to this hard-coded list. */ public static readonly System.Type[] DefaultGraphTypes = new System.Type[] { typeof(gridgraph), typeof(pointgraph), typeof(navmeshgraph), typeof(jumpgraph), Pathfinding 19

21 #endif }; Sidescrolling 2.5D Shooter typeof(gridjumpgraph), This is to ensure that the types JumpGraph and GridJumpGraph are included. In this project we have implemented two new types of graphs for pathfinding where actors need to jump between platforms. These are the JumpGraph and the GridJumpGraph.You can find the implementation details in the path Assets\VikingCrew\2.5D Sidescrolling Shooter\Scripts\Pathfinding. The JumpGraph introduces two new features; a waypoint node will only be connected to a node above it if it is no higher than the variable Max Jump Height of the Jump Graph in the inspector. Vice versa there is a max drop height that characters will allow to avoid jumping from too high heights. Nodes are also only connected if there is no 2D collider between them. Pathfinding 20

22 Figure 23 You can set variables like max jump height in the inspector. Note that the graph will use both jump and drop height and max distance to determine connectivity. The GridJumpGraph instead uses a grid graph and samples points on that grid. Each point connectivity is also based on jump height etc. It is used in e.g. the Voxel test scene where each voxel corresponds to a tile in the grid graph. Note that if characters have different jump heights the AI will need to use the lowest jumping height available to calculate paths or one of your lower jumping characters might get stuck. If you have very varying jump heights it might make sense to create several different graphs, one for each jump height. Pathfinding 21

23 6 Integrations This package has currently two integrations. One is the open sourced voxel engine Cubiquity. The other one is Toon Soldiers WW2 by Polygon Blacksmith. 6.1 Integration instructions Cubiquity The Cubiquity engine is open sourced and can thus be included in full. It does not depend on any other assets and can thus be imported as is Toon Soldiers WW2 This integration requires that you already own Toon Soldiers WW2 by Polygon Blacksmith. Make sure to first import that package. Then import the integration package. You ll get two prefabs of soldiers that can be used instead of the standard ones. 6.2 Other integrations? Do you have other suggestions of packs that should be integrated? Let me know and I ll take care of it! Integrations 22

24 7 Planned features There are many ideas for future updates. Some of them are: Wall climb Wall jump Jetpack Grapple hook Weapon recoil and reloading animations More guns: Machine guns, rocket launchers, hand grenades etc. X-Box (etc.) controller support More object pools for characters, weapons etc. for increased performance Multiplayer, local or online UMA 2.0 integration Playmaker support Integration of other packages such as Final IK, PuppetMaster, DunGen etc. There is a fine balance when adding features in keeping the package clean and simple to use and the awesomeness new features would bring. If you as user or presumptive customer have any feelings that you d like to share, then please do so through either of the channels mentioned in the introduction. Planned features 23