@handjonathan
The biggest thing to me is the ability to run acaddoc.lsp on startup. That allows you to make a self healing system at a company. What I do is also load a .lsp by users login name at the end, so they can then do their tweaks after the company stuff, so they have control in the end.
Then I can load company menus, check variables, all kinds of stuff.
For those who have loved the WT IT set of tools, I attached our latest rendition for LT people.
The idea is these replace the clipboard copy and paste, which is easily overwritten.
This uses wblock methods whose files sit there forever until you overwrite.
It even has a network location for copy and paste between different users (WTN and ITN).
Take a look at the code, the commands are at the top.
If I were autodesk, I would add the VLIDE to LT. You already made the decision that lisp in LT is good, so helping those users to do more lisp is more betterer. You get people going on lisp and they discover .net quickly. Then you sell them upgrade to full acad. Don't miss that boat! Also, you tempt them to try the Bricscad lisp environment so careful there.
internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties