Skip to content

Conversation

Arecher
Copy link

@Arecher Arecher commented Aug 19, 2025

Added a paragraph to explain that you need to create custom commands to be able to hook up custom key shortcuts to extension functionality.

Added link to API documentation for :NewCommand(). Since it links from the Docs repository to the API repository, I had to use a hardcoded website link. If there is a better way to do that, let me know

Added a paragraph to explain that you need to create custom commands to be able to hook up custom key shortcuts to extension functionality.

Added link to API documentation for :NewCommand()
@Arecher
Copy link
Author

Arecher commented Aug 19, 2025

I added this explanation because when I first encountered .aseprite-keys I couldn't for the longest time figure out how to set them up. Even though it clearly states 'Command', I didn't realise it wanted a 'NewCommand()' name.

I tried function names, plugin names, command ids etc. Took me a bit, so I thought I would help out anyone else that might have read the page a little too quickly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant