Exporting

Overview

Now that you have a working game, you probably want to share your success with others. However, it’s not practical to ask your friends to download Godot just so they can open your project. Instead, you can export your project, converting it into a “package” that can be run by anyone.

The way you export your game depends on what platform you are targeting. In this tutorial, you’ll learn how to export the “Dodge the Creeps” game for a variety of platforms. First, however, we need to make some changes to the way the game works.

Note

If you haven’t made “Dodge the Creeps” yourself yet, please read Your first game before continuing with this tutorial.

Preparing the project

In “Dodge the Creeps” we used keyboard controls to move the player’s character. This is fine if your game is being played on a PC platform, but on a phone or tablet, you need to support touchscreen input. Because a click event can be treated the same as a touch event, we’ll convert the game to a click-and-move input style.

By default Godot emulates mouse input from touch input. That means if anything is coded to happen on a mouse event, touch will trigger it as well. Godot can also emulate touch input from mouse clicks, which we will need to be able to keep playing our game on our computer after we switch to touch input. In the “Project Settings” under Input Devices and Pointing, set Emulate Touch From Mouse to “On”.

../../_images/export_touchsettings.png

We also want to ensure that the game scales consistently on different-sized screens, so in the project settings go to Display, then click on Window. In the Stretch options, set Mode to “2d” and Aspect to “keep”.

Since we are already in the Window settings, we should also set under Handheld the Orientation to “portrait”.

../../_images/export_handheld_stretchsettings.png

Next, we need to modify the Player.gd script to change the input method. We’ll remove the key inputs and make the player move towards a “target” that’s set by the touch (or click) event.

Here is the full script for the player, with comments noting what we’ve changed:

GDScript

