-
Notifications
You must be signed in to change notification settings - Fork 65
Testing the adventure
There are several ways to test a game inside the Blade Engine:
The test verb is executed when testing a scene using the 'Test' button inside the editor. The test verb is executed before the init scene verb and can be used to set up the scene for testing.
When the Blade Engine is in debug mode ('d' key) an icon in the main screen allows to enter in the debug screen.
The debug screen provides the following features:
- set the game speed
- play a recorded game or start to record a game
- go to any scene of the game
- run/stop the tester bot
To ease the testing process, the Blade Engine allows to record a game. A recorded game can be played later to check that the game is not broken.
Recorded games are saved in the project user folder but can be moved to the 'test' folder inside the game 'assets'. Through the debug screen recorded games inside the user folder or inside the 'test' folder can be played.
The Tester Bot can play the game automatically executing verbs over objects randomly. It is useful as an automatic tester, you can let the Tester Bot playing the game or an specific scene for hours.
-
The Adventure
- Project structure
- Working with assets
- Multiple resolutions
- Chapters
-
Scenes
- Actor layers
- Walk Zones and obstacles
- Scene music
-
Actors
- Background Actors
- Sprite Actors
- Character Actors
- Obstacle Actors
- Anchor Actors
-
Animations
- Image renderer
- Atlas renderer
- Spine renderer
- 3D renderer
- Stand, Walking and Speak animations
- Dialogs
-
Verbs and Actions
- Control actions
- Sounds
-
Customizing the game UI
- Changing the UI Icons
- Customizing the Inventory
- Customizing the Game Screens
- Creating custom actions
-
Testing the adventure
- The test verb
- Recording and playing games
- The Tester Bot
- I18N and text translations