is this supposed to be used in the same way as !recycle?
flatface's site with the newer litestep docs seems to be down at the moment but looking at the shellfront docs it refers to the step.rc.
does this mean that refresh is a pre-ots2 bang only?


what i want is to change theme settings without recycle, a command like this though:

*Popup "border off" !Execute [!textreplace @$ConfigDir$themevars.rc@ @(border)(.\>)(000000)@ @\1\2 ff00ff@][!Refresh]]

cause litestep to hang with 100% cpu usage.

is there an alternative way that it's possible to change settings like this or is recycle the only option?

!refresh never really worked.
practically no one uses it at any level.
so many module coders probably don't care about it.
stay away.
the major problem is that not all modules support it; so when you call !refresh, all modules have to do something, or at least that seems to be the case. so you're lucky if the modules you do use play nicely.

on a per-module basis you could !reload
and then reload your module; NetLoadModule has a bang for that, if you use NLM.

do that only if the module in question doesn't provide its own mechanism for refreshing itself.

!varsaveall, !reload, then !netunloadmodule on all modules, and if any are hooked, hiding them and destroying the box hooked to first, then !netreload each one.
I set up a script to do iterations of this (save system time at start, then add one each time mzScript was loaded, if the number wasn't equal to the total, do it again--if it wasn't, save the time to another variable), and the difference between !recycles and scripted !reloads was under 10% (7%, IIRC, doing 1000 of each). The hard drive is the bottleneck each way of doing it, I think, as both methods access it like mad.

So overall, you're better of with !recycles, and using features that don't need !recycle/refresh whenever possible.
...and if the HD is in fact the bottleneck, then the OTHER answer is, of course, SCSI :P.

thanks for that guys.
i had actually tried using the !reloadmodule bang but i didn't use it in conjucntion with !reload.

i guess without !reload the modules don't re-check the rc files and just load then go back to what they were doing beforehand