Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “The fcurve.modifiers.new(type) method creates a new modifier according to the type provided in the argument. It returns the new modifier.”

A block of code is set as follows:

bl_info = {
    "name": "Object Shaker",    "author": "Packt Man",    "version": (1, 0),    "blender": (3, 00, 0),    "description": "Add Shaky motion to active object",    "location": "Object Right Click -> Add Object Shake",    "category": "Learning",
}

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

sin((frame / fps) * 2 * pi / (2 * pi * sqrt(length/9.8)))

Any command-line input or output is written as follows:

['ASSETBROWSER_MT_context_menu',...['VIEW3D_MT_edit_metaball_context_menu', 'VIEW3D_MT_gpencil_edit_context_menu', 'VIEW3D_MT_object_context_menu', 'VIEW3D_MT_particle_context_menu',...

Some of the code is meant to be used as input for the interactive Python Console. In that case, the user input is preceded by the >>> prompt, unlike the console output:

>>> print("Hello")
Hello

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “Before we delve into how f-modifiers are scripted, we will have a look at how to create them in Graph Editor.”

Tips or important notes

Appear like this.