Generate LODs and Batch Generate on an object that already has a chain now rebuild that chain instead of adding a second one (Rock_LOD1.001 and a second group empty). With any level of the chain active, the chain is rebuilt from LOD0. Only objects LOD Forge built are replaced: they are now marked, so LOD objects that came with a model, or a chain made by 1.0.1, are left alone and named in the message; remove those with Remove LODs to rebuild.

Batch Generate now fills the LOD Metrics panel with the active object's chain. Before, the panel kept the numbers of whatever was generated earlier.

Remove LODs removes only this object's group. Before, the group was found by a partial name: Remove LODs on Rock could delete BigRock_LODGroup and leave Rock_LODGroup in place.

If objects with the LOD names already exist and LOD Forge did not build them for this object (a plain Rock next to someone's Rock_LOD1), Generate stops and names them instead of creating .001 copies.

Generate LODs and Batch Generate no longer stop with a Python error on a mesh with shape keys (Blender cannot apply the decimation to it), which also left a half-built LOD1 in the scene. LOD1 and below are now built from the mesh's basis shape without shape keys, and the message says so; LOD0 keeps all of its keys.

A mesh with a parent (a wheel on a car) keeps it: the LOD group takes the mesh's place under the parent. Before, Generate cut the mesh loose and it jumped by the parent's offset, and Remove LODs left it without a parent. Objects you parented to the LOD group stay under the rebuilt group.