This might be a bit technical but bear with me.

Currently, search paths are stored under single registry keys as semi-colon separated strings. This was great in the past when there was just "AutoCAD", but more recently with multiple third-party applications, in-house resources, deeply nested folders, etc. these single strings have grown large enough that managing them is becoming difficult.

What I propose is a change in the way the path storage is organized. Each of these semi-colon separated strings would be replaced with a single "parent" registry key, with each folder as another "child" key beneath the parent. Each child folder key would have a string value, holding the path; an optional string value, holding a reference name for that folder; a zero-based integer, holding the index value of that folder in the search tree; an integer, indicating how many levels of sub-folders to look into for nested searches. Alternately the integer index value may be dispensed with if the children keys are named with index values; the reference name may be used for the child key name.

This configuration would allow for a number of benefits. First, it would simplify tweaking profile settings in both the registry and ARG files since each path can be manipulated individually. Second, it would simplify the method of moving folders "up" and "down" in the configuration dialog by changing index numbers under individual keys rather than pulling a string value/separating it/re-sorting/compile to string/write new value. Third, it would simplify the process used by CAD Support people to pull a specific folder through calling a reference name (like "Client blocks"), rather than searching the entire tree. Fourth, it would allow a nested search option for finding files in some sub-folders without needing to search all sub-folders.