I am the author of
LibArtifactData-1.0. Some issues were reported and it all appears to boil down to artifact data becoming prematurely unavailable. I have a guess what is causing this and would like to know if it is reasonable to assume that.
1. When ARTIFACT_UPDATE is fired, it means that artifact data is available and handlers for that event are queued for execution.
2. If an event handler uses C_ArtifactUI.Clear(), the artifact data becomes unavailable and handlers that are still queued will get nils.
If this is how it works, it means I can't rely on updating the artifact data or getting it at all, right? Is there something I can do about that?