In this course, you will learn the basics of script creation in ACTION GAME MAKER.
In the fifth session, we will create scene transitions.
Continue using the project from Sessions 1 to 4.
Please open the project and get ready.
Open a new Scene tab and create a game scene. Once created, save it with the name “title”.
As a child of the UI node, add a ColorRect node.
Expand the ColorRect so that it covers the menu display area.
Since white is too bright, set the Color property to black.
As a child of the UI node, add a Label node. This is a node for drawing text.
Enter “SAMPLE GAME PROJECT PRESS A START” in the Text field of the properties.
Next, create a new LabelSettings and set the font size to 80.
Set the horizontal alignment to center and adjust the Label’s position so it is roughly in the middle.
Although it is very simple, the title scene is now complete. Change to Scene Transition in the top tab.
Place the title.tscn created earlier to the left of game_scene, and link from title to game_scene just like with VisualScript.
Set the transition condition (Switching Conditions) to trigger when the A button is pressed.
For the transition effect, set both Before Transition and After Transition to BLACK.
Right-click on Title and set it as the Start Scene.
Try running a test play. If configured correctly, the title scene should appear, and pressing the A button or the Z key should transition to the game scene.
By pressing the 
icon near the Test Play button or the F6 key while a specific scene is open, you can run the current scene.
However, in this state, scene transitions may not work correctly. Therefore, if you want to test including scene transitions, we recommend setting the scene you wish to test as the Start Scene in the Scene Transition tab.
Switch to the game_scene tab. Create a Portal as a child of BaseLayer.
Configure the portal properties. Set it to trigger when entering from the right. Leave the destination scene path blank for now and proceed.
Set both the entrance effect type and exit effect type to BLACK.
Add 2 to the CollisionMask. This is necessary because the sample player’s layer is set to 2, so a mask of 1 alone won’t detect collisions.
Move the Portal’s coordinates to the right edge of the stage. At this time, please move the Portal node itself, not the PortalCollision. The position of the Portal node will be the destination.
The PortalCollision is too large, so let’s reduce its width. If it’s too big, collisions might trigger unexpectedly.
Next, create the destination scene. In the file system, duplicate game_scene.tscn to create game_scene2.tscn.
Open game_scene2 and delete the player. If not deleted, the player will split into two.
Move the Portal node to the left edge of the map.
Correct the position of PortalCollision. After moving through the portal, the size of the portal collision was changed, so it should be misaligned. In this image, the collision is on the right side of the Portal node, so move it to the left side.
Change the portal properties. Change the input condition from right to left, and set game_scene.tscn as the target scene. Then, you can select the portal in game_scene; select it.
Return to the game_scene tab. Similarly, set game_scene2.tscn in the scene path and select the portal.
Let’s test play. If configured correctly, you should be able to freely move between the two scenes.
That concludes the content of the Script Course tutorial.
The content explained in the tutorial is only basic.
In ACTION GAME MAKER’s visual scripting, various movements can be created by combining conditions and actions.
Depending on your creativity, someone might create something our development team never imagined.
If you come up with ideas, please share them on SNS or in the guild.
1. Graphics Course
This course is for those who want to animate characters they have drawn.
3. Expression Enhancement Course
This course is for those who want to add cool, Godot-style expressions.
