Manual: The .godot Folder and the AGMaker Folder
This manual explains the two folders that are generated when using ACTION GAME MAKER: .godot and AGMaker.
.godot Folder
This folder stores data used by the Godot Engine.
It is essentially a cache folder, so it is regenerated as needed each time you use the project.
Because it can grow quite large, you may want to delete it when handing a project to someone else.
However, some files can cause issues if removed, so here is a breakdown.
cfg / bin files directly under .godot (Not recommended to delete)
These contain relatively important cached data such as UIDs and scene-related caches.
Deleting them may cause inconsistencies, so removal is not recommended.
.godot/editor (Safe to delete)
This saves your current work state, such as which scenes are open and which tabs you were viewing.
It does not contain data beyond your editor state, so deleting it usually causes no problems.
.godot/shader_cache (Safe to delete)
This stores shader data compiled for the GPU.
Deleting it is safe.
.godot/imported (Delete with caution)
This cache stores import/lookup data such as “this scene uses this image.”
Deleting it is generally safe, but on the next launch all images may appear blank/white until importing finishes.
AGMaker Folder
This folder contains data specific to ACTION GAME MAKER.
While it includes some cache-like data, deleting anything here is generally not recommended.
core.tscn (Do NOT delete)
This scene handles runtime processes such as scene transitions when running a game in ACTION GAME MAKER.
If you delete it, the project will no longer function correctly.
project_database.tres (Do NOT delete)
This is the database data file.
Deleting it will erase all database contents.
scene_transition.tres (Do NOT delete)
This contains scene transition data.
Deleting it will remove all scene transitions.
templates (Not recommended to delete)
This folder stores data used by the GameObject Template feature.
Due to how Godot works, template data located in the ACTION GAME MAKER application is first copied into this folder, and then instantiated as new scenes from here.
While the newly created scene itself can be saved anywhere under a new name,
referenced resources such as images and scripts continue to point to files inside the templates folder.
Therefore, deleting this folder may cause scenes to stop working properly.