I would like to fly like a bird, and I would like a QLab OSC and script cues to have the means of knowing their own cue numbers. I think its safe to say none of these things are going to happen, the first because well you know..., and the second, because for the past seven years we have used various tortuous methods to get round this problem, and no simpler method has ever been forthcoming!
There is a workaround for what you want to do, which comes at the cost of a tiny bit of latency,
Create a network cue patched to your Dlight and number it DLight
Where you would have used your pseudo OSC /seq/X2LoadAndFireID #/cue/my own number/number# use a script cue with this instead
--set the custom message of cue DLIGHT to either the q number of the script cue if it has one, or the q number of it's parent if it doesn't, and then start cue "DLIGHT"
tell application id "com.figure53.QLab.4" to tell front workspace
set mycue to (last item of (cues whose running is true and q type is "script"))
if q number of mycue is "" then
set mynumber to q number of parent of mycue
else
set mynumber to q number of mycue
end if
set the custom message of cue "DLIGHT" to "/seq/X2LoadAndFireID " & mynumber
start cue "DLIGHT"
end tell
Mic