ValueMarks 1.0.0 Documentation

Save frequently used numbers in supported Blender fields, then recall them with the right-click menu, the Preset Slider, or hover shortcuts.

1. Requirements and included files

Minimum Blender version: 4.2.0. Tested on Windows with Blender 4.2.23, 4.3.2, 4.4.3, 4.5.11, 5.0.1, 5.1.2, and 5.2.1. macOS testing is not complete; Linux and versions outside this range have not been tested. In Blender 4.3.x, use the right-click menu because hover shortcuts do not work.

The download includes valuemarks-1.0.0.zip, Quick_Start.pdf, and User_Manual.pdf. If supplied as ValueMarks-1.0.0.zip, extract that outer package first. Keep the two PDFs in the same folder so their links work. The Extension ZIP includes the README, release notes, Python source, and GPL-3.0-or-later license.

2. Install

1. Open Edit > Preferences > Get Extensions.
2. Open the upper-right menu and choose Install from Disk.
3. Select the inner valuemarks-1.0.0.zip and install it without extracting it.
4. In Preferences > Add-ons, find ValueMarks and enable it if needed.

Do not install the outer ValueMarks-1.0.0.zip package directly in Blender. ValueMarks needs permission to write its saved data in Blender's Extension user folder.

3. Save your first presets

1. Select a mesh, such as the default Cube, and add a Bevel modifier in Modifier Properties.
2. Set Segments to 2. Right-click the number itself and choose Save Current Value under Value Presets.
3. Repeat with 4 and 8.
4. Right-click Segments and choose Preset Slider... to try the saved values.

Save a different number to add another preset. Duplicate saved numbers are refused.

4. Use the Preset Slider

Click a preset mark, or press and drag along the slider. The field changes as you drag and snaps to nearby saved values. Release the left mouse button to confirm. Hold Ctrl to adjust freely without snapping. Press Esc, right-click, or click outside the slider to cancel and restore the original value.

The right-click menu can open the slider even before you save presets. Hover shortcuts require at least one preset for the field.

5. Use hover shortcuts

Before starting either shortcut, place the pointer over the number itself, rather than its label.

• Hold Shift+Alt+S: move the mouse to adjust the value. Release S or left-click to confirm. Esc or right-click cancels. Ctrl disables snapping.
• Shift+Alt+Wheel Up / Down: apply the next higher or lower saved value in numeric order. The wheel stops at the ends of the list.

Both shortcuts require a saved preset for that field and are unavailable in Blender 4.3.x. In that version, use the right-click menu. Avoid Ctrl combinations for the wheel shortcut: Blender handles them first, so they do not reach ValueMarks.

6. Manage presets and customize controls

Right-click a supported number field and choose Manage Presets....

• Value field: edit a saved number without applying it to the original field. Duplicate and out-of-range values are refused.
• Pencil: add or change the preset name.
• Up / down arrows: rearrange the list. Wheel navigation still follows numeric order.
• X, then Delete: remove a preset.
• +: add the current field value. If it is already saved, ValueMarks generates an unused value within the allowed range when possible; edit the result if needed.

Each list holds up to 100 presets; names can contain up to 64 characters. Management changes save immediately. Saving, renaming, editing, deleting, and rearranging presets cannot be undone with Ctrl+Z.

In Edit > Preferences > Add-ons > ValueMarks, choose Compact for the three main menu actions or With Preset List to add clickable saved values. The menu choice saves automatically. Shortcuts can also be changed here; save Blender Preferences if automatic preference saving is off.

7. Supported fields, animation, and Undo

ValueMarks supports editable integer and decimal fields, including lengths, angles, percentages, Bevel Amount/Width and Segments, material Roughness, numeric node and Geometry Nodes inputs, custom number fields, and individual Location, Rotation, or Scale components.

It saves one number at a time. Colors, Quaternion and Axis Angle rotation fields, direction and matrix values, checkboxes, text, and drop-down choices are unsupported. Read-only and driven fields, fields on linked or overridden library data, and number fields in Blender Preferences (including add-on settings) are unavailable.

Applying a preset to a keyframed field does not insert a keyframe. Insert or update the keyframe yourself to include the change in your animation.

Applied values normally support Ctrl+Z and Ctrl+Shift+Z. One confirmed slider change or one wheel step is one undo action. View settings such as the 3D View's Focal Length are outside Blender's undo system.

8. Saved data and backups

Presets are shared across .blend files for the same kind of field within the same ValueMarks saved-data folder, rather than stored in each file. Different Blender versions, profiles, or computers may use different folders; presets are not automatically synchronized between them. Bevel Width and Roughness have separate lists, as do X, Y, and Z components. Node inputs share by node type and input; Geometry Nodes inputs share by node group and input. Custom fields share by property name and the kind of item they belong to.

Saved values are stored in presets.json in ValueMarks' Blender Extension user folder. The menu choice is in settings.json; Blender stores the shortcuts. Presets remain after restarting Blender or disabling and re-enabling ValueMarks.

For a standard Windows installation, open %APPDATA%\Blender Foundation\Blender, then your Blender version's folder, extensions, .user, the repository folder (usually user_default), and valuemarks. Portable and custom installations may use another location. The preset file appears after the first saved preset; the settings file appears after changing the menu choice.

1. Close all Blender windows using the same saved-data folder.
2. Copy presets.json to a safe folder outside Blender's settings. Copy settings.json too to preserve the menu choice.
3. To restore, keep a copy of the current files, replace them with the backup in the same ValueMarks folder, then restart Blender.

There are no Import or Export buttons in version 1.0.0. Do not edit the JSON contents by hand. Values display using Blender's current units; changing unit settings does not convert or rescale saved values. Check the result when reusing presets in files with different units.

9. Update, disable, and uninstall

Back up saved data before updating or changing Blender versions. Update through Blender's Extension controls or use Install from Disk with the newer Extension ZIP. A normal update keeps saved data; another Blender version may use another folder. Use the same current ValueMarks version in all Blender windows sharing the files.

Disable ValueMarks in Preferences > Add-ons to stop using it temporarily. Uninstall deletes its saved presets and menu setting. Back up before using Uninstall in the Extension controls.

10. Troubleshooting and support

• No Value Presets menu: enable ValueMarks and right-click the number itself. Try Bevel Segments or Location X to check a supported field.
• Shortcut does nothing: check pointer position, save a preset for the field, and check key conflicts in Preferences. In Blender 4.3.x, use the menu.
• Out-of-range value: use a value accepted by the field. The slider also refuses to open if the current value is outside its allowed range.
• Target changed: close the menu or management panel and right-click the field again.
• Saved presets have a different value type: manage them from a field with the original integer or decimal type.
• Presets changed in another Blender window: check the reloaded list and repeat your intended action. If a save is in progress, wait and try again.
• Cannot save: check disk space and folder permissions.
• Cannot read the preset file: keep a copy first and restore a working backup. Alternatively, choose Reset Presets File and confirm. Reset starts an empty list and keeps the unreadable file as presets.corrupt-.json. It does not repair that file; a new presets.json is written on the next preset save.

Names and unit symbols may appear garbled in the Windows System Console; this alone does not mean presets are damaged. The interface and documentation are English only.

For help, contact Virtual Rain through the Superhive product page or email [email protected]. Include your Blender and ValueMarks versions, operating system, target field, reproduction steps, and the exact message or a screenshot. Remove personal information before sharing logs or images.

The included Quick_Start.pdf provides an illustrated first-use guide. User_Manual.pdf covers controls, supported fields, storage, and troubleshooting in more detail. Support is available while the product is published. Updates are made when bugs or feature requests arise.