English

Русский

About MiBlend

Detailed information about MiBlend, its releases, versioning system, and compatibility.

šŸ“Œ Release Plan

The current plan for upcoming releases and the ongoing progress are available in GitHub Projects. If you are interested in changes planned for more distant versions, please refer to Milestones.

Major MiBlend updates are released every 2-4 months, while minor patches and improvements are released as needed.

šŸ”¬ Experimental Builds

All commits from the experimental branch of MiBlend are automatically published on GitHub as ready-to-use add-ons.

Important: These versions may contain critical bugs and potentially cause serious damage to your project. They are recommended for testing and research purposes only. You can learn how to install experimental builds in the guide.

The add-on information always includes a warning about its experimental status and the exact build date.

šŸš€ Milestones

When most tasks for a new major version are completed, a Milestone is released – a more stable version of the experimental build. It may still contain bugs and shortcomings, but there are significantly fewer of them than in experimental builds.

Single-digit milestones may be released multiple times with letters added to the end of the name, for example: Milestone 3A (M3A), Milestone 3B (M3B), etc. Such intermediate updates usually do not include anything substantial other than bug fixes and minor improvements.

šŸ”¢ Version Numbering and Naming

šŸ“› Version Name Formation

The name for major updates is chosen based on their main theme or key functionality. Minor updates inherit the name of the major one, and their own names are usually chosen in a more flexible manner.

šŸ“Œ Numbering System

MiBlend versions are numbered according to the standard scheme x.y.z, where:

  • x — Global update number (e.g., the first official add-on release).
  • y — Major update number with new features.
  • z — Minor update number, including bug fixes or small additions.

šŸ”  Version Indices

Additionally, letter indices may be present in the version name, indicating the type of changes made:

  • F (Fix) — Bug fixes, without adding new functionality.
  • Plus (+) — Small additions to existing functions.
  • S — Minor changes, bug fixes, and small improvements.

šŸ”„ Compatibility

šŸ›  Supported Blender Versions

MiBlend works with all Blender versions, starting from the oldest updatable LTS (currently Blender 3.6 LTS). However, some functions and assets may be missing in older versions due to the limitations of the Blender version itself.

Supported Versions:

  • 3.6 LTS
  • 4.0
  • 4.1
  • 4.2 LTS
  • 4.3
  • 4.4
  • 4.5

ā„¹ļø Legend: — Full support, — Supported, but with limitations.

šŸŒ World Exporter Support

I strive to support all Minecraft world exporters. jmc2obj demonstrates the best compatibility, as it minimally alters textures and their names, and also provides more information, which contributes to more correct operation.

List of Supported Exporters:

  • Mineways
  • jmc2obj
  • MiEx šŸ”“

ā„¹ļø Legend: — Full support, — Partial support, šŸ”“ — Not supported.

šŸ–„ Supported Operating Systems

Currently, development is carried out on Windows 11. Previously, I actively used Linux, so MiBlend retains compatibility laid down at that time whenever possible. The situation on macOS remains uncertain: since it is a Unix-like system, theoretically everything should work, but full testing on this platform has not been conducted.

List of OS:

  • Windows
  • Linux
  • macOS ā“

ā„¹ļø Legend: — Full support, — Possible issues, ā“ — Compatibility unknown (operability depends on the specific case).