This is perhaps one of the most frustrating and maddening things I've experienced yet. I have a couple of testers that so far, no matter what we do other that use the console, my quest will not start as it should. Here's the script:

Scriptname BalokMQ101ChechSCRIPT extends QuestQuest property MQ102 autoQuest Property BalokCourierTimer  AutoQuest Property BalokMQ101Check  AutoEvent OnInit()		    RegisterForSingleUpdate(10)EndEventEvent OnUpdate()		  if MQ102.GetCurrentStageID()>=5				    BalokCourierTimer.Start()				    Debug.Notification("Courier Timer has started")				    BalokMQ101Check.Stop()																									    		    else				    RegisterForSingleUpdate(60)				    Debug.Notification("MQ102 is not set")				    Return  		    endifEndEvent 

All that does is check for the stage and starts my timer quest. This script have NEVER failed for me. Not Once. But even though sqv MQ102 or getstage says MQ102 is clearly >= 5, it refuses to start my timer quest for them. I've even gone as far as practically duplicating one testers load order, and it still works perfectly for me, but not for them.

WTF could it be, or how the hell can I determine why it is failing. It just don't make any sense whatsoever to me. NONE.