What I am trying to do with A25 tools is set up quests where you move from clickie to clickie within a scene, doing something at each station that changes the status and/or visibility of all the clickies, especially turning OFF a clickie just used. Normally you would expect this to be via a key reset. However, using npctalk dialogs, the refresh (to show new key status) is delayed after exiting the first clickie by up to 20 seconds, and if you enter the next clickie/npctalk the refresh will interrupt the second npctalk at a random place -- not good.
This is easily demonstrated at bug gardens, where improving one plot and moving too quickly to the next plot causes interruption of the second plot's npctalk. I explained this away as "heat stroke from working too hard" and encouraged players to slow down, but....
When the last box of an npctalk ends with a reset w/refresh command, the text on that final box vanishes quickly, before a long text could be read. This is annoying, but can be worked around.
However, refreshes seem to occur for other reasons than triggering by npctalk. Some scenes seem to have an extra refresh built in (possibly the case at Deathmarrow?), possibly due to other stuff going on there. In NC in particular, each step gives a dialog box about ap being lost, then later a delayed refresh.
BSR seems to be running a system/browser/interface (?) that gets more refreshes than what I'm running (mac/os High Sierra/Chrome). To test this sort of thing, you'd need someone with access to multiple portals to the realm. I'm not sure where to start. {Edit: Death Ray running a Chromebook with Google Chrome does not have this issue either.}
My suggestion is to simply make refreshes BLOCKED (or perhaps held off) while an npctalk is running, then run all the saved up ones IMMEDIATELY after exiting npctalk.