[DGD] Changing the driver/auto object at runtime

[Raymond Jennings]

So far, it appears that the "driver object" handle only persists
during a single runtime of the driver and is reset, so if you fiddle
with the config file and pick a new driver object, the next boot with
that config file will direct all driver calls to the new driver (if
necessary compiling it first), even in the event of a warm/hot boot.
On Sat, Nov 3, 2018 at 12:38 AM Raymond Jennings <shentino at gmail.com> wrote:
>
> What sort of support/caveats would apply to changing the driver and/or
> auto object of a running mud at runtime?
>
> By this I mean via warm/hot boot.