$ ls ./scripts/

PYTHON
SCRIPTS_

— SCRIPTS · AUTODESK FLAME

Browse, Download, and Submit Flame Python Scripts

python scripts tools pixel expressions matchboxes batch setups inference nodes

SELECT A SCRIPT

// SUBMIT A SCRIPT

Share a Python script with the community. You can submit a single python script (.py) file or a folder containing your script and any supporting files. Read the submission guidelines before you submit.

// TYPE

Single File (.py)

Folder

Drag .py file here

BROWSE

—

SCRIPT

—

VIDEO

Optional. A video demoing your script. YouTube links only — youtube.com or youtu.be. Anything else is rejected. The link is checked to confirm the video exists.

NAME

Website (leave blank)

// script submitted successfully.

// SUBMIT A GITHUB REPO

Share a Python script that lives in its own public GitHub repository. Provide a link to the top level of the repo — e.g. https://github.com/owner/repo — not a link to a specific file, branch, or subfolder. The script must follow the submission guidelines.

// BEFORE YOU SUBMIT

> Your repo must be public and have at least one GitHub Release. Logik Portal publishes your latest release, not your main branch — plain tags, commits, drafts and pre-releases are not picked up.
> The release must contain a Python file named after the repository, e.g. test_script.py for a repo named test_script, with the standard Logik Portal docstring (see submission guidelines).
> The repository name becomes the script name, so it must use only lowercase letters, numbers and underscores (e.g. test_script).
> The release’s version tag (e.g. v1.2.0) must match the Script Version: in your docstring (1.2.0).

// UPDATING YOUR SCRIPT LATER

> Update your script and its docstring — Script Version:, Update Date: and a new Updates: entry — and commit it.
> Create a new GitHub Release with the higher version number (e.g. v1.3.0).
> That’s it. Logik Portal checks for new releases every hour and updates your script automatically.
> If the release version doesn’t match the docstring’s Script Version, the update is held until it’s fixed.

// FIXING A RELEASE

> A GitHub release is a snapshot of the commit its tag points to. Editing or re-publishing the release does not change its files.
> Made a mistake (a missing file, the wrong docstring)? Publish a new release with a higher version — or, to keep the same version, delete the release and its tag (Releases → delete the release, then Tags → delete the tag, or git push --delete origin v1.0.0) and create the release again with the same tag on your latest commit.
> Once your script is approved, only a release with a higher version than the one on Logik Portal is picked up.

REPO

NAME

Website (leave blank)

VALIDATION_ERRORS

// SUBMISSION GUIDELINES

Scripts submitted to Logik Portal must follow these guidelines to be accepted.

Do not upload scripts as a zip file.

// FILE & FOLDER NAMING

> All lowercase letters, numbers, and underscores only
> No spaces in the file or folder name
> No version numbers in the name (e.g. my_script_v1.py will fail)
> Single file submissions must end in .py
> Scripts requiring multiple files must be submitted as a folder

// FOLDER STRUCTURE

If submitting a folder, the main script inside must share the same name as the folder:

my_script/
  my_script.py        # ← main script, must match folder name
  helper.py           # ← additional files are fine
  lib/
    some_lib.py

Files automatically ignored: .DS_Store __pycache__ .pyc files

// REQUIRED DOCSTRING

The main script file must contain a docstring with the following fields and sections. Fields are case-sensitive.

"""
 
Script Name:    My Script           # must match filename (case-insensitive)

Script Version: 1.0.0               # X.Y or X.Y.Z — no "v" prefix

Flame Version:  2025.1              # YYYY or YYYY.X — numbers only, no third segment

Written by:     Your Name

Creation Date:  01.15.25            # MM.DD.YY

Update Date:    03.26.26            # MM.DD.YY — required if updating existing script

Description:

    What the script does.

Menus:

    Right-click in batch -> My Script

Updates:                                # required if Update Date is present

    v1.0.0 03.26.26

        - Initial release.

"""

// FIELD RULES

Script Name:	Must match the filename (without .py), case-insensitive
Script Version:	1.0 or 1.0.0 — no v prefix
Flame Version:	2025 or 2025.1 or 2025.1.1 — numbers only, no letters or symbols
Creation Date:	MM.DD.YY format — e.g. 01.15.25
Update Date:	Same format as Creation Date. Required when updating an existing script. If present, an Updates: section is also required.
Description: / Menus:	Both sections are required.

// UPDATING AN EXISTING SCRIPT

> If a script of the same name already exists, you must include an Update Date: field and an Updates: section explaining whats new in this version.
> Submitting a script with the same version number will show a warning — but you can still continue submitting your script. Versioning up is preferred.

// GITHUB REPO SUBMISSIONS

> The repo must be public and have at least one GitHub Release. Logik Portal publishes your latest release, not your main branch — plain tags, commits, drafts and pre-releases are not picked up.
> The release must contain a Python file named after the repository, e.g. test_script.py for a repo named test_script, with the docstring above.
> The repository name becomes the script name, so it must use only lowercase letters, numbers and underscores (e.g. test_script).
> The release’s version tag (e.g. v1.2.0) must match the docstring’s Script Version: (1.2.0).
> To update: change the script and its docstring (Script Version:, Update Date:, a new Updates: entry), commit, then create a new release with the higher version (e.g. v1.3.0). Logik Portal checks hourly and updates your script automatically.
> If the release version doesn’t match the docstring’s Script Version, the update is held until it’s fixed.

// FIXING A GITHUB RELEASE

> A GitHub release is a snapshot of the commit its tag points to. Editing or re-publishing the release does not change its files.
> Made a mistake (a missing file, the wrong docstring)? Publish a new release with a higher version — or, to keep the same version, delete the release and its tag (Releases → delete the release, then Tags → delete the tag, or git push --delete origin v1.0.0) and create the release again with the same tag on your latest commit.
> Once your script is approved, only a release with a higher version than the one on Logik Portal is picked up.

// THANK YOU

Thank you for your submission. Your script is being processed and will appear on the Logik Portal soon.

// SUBMITTED

PYTHONSCRIPTS_

PYTHON
SCRIPTS_