• Introduction
• What is a point-and-click Game?
• What is Escoria?
• Requirements
• Basic Concepts in Godot
• Basics Concepts of Escoria
• About this book
• First Quick Game with Escoria
• About the example game
• Our project planning
• How to start your Escoria project
• Create your first scene
• Testing your Game
• Create Actions
• Escoria Fundamentals
• The Items
• Main Scene
• The Esc scripting language
• Inventory
• Verbs & Actions
• Speech Text
• Dialog interface
• Main Player
• What you need to know as an artist
• Artwork Import
• Scene composition
• Animations
• Music and sound effects
• Terrain: Light and Perspective
• What you need to know as a game designer
• Global states and saving
• Structure
• Booleans and conditions
• Instructions and commands
• Dialog trees
• Internationalization
• Audio speech files
• What you need to know as a programmer
• Game menus
• Implementing savegames
• Optimization
• How to publish
• Export your game

Testing your Game

Thanks to Godot’s ability to run any scene at any time without long waiting times, you are able to easily and incrementally test your changes.

You will find all the necessary tools to test your game in the top-middle part of Godot’s interface (here highlighted in the screenshot).

Each button of this panel is about testing your game. There is also key bindings defined for each of them.

1. The first one (play button), also accessible via the F5 key, will run the game’s default scene, effectively running the game as if it were started by a regular user. The default scene is the one defined in the Scene > Project settings menu, in the Applicationsection, main_scene property.
2. The second button (pause button) is to pause the scene while you’re testing it, you can press F7 to get the same effect.
3. The square button is to stop testing the scene and resume editing it, use F8 inside the game or the editor to achieve the same effect.
4. The fourth one, looking like a clapper-board with a play symbol inside, that you can also use with the F6 key, is similar to the previous play but it runs the scene you’re currently editing instead of the default game scene. It’s really useful as you don’t want to start the whole game each time you want to test a level.
5. The fifth one is about running a scene chosen from a menu listing all the scenes of your project.
6. The last one is a menu containing various advanced debugging options.

The whole point of these tools is to enable you to quickly see your changes in game.

If you’re a graphical artist on the project, you can integrate the assets yourself, compose the scene to your liking, and see the result in game without ever needing to ask a developer.