Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Since you're on a self-compiled build, could you try two quick things?

  1. Launch Aseprite from a terminal (./aseprite or whatever binary you use), open the extension, click the buttons that do nothing, and paste here any output you get. Lua errors get printed there.
  2. If nothing shows up in the terminal, try enabling the console inside Aseprite: press F1 Developer Console, or check "Show console messages" under Preferences -> Experimental. Errors should pop up there too

I haven't that option in preferences -> Experimental. Maybe because I selected user and not developer in the dialog that apeared when I started compiling aseprite?