C#

  1. extends Area2D
  3. signal hit
  5. export var speed = 400
  6. var screen_size
  7. # Add this variable to hold the clicked position.
  8. var target = Vector2()
  10. func _ready():
  11.     hide()
  12.     screen_size = get_viewport_rect().size
  14. func start(pos):
  15.     position = pos
  16.     # Initial target is the start position.
  17.     target = pos
  18.     show()
  19.     $CollisionShape2D.disabled = false
  21. # Change the target whenever a touch event happens.
  22. func _input(event):
  23.     if event is InputEventScreenTouch and event.pressed:
  24.         target = event.position
  26. func _process(delta):
  27.     var velocity = Vector2()
  28.     # Move towards the target and stop when close.
  29.     if position.distance_to(target) > 10:
  30.         velocity = target - position
  32. # Remove keyboard controls.
  33. #    if Input.is_action_pressed("ui_right"):
  34. #       velocity.x += 1
  35. #    if Input.is_action_pressed("ui_left"):
  36. #        velocity.x -= 1
  37. #    if Input.is_action_pressed("ui_down"):
  38. #        velocity.y += 1
  39. #    if Input.is_action_pressed("ui_up"):
  40. #        velocity.y -= 1
  42.     if velocity.length() > 0:
  43.         velocity = velocity.normalized() * speed
  44.         $AnimatedSprite.play()
  45.     else:
  46.         $AnimatedSprite.stop()
  48.     position += velocity * delta
  49.     # We still need to clamp the player's position here because on devices that don't
  50.     # match your game's aspect ratio, Godot will try to maintain it as much as possible
  51.     # by creating black borders, if necessary.
  52.     # Without clamp(), the player would be able to move under those borders.
  53.     position.x = clamp(position.x, 0, screen_size.x)
  54.     position.y = clamp(position.y, 0, screen_size.y)
  56.     if velocity.x != 0:
  57.         $AnimatedSprite.animation = "walk"
  58.         $AnimatedSprite.flip_v = false
  59.         $AnimatedSprite.flip_h = velocity.x < 0
  60.     elif velocity.y != 0:
  61.         $AnimatedSprite.animation = "up"
  62.         $AnimatedSprite.flip_v = velocity.y > 0
  64. func _on_Player_body_entered( body ):
  65.     hide()
  66.     emit_signal("hit")
  67.     $CollisionShape2D.set_deferred("disabled", true)
  1. using Godot;
  2. using System;
  4. public class Player : Area2D
  5. {
  6.     [Signal]
  7.     public delegate void Hit();
  9.     [Export]
  10.     public int Speed = 400;
  12.     private Vector2 _screenSize;
  13.     // Add this variable to hold the clicked position.
  14.     private Vector2 _target;
  16.     public override void _Ready()
  17.     {
  18.         Hide();
  19.         _screenSize = GetViewport().Size;
  20.     }
  22.     public void Start(Vector2 pos)
  23.     {
  24.         Position = pos;
  25.         // Initial target us the start position.
  26.         _target = pos;
  27.         Show();
  28.         GetNode<CollisionShape2D>("CollisionShape2D").Disabled = false;
  29.     }
  31.     // Change the target whenever a touch event happens.
  32.     public override void _Input(InputEvent @event)
  33.     {
  34.         if (@event is InputEventScreenTouch eventMouseButton && eventMouseButton.Pressed)
  35.         {
  36.             _target = (@event as InputEventScreenTouch).Position;
  37.         }
  38.     }
  40.     public override void _Process(float delta)
  41.     {
  42.         var velocity = new Vector2();
  43.         // Move towards the target and stop when close.
  44.         if (Position.DistanceTo(_target) > 10)
  45.         {
  46.             velocity = _target - Position;
  47.         }
  49.         // Remove keyboard controls.
  50.         //if (Input.IsActionPressed("ui_right"))
  51.         //{
  52.         //    velocity.x += 1;
  53.         //}
  55.         //if (Input.IsActionPressed("ui_left"))
  56.         //{
  57.         //    velocity.x -= 1;
  58.         //}
  60.         //if (Input.IsActionPressed("ui_down"))
  61.         //{
  62.         //    velocity.y += 1;
  63.         //}
  65.         //if (Input.IsActionPressed("ui_up"))
  66.         //{
  67.         //    velocity.y -= 1;
  68.         //}
  70.         var animatedSprite = GetNode<AnimatedSprite>("AnimatedSprite");
  72.         if (velocity.Length() > 0)
  73.         {
  74.             velocity = velocity.Normalized() * Speed;
  75.             animatedSprite.Play();
  76.         }
  77.         else
  78.         {
  79.             animatedSprite.Stop();
  80.         }
  82.         Position += velocity * delta;
  83.         // We still need to clamp the player's position here because on devices that don't
  84.         // match your game's aspect ratio, Godot will try to maintain it as much as possible
  85.         // by creating black borders, if necessary.
  86.         // Without clamp(), the player would be able to move under those borders.
  87.         Position = new Vector2(
  88.             x: Mathf.Clamp(Position.x, 0, _screenSize.x),
  89.             y: Mathf.Clamp(Position.y, 0, _screenSize.y)
  90.         );
  92.         if (velocity.x != 0)
  93.         {
  94.             animatedSprite.Animation = "walk";
  95.             animatedSprite.FlipV = false;
  96.             animatedSprite.FlipH = velocity.x < 0;
  97.         }
  98.         else if(velocity.y != 0)
  99.         {
  100.             animatedSprite.Animation = "up";
  101.             animatedSprite.FlipV = velocity.y > 0;
  102.         }
  103.     }
  104.     public void OnPlayerBodyEntered(PhysicsBody2D body)
  105.     {
  106.         Hide(); // Player disappears after being hit.
  107.         EmitSignal("Hit");
  108.         GetNode<CollisionShape2D>("CollisionShape2D").SetDeferred("disabled", true);
  109.     }
  110. }

Setting a main scene

The main scene is the one that your game will start in. In Project -> Project Settings -> Application -> Run, set Main Scene to “Main.tscn” by clicking the folder icon and selecting it.

Export templates

In order to export, you need to download the export templates from the http://godotengine.org/download. These templates are optimized versions of the engine without the editor pre-compiled for each platform . You can also download them in Godot by clicking on Editor -> Manage Export Templates:

../../_images/export_template_menu.png

In the window that appears, you can click “Download” to get the template version that matches your version of Godot.

../../_images/export_template_manager.png

Note

If you upgrade Godot, you must download templates that match the new version or your exported projects may not work correctly.

Export presets

Next, you can configure the export settings by clicking on Project -> Export.

Create a new export preset by clicking “Add…” and selecting a platform. You can make as many presets as you like with different settings.

