Skip to content

Publishing tools

Sell your project

Sell a Godot project on itch.io or Gumroad, or share it free on GitHub. Flockbay takes no cut and hosts nothing: you pack the project, put it up where you sell it, and check the licence of each asset in it.

Pack the project

  1. Make a copy of the project folder and work on the copy, so your own project keeps everything.
  2. Take out what is not the project: builds you exported into the folder, .env and any other file that holds an API key or a password, and .git/ unless you mean to share the history.
  3. Take out Flockbay’s own files. On Home, choose Open project…, pick the copy and choose Open without Flockbay. Close its editor, then choose Uninstall Flockbay from project… in the copy’s project menu. Its card lists what goes: addons/flockbay_editor/, .flockbay/, stage_generated/ and Flockbay’s lines in project.godot. Your scenes and scripts stay, and a buyer who opens the project in Flockbay is asked before anything is added back.
  4. Open the copy again with Open without Flockbay and choose Project › Pack Project as ZIP… in Godot’s menu. The .zip holds the whole folder except .godot/, Godot’s import cache, which is rebuilt the first time the project opens.
  5. Extract the .zip into an empty folder, open it, and run it once (Play in Flockbay, F5 in Godot) before you put it up.

If you have a creator code from Flockbay, a flockbay-credit.json came with it. Keep it at the project’s root, beside project.godot: it tells Flockbay the project is yours. Godot ignores it, and Flockbay never changes it.

Sell it on itch.io

  1. Create a project on itch.io with Kind of project set to Downloadable and Classification set to Game assets, give it a price, and upload the .zip under Uploads.
  2. Fill in AI generation disclosure on the project’s edit page. itch.io requires it on every asset page and may delist one without it. Publishing tools › itch.io lists what Flockbay’s records show was generated with AI in the game.
  3. itch.io takes 10% of each sale unless you change it. Set its share with the slider in your account’s seller settings, down to 0% if you like; payment processing fees still come out of each sale.

To let buyers try the game first, Upload to itch.io in Publishing tools › itch.io pushes playable Windows, Linux or Web builds of it to the same page. On a paid page, mark each of them as a demo under Uploads on itch.io, or they sit behind the price with the .zip.

Sources: itch.io quality guidelines, itch.io payments.

Sell it on Gumroad

Create a digital product on Gumroad, upload the .zip and set its price. Gumroad takes a fee on each sale, plus payment processing, listed on its fees page.

Gumroad doesn’t allow reselling products you didn’t create, and names templates among them. Sell the game you built, not a template as it came from New from template….

Sources: Gumroad’s fees, What you can’t sell on Gumroad.

Share it free on GitHub

Publish the copy you packed, not your working project: a repository carries every file and its whole history, generated audio and old secrets included. Put it in a public repository with Publish to GitHub… in the Version control panel, or with Git itself: Version control with Git and GitHub. Anyone can then open it with Open from GitHub… on Home.

If you are a Flockbay creator, each project listed on your creator account opens from an Open in Flockbay link: the repository’s address after src= and your creator handle after c=. The link opens a page that names the project and you; Open in Flockbay asks the app to clone the repository where new projects go and open it once the developer presses Open, and someone without Flockbay downloads it first. A repository or .zip that isn’t listed on a creator’s account doesn’t open from a link; one of Flockbay’s templates (src=template: and its id) always does.

Text
https://flockbay.com/open?src=https://github.com/your-name/your-project&c=your-handle

Check the licence of every asset

Whoever buys or downloads your project gets every file in it, so each one has to be yours to pass on. Flockbay doesn’t clear the rights to what a project holds; that is yours to check (Flockbay’s Terms, sections 4 and 6). The sections below say what each source’s terms say.

Templates and Godot

A project made with New from template… keeps its template’s LICENSE file. A template’s code is under the MIT licence, which asks one thing of anyone who sells or shares it: keep its copyright and permission notice with every copy. Some templates’ art, fonts and sounds have licences of their own, listed in the template’s credits file. Keep LICENSE and the credits word for word.

Godot is under the MIT licence too, and what you make with it is yours.

Sources: The MIT licence, Godot’s licence.

Pictures generated through Flockbay

Flockbay makes them with OpenAI’s image models. OpenAI’s Services Agreement gives its customer, Flockbay, the rights in what the models make, and names no limit on selling them; it also says an output may not be unique, so someone else may get a similar picture (sections 4.1 and 4.4). Flockbay’s Terms leave you the content you create, subject to anyone else’s rights (section 5).

Pictures made on your own OpenRouter key come under your own agreement with OpenRouter and the model’s provider instead.

Sources: OpenAI Services Agreement.

Sound and music generated through Flockbay

Flockbay makes them with ElevenLabs. Its sound effects terms allow generated sound only combined with other material: not sold or licensed on its own, and not made available as isolated audio files or samples, or in a sound library. Its music terms rule out collections of generated music made available for others to use in their own work.

A project zip or a public repository hands people the audio files themselves, which both sets of terms rule out, whether you charge or not. Leave generated sound and music out of what you sell or share, or replace them with sound you hold the rights to. Sound made on your own ElevenLabs key comes under the same terms, on your own plan.

Sources: ElevenLabs sound effects terms, ElevenLabs music terms.

3D models from your own Tripo key

They come from your Tripo account, under Tripo’s terms. On a paid plan you hold the rights in what you generate, including to distribute and license it (section 5.2.2); on the free plan Tripo keeps them (section 5.2.1), and Tripo’s pricing page lists free models as non-commercial.

The terms don’t say whether buying API credits makes you a paid user, so ask Tripo before you sell models made that way.

Sources: Tripo’s terms, Tripo’s pricing.

Add-ons

An add-on keeps its own licence: in its folder under addons/, and on its page in Godot’s Asset Library. Some allow resale, some ask for credit, and some rule out commercial use. Read each one before you sell a project that includes it.

Sources: Godot Asset Library.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux