Addons Manager Documentation
Installation
Installation
Installing the Addon
The installation process is straightforward and identical across all operating systems:
- Download the addon ZIP file from your order page.
- Open Blender and navigate to Edit › Preferences › Add-ons.
- Click the Install button in the top-right corner.
- Select the downloaded ZIP file and click Install Add-on.
- Enable the addon by checking the box next to "Addons Manager".
- The addon panel will appear in the 3D Viewport sidebar (press N) under the "Addons Manager" tab.
Configuring Preferences
After installation, you may want to configure the addon's preferences:
- Open Edit › Preferences › Add-ons.
- Find Addons Manager in the list and expand its preferences panel.
- You'll see the Show Reload Button option.
Show Reload Button
This checkbox controls whether the hot reload button appears next to each enabled addon. The reload functionality is primarily designed for addon developers who need to test code changes without restarting Blender.
Why it's disabled by default: For most users, the reload button adds unnecessary UI clutter. End users typically don't need to reload addons during normal Blender usage. Keeping this feature hidden by default provides a cleaner, more focused interface.
When to enable it: If you're developing Blender addons or frequently testing addon modifications, enable this option. The reload button will appear to the left of the addon name in the enabled addons list, allowing you to refresh addon code instantly without restarting Blender.
Interface Reference
The Addons Manager panel is located in the 3D Viewport sidebar (press N) under the "Addons Manager" tab. This section explains each control and feature in detail.
Search & Display Mode
Search
The search box allows you to quickly filter addons by name. Type any part of an addon's name and the list will update to show only matching results.
Display Mode
Controls which addons appear in the lists. Two modes are available:
| Mode | Description |
|---|---|
| Filtered | Shows only addons marked as visible. Provides a clean view of your frequently-used addons. |
| All | Shows every installed |
Refresh Addons
The Refresh Addons button forces Blender to rescan the addons directories and update the internal addon list.
When to use it: Addons manager usually refresh itself when you install or uninstall an addon but if you manually install it by extracting its files directly into the scripts folder (rather than using Blender's Install button), the addon won't appear in the list until you click Refresh.
Preset Management
Presets allow you to save and restore complete addon configurations.configurations: which addons are enabled, which are disabled, and all their individual preferences. This is one of the most powerful features of Addons Manager.
Preset Dropdown
What happens when you load a preset:
Save Current as Preset
What gets saved:
Tip: Name your presets descriptively based on your workflow. Examples: "Modeling", "Rendering", "Animation", "UV Unwrapping", "Development".
Saved Presets Panel
This collapsible panel lists all saved presets with management options for each:
Addon Lists
Addons are organized into two collapsible sections: Enabled Addons and Disabled Addons. Each section can be expanded or collapsed independently.
Enabled Addons
Shows all currently active addons. Each addon entry displays:
Disabled Addons
Shows all currently inactive addons. Each addon entry displays:
Visibility System
The visibility system allows you to declutter your addon lists without actually disabling addons. This is separate from the enabled/disabled state.
How Visibility Works
Each addon has a visibility toggle button (eye icon) on the left side of its entry:
Use case: You have 50 installed addons but only use 10 regularly. Mark those 10 as visible, hide the rest, and switch to Filtered mode. Your list now shows only the addons you actually need, making it much faster to find and toggle them.
Important: Visibility is purely organizational. It doesn't affect whether an addon is enabled or disabled. It only controls whether the addon appears in your filtered view.
Hot Reload (Nerd Developer Feature)
Hot reload allows addon developers to test code changes without restarting Blender. This feature must be enabled in addon preferences (see Installation section above).
How Hot Reload Works
When you click the reload button next to an enabled addon:
Requirements
For hot reload to work properly, your addon must:
register() and unregister() functions.
Be properly structured as a Python package or module.
Limitations
Hot reload works well for most addons but has some limitations:
Troubleshooting: If reload fails, check Blender's System Console (Window › Toggle System Console on Windows, or launch from terminal on Linux/macOS). Detailed error messages and stack traces will appear there.
Best Practices
Organizing Your Workflow with Presets
Task-Based Presets
Create presets organized around specific tasks rather than arbitrary groupings:
Performance Optimization
More enabled addons = longer Blender startup time and higher memory usage. Use presets strategically:
Visibility vs. Presets: When to Use Each
Use Visibility When:
Use Presets When:
Combining Both:
The most efficient workflow uses visibility and presets together:
Advanced Usage
Understanding the File Structure
Addons Manager stores all its data in:in the Blender scripts directory under addon_manager_prefs:
~/.config/blender/[version]/scripts/addon_manager_prefs/
On Windows, this is typically:
%APPDATA%\Blender Foundation\Blender\[version]\scripts\addon_manager_prefs\
Directory Contents
prefs/
Directory containing individual preference files for each addon (one JSON file per addon).
addon_visibility.json
Stores visibility state for each addon (visible/hidden in filtered mode).
presets.json
Contains all saved presets with addon states and preferences.
Manual Backup and Restoration
Backing Up Your Configuration
To manually backup your entire Addons Manager configuration:
What gets backed up:
Restoring from Backup
Transferring Configuration Between Blender Versions
When upgrading to a new Blender version, you can transfer your Addons Manager configuration:
addon_manager_prefs folder in your old Blender version's scripts directory.
Copy the entire folder.
Paste it into the new Blender version's scripts directory at the same relative path.
Open the new Blender version and verify everything loaded correctly.
Note: This transfers your presets and preferences, but it doesn't transfer the addons themselves. You'll still need to install your addons in the new Blender version.
Editing Presets Manually
Advanced users can edit presets.json directly in a text editor. The file structure is straightforward JSON.
Use cases for manual editing:
Warning: Always backup presets.json before manually editing. Invalid JSON will cause presets to fail loading.
Understanding Preference Files
Each addon's preferences are stored as individual JSON files in the prefs/ subdirectory. File names are sanitized versions of addon module names.
Example: An addon with module name my_addon would have its preferences stored at:
addon_manager_prefs/prefs/my_addon.json
This architecture provides several benefits:
Troubleshooting
Preset Issues
Preset Won't Load
Symptom: Clicking "Load" on a preset does nothing or shows an error.
Causes and solutions:
presets.json in a text editor and verify it's valid JSON. Look for missing brackets, quotes, or commas.
Missing addons: The preset may reference addons that are no longer installed. Check the System Console for messages about addons that couldn't be enabled.
Dependency conflicts: Some addons in the preset may have unmet dependencies. Enable them manually to see specific error messages.
Preset Partially Loads
Symptom: Some addons from the preset enable correctly, but others don't.
Solution: Check the System Console (Window › Toggle System Console) for detailed error messages. Addons Manager logs which addons failed to enable and why. Common reasons include missing dependencies or conflicts with other addons.
Hot Reload Issues
Reload Fails with Error
Symptom: Clicking reload shows an error message and the addon stops working.
Common causes:
Recovery: If reload breaks your addon, disable it, fix the code issue, then re-enable it normally.
Reload Succeeds but Changes Don't Appear
Symptom: Reload reports success, but your code changes aren't reflected.
Possible causes:
__pycache__ directories in your addon folder and try again.
UI not updating: Force Blender to redraw by hovering over panels or switching areas.
Changes in wrong file: Verify you saved changes to the correct file and that Blender is loading from the right addon directory.
Preference Issues
Preferences Not Saving
Symptom: Changes to addon preferences disappear after disabling and re-enabling.
Causes and solutions:
addon_manager_prefs directory.
Disk space: Ensure you have available disk space.
File corruption: Check if the addon's preference file in prefs/ exists and contains valid JSON.
Preferences Reset to Defaults
Symptom: Addon preferences spontaneously reset.
Solution: This usually happens if the addon's preference structure changed (e.g., after an addon update). The old saved preferences may no longer match the new preference schema. Configure the addon with your desired settings again and they'll be saved with the new structure.
General Issues
Addons Manager Panel Doesn't Appear
Symptom: After enabling the addon, the panel doesn't show in the sidebar.
Solutions:
Viewing Console Messages
Many issues can be diagnosed by checking console output:
Addons Manager prefixes its messages with [Addons Manager] for easy identification.
Changelog
Version 1.9.9 (Current Release)
Version 1.9.7
Version 1.9.6
Version 1.9.5
Version 1.9.4
Version 1.9.3
Version 1.9.0
Version 1.8.5
Version 1.8.0
Version 1.7.0
Version 1.6.0
Version 1.5.0
Version 1.4.0
Version 1.0.0
Contact and Support
If you encounter issues, have questions, or want to suggest features, there are two ways to reach support:
SuperHive Market
Send a private message through the SuperHive Market platform. This is the preferred method for purchase-related questions, license inquiries, or general support.
For technical support, bug reports, or feature requests:
support@yatima.xyz
When Reporting Bugs
Please include the following information to help diagnose issues quickly:
💡 Tip: Detailed information helps provide effective solutions faster. The more context you provide, the better we can assist you!