First off, thank you both for the reply. I am guessing the loot popups are turned off and I didn't seem to find the loot management panel. Thanks very much for the pointer, I'll find that.
The reason I'm asking about the raid note is that, in our guild's system, all raid attendees are awarded a set number of points for attending a specific event. Say Naxx is worth 10 points.
Ok, in EQDKP I can go in and set the event and upon upload the nax value in the export string matches the nax event set in the dkp system and 10 becomes the value that everyone earns. No issues there.
The sticking point is when we decide that the raid is, for this night only, worth MORE (or less) than that default value. We'll do this periodically when we run over our hard stop time to get a mob down or to get an attempt or two on a new boss. In these cases my raid tracking guy wants to be able to set, in game, the new point value for the raid. Generally in CTRT we'd do this in the raid note, and I've modified our copy of eqDKP to accept the raid note and parse the note for a value string. Admittedly however I am very new to eqDKP, is there a more generally accepted way of changing the event cost for a specific event for a specific night? I realize this is not the eqDKP forums, but I ask that to emphasize what benefit the raid note provides or to solicit ideas for a "better" place to attain this cost. I realize the standard answer here would be "upload the string and change the value before you parse the final upload" but that doesn't keep the note in the raid tracking application which provides a "backup" to the data imported online.
As to the automatic raid start/end/recovery. I can only give you incidental evidence of what I am saying: I appreciate and fully understand the explanation of how and when the LUA variables are written out to disk, however I have 2 raids right now in HeadCount that are split raids across crashes/logouts (I forget which) that are NOT split in my CTRT window. This leads me to believe that CTRT is handling things differently from HeadCount, and in this regard the CTRT application seems to be handling it better in some way. I can't speak to how or why, only that this IS happening. And again I only identify this mostly as an "FYI" to you as the app developer that there might be a better way of handling the raid split issue.
In either regard the answers above go a long way to allowing me to switch over from CTRT to HeadCount.
Thanks again for a well developed and good looking raid tracking alternative application.