However I still believe, if you really wanted to, you could add a 1s delay between acquiring the writ and reading the recipes it calls for, but hey, I'm not a coder.
This was my request and will remain as such, no reason to get upset. It's your script and your choice. I can respect that.
Ok, I see I must explain this yet again in plain english.
1) We accept writ quest.
2) Server sends quest update packet.
3) ISXEQ2 intercepts decoding of quest update packet.
4) ISXEQ2 throws a quest update event, to be intercepted by craft. This event contains everything that the eq2 client has decoded from the quest update packet.
5) Craft parses all the data passed in from ISXEQ2. In the case of high latency, this contains exactly nothing, due to the packet being broken by the latency and the eq2 client not locking itself up for 1+ seconds to receive the rest of the packet. Delay at this point would simply delay parsing the nothing.
It may actually be theoretically possible for Amadeus to intercept the quest update packet further down the line, after the entire packet has been received and decoded (e.g. when the dynamic data gets updated), and that would fix the issue without adding ANY delays into craft. This is mere conjecture on my part, and may not even be possible at all. Amadeus would know for certain.
I understand the confusion about this, as it seems it should be possible to script around a little latency. The fact remains that this is NOT a craft feature request, nor a craft bug report. This belongs, if anywhere, in the ISXEQ2 bug reports. I'd actually recommend posting it there so it doesn't get buried and forgotten.
Oh, and I tend to get nasty when people post requests for things that I've already explained in the past are impossible, with very similar words to the ones I've just typed. Again.