Questions, answered directly.

No. BSM Tools doesn't design a level or a biome for you - it gives you the hands-on placement, painting and animation controls a DCC artist already knows (Houdini scattering, Blender vertex painting, Substance-style layered texturing), applied directly inside Unity's own Editor. You still make every creative decision.

28 editor tools across nine categories (Scene, Scattering, Painting, Terrain, Camera, Animation, Rendering, Procedural GameObjects, Utilities) plus 6 runtime components you can drop into a playing scene. Full breakdown on the Documentation page.

No. Every tool is a standard Unity Editor window driven by the mouse and inspector fields, the way you'd expect from any DCC application panel. The full C# source is included if you ever want to extend or reference it, but nothing requires opening a script to use the suite.

Unity 6.0 or later. The suite is validated on Unity 6.5 (6000.5), including its updated C# compiler and scripting runtime, and also compiles and runs on 6000.3.

No. Since Unity 6000.3, most tools are render-pipeline independent. Only Decal Painter, Light FX, Renderer, Framebuffer and Ray Tracing Setup require HDRP - every other tool works the same under URP, and the HDRP-only tools simply stay unavailable rather than breaking anything else.

com.unity.splines for Shot Designer and two runtime components, com.unity.cinemachine for the Camera System, and HDRP for the five tools listed above. All three are feature-gated: install only what you need, and BSM Tools includes a one-click installer that shows Installed/Missing status for each (BSM Tools > Utilities > Install Optional Packages).

Yes. Each tool was built to work on its own; nothing in the suite depends on another tool being present. Copy the whole package or trim it down to the categories you need.

Yes, the full C# source for every editor tool and runtime component ships with the package - nothing is compiled into a DLL.

Yes, you can modify the source files for your own internal use. You may not publish, resell or share the modified (or original) source outside your own projects - see the licensing section below.

Poly Haven and ambientCG, both CC0 (public domain) texture libraries. The Material Browser's External tab downloads the maps you choose, at your pick of resolution, directly into your project through their public APIs - no account or subscription required, and no extra licensing to track.

Yes. The license covers personal and commercial Unity projects, and built games or applications produced with the Software can be distributed without any additional royalty.

A single license covers one individual developer. Studio or team licenses covering multiple seats are available separately - contact Contact for multi-seat pricing.

No subscription - the license is perpetual, purchased once. Bug-fix updates pushed to the Asset Store listing are free for every existing owner, for as long as the asset is maintained; that's how Asset Store purchases work, not a separate promise on top. As noted above, support is best-effort from a single developer, so there's no guaranteed release schedule for fixes - but when a fix does ship, it never costs anything extra.

No. The license does not allow redistributing, reselling, or sharing the Software or its source (in whole or in part) on any public repository, forum or file-sharing service, or bundling it into another asset intended for distribution or sale.

Support is provided on a best-effort basis by the author - an independent, single-developer project, not a company with a support desk. Bug reports and questions go through Contact or the Unity Asset Store support page; response times aren't guaranteed. Studios needing SLA-backed support can contact the same address to discuss it.

Yes, a small anonymous ping at most once per day per install: a random install ID, the BSM Tools version, your Unity version and license tier, and your active render pipeline. No username, machine name, project content, or path is ever sent. It's on by default and can be switched off anytime from BSM Tools > Support > Privacy - see README.txt for the exact field list.

As a solo developer, this is the only way to know which Unity versions and pipelines are actually in use, which shapes what gets maintained and improved first.