Create a directory with your add-on’s name prefixed by an_, that is, an_<your_extension_name>. The directory should follow the following base structure:

├── ui/
│   ├──
│   ├──
├── sockets/
│   ├──
│   ├── ...
├── nodes/
│   ├──
│   ├── ...

Do not use animation_nodes in your extension name.

We will explain what needs to be added in those files in a moment. The file can be copied from the Animation Nodes source without any changes, the file is inside the animation_nodes directory. This file will help us automatically register and load classes, so it is not mandatory, but it is recommended. For auto loading to work, each of the directories that have files that define a Blender class needs to have an empty file, which are the files you see in the sub-directories above.

This structure works for simple extensions. More complex extensions that utilize Cython should follow a more complex structure. This structure is described later in the Cython section.


In the top-level file, we need to do three things:

  • Make sure Animation Nodes is loaded and available.
  • Initialize the automatic loader and register/unregister the classes.
  • Update socket information. This is only needed if you define new sockets.
Copyright (C) 2020 <YOUR NAME>

Created by <YOUR NAME>

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <>.

bl_info = {
    "name": "Animation Nodes Test Extension",
    "author": "<YOUR NAME>",
    "version": (1, 0, 0),
    "blender": (2, 90, 0),
    "location": "Animation Nodes",
    "description": "A Test Extension For Animation Nodes.",
    "warning": "",
    "doc_url": "",
    "tracker_url": "",
    "category": "Nodes",

import bpy
import addon_utils
from . import auto_load

try: import animation_nodes
    animation_nodes = addon_utils.enable("animation_nodes", default_set = False, persistent = True)
    if not animation_nodes:
        raise Exception("Could not load Animation Nodes.")


def register():
def unregister():


Add your nodes inside the nodes directory or any of its sub-directories. The directory and its sub-directories should each have an empty file as we mentioned before. Check the Node Development guide for information on how to create nodes or check the Animation Nodes source for examples on how to write nodes.


Absolute Imports

In the Animation Nodes source, Animation Nodes objects are imported relatively. This will not work for extensions. You have to import objects absolutely from the animation_nodes module. So if you see an import statement like this in the Animation Nodes source:

from .. perlin_noise cimport perlinNoise1D

It should be translated into:

from animation_nodes.algorithms.perlin_noise cimport perlinNoise1D

Extension Module In Execution Code

You can use the animation_nodes module—which is also aliased to AN—in the execution code of the node. That’s because it is imported by default. In order to use your extension module, you have to tell Animation Nodes to import it by overriding the getUsedModules method. So the code should be:

    def getUsedModules(self):
            return ["an_<your_extension_name>"]


Add your sockets inside the sockets directory or any of its sub-directories. The directory and its sub-directories should each have an empty file as we mentioned before.


In order to add your nodes to a menu. In a file in the ui directory, define a draw function that either draw other menus or draw node insert operators directly. Then, in the register function, append this draw function to any of the Animation Nodes menus or the Add menu directly. For instance, the following file defines a new menu and draws a node insert operator in it. Then, a draw function is defined that draws this menu, which is then appended to the NODE_MT_add menu, which is the node add menu. The menu will be positioned at the end of the menu you appended to.

import bpy
from animation_nodes.ui.node_menu import insertNode

class TestExtensionMenu(bpy.types.Menu):
    bl_idname = "AN_MT_test_extension_menu"
    bl_label = "Test Extension Menu"

    def draw(self, context):
        layout = self.layout
        insertNode(layout, "an_TestExtensionNode", "Test Extension Node")

def drawMenu(self, context):
    if context.space_data.tree_type != "an_AnimationNodeTree": return

    layout = self.layout
    layout.operator_context = "INVOKE_DEFAULT"

    layout.separator()"AN_MT_test_extension_menu", text = "Test Extension Menu", icon = "SCRIPTPLUGINS")

def register():

def unregister():

Had I wanted to add the menu to the vectors menu in Animation Nodes, I would have appended to the AN_MT_vector_menu menu instead. For a full list of menus and more examples on how to define more complex menus, check the file in the Animation Nodes source here.


If you would like to write your own Cython code and define your own Cython structures, you can use the setup script from Animation Nodes, in which case, your project should follow the following base structure:

├── conf.default.json
├── an_<your_extension_name>/
│   ├── ...
├── _setuputils/
│   ├── ...

The inner an_<your_extension_name> directory is the one illustrated above. The _setuputils directory,,, and conf.default.json should be copied from the Animation Nodes source. The only change you need to make is to change the addonName variable to an_<your_extension_name> in both the and the files. The last thing that need to be done is to setup the headers.

Header Files

In order to build your extension, Cython needs to look at the header files of Animation Nodes. So first download the latest archive from the release page, extract it, and configure the build system to find it by adding the path of the extracted directory to the array entry named Cython Include Paths in the conf.json file. Notice that this file is generated after the first time you build, but you can add it yourself to the root directory before that. An example conf.json is shown:

    "Copy Target" : "/path/to/your/blender/addon/directory",
    "Cython Include Paths" : ["/path/to/the/extracted/directory/animation_nodes_headers/"]