Hey, another toy!

This one is pure silly, but a most useful program for debugging DragonSpeak. The program tags all your emits in the program with an indicator to let you know where which emit came from.

((2:12) (3:13))

And that means that the emit is from the second trigger in the DS file, located at line 12, and it's the third emit in the script, located at line 13.

Don't mess with the format of the line, the program also removes them, based on pattern, you mess up the pattern, you mess up the ability of the program to remove it.

More stuff to do with the program. It now will generate emit tags for selected (0:xx) causes, whichever ones you want at that. However, it's an all or nothing deal, if you want to catch instances of:
(0:1) Whenever somebody moves,
You're going to get every one tagged. The tags are inserted at the bottom of each chuck, so if you have stacked (0:xx) & (1:xx) elements to common some effects, it will be at the bottom of that chunk.

(0:1) Whenever somebody moves,
 (1:19) and the triggering furre (moved from/is standing at) position (66,81),
 (1:113) and the triggering furre is not facing northeast (up and right),
 (1:18) and the triggering furre (moved from/is standing at) object type 2422,

(0:1) Whenever somebody moves,
 (1:19) and the triggering furre (moved from/is standing at) position (62,81),
 (1:113) and the triggering furre is not facing northeast (up and right),
 (1:18) and the triggering furre (moved from/is standing at) object type 2422,

    (5:350) set variable %closer to the X,Y position the triggering furre (moved from/is standing at).
  (3:2) at position (%closer) on the map,
    (5:5) change object type 2422 to type 2421.
    (5:352) move the position in variable %closer northeast (up and right) 1 step(s).
  (3:2) at position (%closer) on the map,
    (5:5) change object type 65 to type 66.
    (5:430) jump the animation of all copies of object type 2421 in the dream to step 13.
    (5:50) set countdown timer 116 to go off in 1 seconds.
    (5:11) play sound 3 to every furre who can see the triggering furre.
(5:204) emitloud message {((69:506) (0:1)) / ((70:511) (0:1))} to everyone on the map.

The format for the cause tagging is a tad different, the first two numbers is the Cause count, not the count of causes that you've selected, but every cause the program has reached in getting to your selected statements. The second number is line of the cause itself. The second set of numbers is the cause. When the program tags multiple causes for chunks like the above, it will put each one in the same emit, separated with " / ".

Oops, bug fix required, the index changing count, ...

Bug fixed. Program now will generate the proper index for each cause selected from the list.

Notation, the program inserts emits into your DragonSpeak, this may cause the number of lines to exceed current limits for uploading dreams, either forcing the upload to being in test mode when uploaded, or worse, end abruptly. So when you upload, check the number of lines reported by the server on entry. You won't see this issue if you're tagging emits, and using inline emits, the tag is part of the emit itself.

Fetch The Program.

Please report any bugs on the Furcadia Forum please.