Skip to content
Docs

Common editor problems

Causes and fixes for the most common stumbles of the editor 0.4.0, from the window that does not open and the bot that does not finish to where your projects ended up after updating.

DescribesEditor 0.4.0 For creating without programming

On this page

Each problem comes with its cause and its fix. If yours is not here, look first at the editor's Problems panel: it explains what it finds and has a Take me there button that opens the place.

The editor does not open on Linux#

Cause. The editor uses the system's web component to draw its window. Editor 0.4.0 needs version 4.1 of that component, as well as GTK 3. If they are missing, the program does not start.

Fix. Install the libraries with your distribution's package manager.

DistributionPackages
Debian and Ubuntulibwebkit2gtk-4.1-0 and libgtk-3-0
Fedorawebkit2gtk4.1 and gtk3

The full steps are in Download and install.

Windows warns that the file is not safe#

Cause. The files of this version are not signed, and Windows warns you when you open an unsigned program.

Fix. Download the editor only from the official page and follow the steps in Download and install. The installer asks for administrator permissions.

If the window never shows, the Windows WebView2 component may be missing. Windows 11 already includes it.

macOS does not let you open the editor#

Cause. The editor for macOS is not signed with a developer account and did not go through the system's review, so the first time macOS refuses to open it with a double click.

Fix. The first time only, use one of these three ways:

  1. Right-click the application and choose Open.
  2. Or go to System Settings > Privacy & Security and press Open Anyway.
  3. Or, in the Terminal, remove the quarantine mark:
sh
xattr -dr com.apple.quarantine "/Applications/Green Games Studio.app"

After that it opens normally. The editor needs macOS 12 or later. The Intel version also runs on computers with Apple Silicon.

The bot does not finish#

Symptom. Test with bot says "Test failed", with a reason like "The bot got stuck on step 1 of 1 (go to zone "meta"): it did not reach the destination…".

Cause. The bot walks around walls and gaps by itself, but it does not dodge hazards or plan jumps. If between it and its goal there is a danger zone, a platform you have to jump to or a moving platform, it does not get there.

Fix.

  1. Press See where on the match that failed: the camera goes to the place where the bot ended up.
  2. In Rules, Test bot section, mark steps for it: select a piece where the way is clear and press + Go to selection.
  3. If it has to jump, untick go around on that step.
  4. Test again.

In a side-view game, the panel also has a collapsible help about jumps. It is all in Test bot.

Export is blocked#

Symptom. The Export game dialog stops at the first step, in red, and says "The game has N errors to fix. They are under Problems, with a button to jump to each."

Cause. The game has errors. While it has them, the .ggx is not written.

Fix. Close the dialog, open Problems and press Take me there on each error. If the errors are in code you wrote yourself and you do not know how to fix them, Ctrl+Z undoes until they disappear.

If what fails is the second step, the bot's, sort out the test first: see The bot does not finish.

A live match cuts off#

Symptom. You are playing with Play and the match stops by itself, without you having lost.

Cause. An internal physics failure, which is infrequent. It is not an error in your game and it does not repeat in the same place.

Fix. Press Restart or Play again.

Test with bot and Export are not affected: if one of their matches dies from that failure, they repeat it by themselves.

The assistant does not answer or there is no model#

Symptom. The assistant replies that it does not understand, takes a long time, or Settings says there is no model available.

Cause. It depends on what the assistant is working with:

SituationWhat happens
It is in basic mode, with no modelIt is not artificial intelligence: it recognizes a list of common requests. It does not understand the rest, and says so.
You chose a model on your PC, but it is not installed or not runningThe editor explains it and handles the request without a model.
You chose the cloudThe Green Games cloud service is not published yet.
The package does not include the AI layerThe standalone Windows .exe includes only the basic assistant, and says so. The Windows installer and portable zip, the Linux package and the macOS ones do include it.

Fix. Open Settings and look at AI status on this computer: it says what is connected and what is missing. Meanwhile, use requests the basic assistant understands, such as "add 5 coins", "place a tree" or "change the colors to sunset".

What each mode does, what is installed separately and how to choose is in Assistant.

A model, a texture or a sound does not get into the game#

Symptom. Problems shows an error with a code that starts with GB7, such as "The scene has too many models", and Export stops at Validate the game.

Cause. A model, a texture or a sound goes over one of the game's limits, or a piece names one that does not exist. The Game card, under Package limits, marks in red the one that was exceeded.

Fix. Press Take me there on the problem: the title says in words what is wrong and the message says how much there is and what the maximum is. Use fewer copies, a lighter model or a smaller texture; the importer reduces triangles and textures with its conversion options. The limits are in Models in the scene and each code, in The validator.

A workshop document does not open#

Symptom. Problems shows a warning with the code TLL: a document in taller/ could not be read, or a drawing, a model or a map could not be exported.

Cause. The file is damaged, for example because it was edited by hand, or what was drawn does not fit the game format (a sprite bigger than 64 x 64 pixels, for example).

Fix. The rest of the project opens anyway. If the document is damaged, fix it with a text editor or delete it, as the warning says. If it could not be exported, the message says why; open the document and make it smaller. See Asset workshop.

It could not save#

Symptom. A notice says the project could not be saved and offers Retry.

Cause. The editor cannot write in the project folder, for example because it has no permission.

Fix. Your work is still open in the editor: do not close it. Fix the folder's permission and press Retry or Ctrl+S. The editor does not let you close the project without asking.

Texts in Problems#

Since editor 0.4.0, the explanations in the Problems panel come out in the language of the interface, also the place of the problem ("line 98, column 1"). The test bot's reasons come out like that since 0.3.0, with the step said in words, such as go to zone "meta". See Test bot.

Where my projects are#

WhatWhere
The projectsGreen Games/proyectos/<id>, in your home folder.
Exported gamesGreen Games/exportados/<id>.ggx.
The ones you sent to the trashGreen Games/papelera/.

The full path of the projects folder appears at the foot of the home screen and at the foot of Settings.

Three ways to get to a game's folder:

  • On the home screen, the folder icon on its card.
  • With the project open in Full mode, File > Show the project in its folder.
  • After exporting, Show in folder.

If a game does not appear in the list but its folder exists, open it with Open folder…. If you sent it to the trash by mistake, move its folder from Green Games/papelera to Green Games/proyectos.

On Windows, uninstalling the editor keeps your projects.

Next#