In this tutorial we’ll set up schematics to animate the start and end of our battles.

Our battles take place in a separate battle scene – i.e. we need to remember the scene and position the player was before loading into the battle scene, or we can’t return there after the battle.

Additionally, which battle scene is used depends on the scene the player is in, so we’ll use a string variable that’ll contain the battle scene (we’ll set the variable later in our scenes, not in the schematics here).

We’ll set up:

• game state
• camera position
• battle start schematic
• battle end schematic for victory (collecting loot)
• battle end schematic for lost (game over)

Since we don’t use escaping in this game, we don’t need to set up a separate battle end schematic for this battle outcome. Let’s get to it!

Game State #

We’ll begin with setting up a game state – we’ll use this later as a condition for displaying the player’s battle HUD. Our battle start/end schematics will change that game state, giving us exact control over when the HUD should be visible.

Game states are simple states that are either active or inactive. They can be used as conditions for other things and also be changed automatically. A new project already comes with some game states set up, e.g. to check if player controls are blocked. Learn more about game states in this Makinom documentation.

Open the Makinom editor, navigate to Game > Game States and add a new game state.

Camera Position #

Camera positions are used to change a camera’s position, rotation or field of view based on a target, e.g. showing the front of a game object. We’ll use one to zoom in at the start of a battle, before transitioning to the battle scene.

Beside using the Makinom editor, you can also create camera positions using the scene wizard via a camera and a game object in your scene.

Navigate to Game > Camera Positions, we’ll change the Default position.

0: Battle Intro Zoom #

We’ll use this camera position in a battle start schematic to zoom in (high field of view) and do a camera spin.

Camera Settings #

Position #

Rotation #

Field of View #

Save Changes #

That’s it for now in the regular editor – before changing to Schematics we need to save our changes.

Save the changes using the Save Settings button at the bottom of the editor.

Battle Start Schematic #

Now, we’ll set up the schematic animating our battle start.

We’ll remember the currently playing music (including it’s track position), the scene and position of the player and use the camera position to zoom in before loading into the battle scene.

Navigate to Schematics.

Settings #

We’ll block player/camera controls during the start schematic.

Actors #

We’ll add an actor to have access to the Battle Arena – we’ll use it to focus the camera on the battle instead of the player.

Store Music #

Add Node > Audio > Music > Store Music

We store the currently playing music to be able to resume playing it after the battle (i.e. in a battle end schematic).

The default setup of the node should usually already be what we need. Please note that this depends on which music channel your music is playing on.

Play Sound (Channel) #

Add Node > Audio > Audio > Play Sound (Channel)

This node plays a sound on a sound channel instead of a game object in the scene.

Store Scene #

Add Node > Game > Scene > Store Scene

Stores the current scene and player position.

No further settings needed.

Change Camera Position #

Add Node > Game Object > Camera > Change Camera Position

Now we’ll zoom in by fading to the camera position.

Wait #

Add Node > Base > Wait

We’ll wait for a part of the zoom in before loading into the battle scene.

Load Scene #

Add Node > Game > Scene > Load Scene

Now we’ll load the scene the battle should take place in.

As said above, we’ll use the value of a string variable to hold the scene name.

Target Scene 0 #

The Target Scene settings define the scene that will be loaded and where to spawn the machine (e.g. via spawn point).

Screen Fade Settings #

We handle fading out the screen here.

Place At Spots #

Add Node > Battle > Spawn > Place At Spots

This’ll place the already spawned combatants at their battle spots.

This is probably not needed in a this battle start schematic since no spawned combatants should be there – but it doesn’t hurt to have it.

Spawn Battle Combatants #

Add Node > Battle > Spawn > Spawn Battle Combatants

This’ll spawn all combatants participating in battle.

Change Music #

Add Node > Audio > Music > Change Music

Now we change the music to our battle music.

Change Game State #

Add Node > Game > Game > Change Game State

We’ll activate our new game states to show the battle HUD (which we’ll set up later).

Block Camera Control #

Add Node > Input > Block Camera Control

We’ll now unblock the camera control – we need to do this before we set the camera’s target, and also give the camera control time to update before fading in the screen.

Camera Control Target #

Add Node > Input > Camera Control Target

This node changes the current target of the camera control. We’ll target the Battle Arena actor.

Please note that this only works for the built-in controls or custom controls that are based on them.

Fade Screen #

Add Node > Animation > Fade > Fade Screen

And finally, we’ll fade in the screen.

And that’s it for the schematic. Click on Save Schematic to save it, e.g. as BattleStart.

Victory Schematic #

This battle end schematic is used when the player won the battle. We’ll play the victory music, collect our loot and return to the stored scene.

Create a new schematic.

Settings #

Change Music #

Add Node > Audio > Music > Change Music

Play the victory music.

Wait #

Add Node > Base > Wait

Wait a second.

Collect Battle Gains #

Add Node > Battle > Gains > Collect Battle Gains

This node is used to collect experience and loot from a battle – we’ll also display the loot dialogue.

Wait #

Add Node > Base > Wait

We’ll wait a short time before returning to the stored scene.

Change Music #

Add Node > Audio > Music > Change Music

Now we’ll fade back to the stored music (we stored it in the battle start schematic).

Change Game State #

Add Node > Game > Game > Change Game State

We’ll inactivate the new game state to hide the HUD again.

Load Scene #

Add Node > Game > Scene > Load Scene

We’ll load the scene that was previously stored.

And that’s it for the schematic. Click on Save Schematic to save it, e.g. as BattleEndVictory.

Defeat Schematic #

This battle end schematic is used when the player lost the battle. We’ll play the lost music and call game over.

Create a new schematic.

Settings #

Change Music #

Add Node > Audio > Music > Change Music

Play the victory music.

Change Game State #

Add Node > Game > Game > Change Game State

We’ll inactivate the new game state to hide the HUD again.

Wait #

Add Node > Base > Wait

We’ll wait for 3 seconds.

Game Over #

Add Node > Game > Game > Game Over

This node will call game over according to the Game Over Settings (in Game > Game Settings).

No further settings.

And that’s it for the schematic. Click on Save Schematic As … to save it, e.g. as BattleEndDefeat.

Using the Schematics #

With our battle start/end schematics set up, we’ll now return to our Turn Based battle system to use the schematics.

Navigate to Battles > Battle System and select the Turn Based battle system.

Base Settings > Battle Start/End Schematics #

We’ll use the schematics we’ve set up.

Save Changes #

And that’s it!

Save the changes using the Save Settings button at the bottom of the editor.

 

Next, we’ll finally get to adding battles to our game.