../../_images/export_presets_window.png

At the bottom of the window are two buttons. “Export PCK/ZIP” only creates a packed version of your project’s data. This doesn’t include an executable so the project can’t be run on its own.

The second button, “Export Project”, creates a complete executable version of your game, such as an .apk for Android or an .exe for Windows.

In the “Resources” and “Features” tabs, you can customize how the game is exported for each platform. We can leave those settings alone for now.

Exporting by platform

In this section, we’ll walk through the process for each platform, including any additional software or requirements you’ll need.

PC (Linux/macOS/Windows)

Exporting PC platforms works the same across the three supported operating systems. Open the export window and click “Add..” to create the preset(s) you want to make. Then click “Export Project” and choose a name and destination folder. Choose a location outside of your project folder.

Click “Save” and the engine will build the export files.

Note

When exporting for macOS, if you export on a macOS computer, you’ll end up with a .dmg file, while using Linux or Windows produces a .zip. In either case, the compressed file contains a macOS .app that you can double-click and run.

Note

On Windows, if you want your exported executable to have a different icon than the default one, you need to change it manually. See: Changing application icon for Windows.

Android

Tip

Mobile devices come with a wide variety of capabilities. In most cases, Godot’s default settings will work, but mobile development is sometimes more art than science, and you may need to do some experimenting and searching for help in order to get everything working.

Before you can export your project for Android, you must download the following software:

When you run Android Studio for the first time, click on Configure -> SDK Manager and install “Android SDK Platform Tools”. This installs the adb command-line tool that Godot uses to communicate with your device.

Next, create a debug keystore by running the following command on your system’s command line:

  1. keytool -keyalg RSA -genkeypair -alias androiddebugkey -keypass android -keystore debug.keystore -storepass android -dname "CN=Android Debug,O=Android,C=US" -validity 9999

Click on Editor -> Editor Settings in Godot and select the Export/Android section. Here, you need to set the paths to the Android SDK applications on your system and the location of the keystore you just created.

../../_images/export_editor_android_settings.png

Now you’re ready to export. Click on Project -> Export and add a preset for Android (see above). Select the Android Presets and under Options go to Screen and set Orientation to “Portrait”.

Click the “Export Project” button and Godot will build an APK you can download on your device. To do this on the command line, use the following:

  1. adb install dodge.apk

Note

Your device may need to be in developer mode. Consult your device’s documentation for details.

If your system supports it, connecting a compatible Android device will cause a “One-click Deploy” button to appear in Godot’s playtest button area:

../../_images/export_android_oneclick.png

Clicking this button builds the APK and copies it onto your device in one step.

iOS

Note

In order to build your game for iOS, you must have a computer running macOS with Xcode installed.

Before exporting, there are some settings that you must complete for the project to export successfully. First, the “App Store Team Id”, which you can find by logging in to your Apple developer account and looking in the “Membership” section.

You must also provide icons and splash screen images as shown below:

../../_images/export_ios_settings.png

Click “Export Project” and select a destination folder.

Once you have successfully exported the project, you’ll find the following folders and files have been created in your selected location:

../../_images/export_xcode_project_folders.png

You can now open the project in Xcode and build the project for iOS. Xcode build procedure is beyond the scope of this tutorial. See https://help.apple.com/xcode/mac/current/#/devc8c2a6be1 for more information.

HTML5 (web)

Click “Export Project” on the HTML5 preset. We don’t need to change any of the default settings.

When the export is complete, you’ll have a folder containing the following files:

../../_images/export_web_files.png

Viewing the .html file in your browser lets you play the game. However, you can’t open the file directly, it needs to be served by a web server. If you don’t have one set up on your computer, you can search online to find suggestions for your specific OS.

Point your browser at the URL where you’ve placed the html file. You may have to wait a few moments while the game loads before you see the start screen.

../../_images/export_web_example.png

The console window beneath the game tells you if anything goes wrong. You can disable it by setting “Export With Debug” off when you export the project.

../../_images/export_web_export_with_debug_disabled.png

Note

While WASM is supported in all major browsers, it is still an emerging technology and you may find some things that don’t work. Make sure you have updated your browser to the most recent version, and report any bugs you find at the Godot GitHub repository.