I posted this in another thread, but this spot seemed just as (if not more) appropriate...

Why not have the program output an act-export.txt file for every 16 lines of the parse? So if there are 24 combatants, it could be handled with two separate /do_file_commands statements:

/do_file_commands act-export1.txt
/do_file_commands act-export2.txt

Could bind each one of these to a macro and a hotkey, so to dump the whole raid parse, you'd hit the first key followed by the second key. This way we could dump out up to 32 lines (or more!) and get the complete raid parse for a 24 person group.

The ability to make the files is already there... it just simply needs to be extended to dump out another file for every 16 lines in the parse.

I also have two suggestions for the HTML output to a web server... First, can you add an option to list the encounters on the index page starting from the most recent and working down? If you keep lots (20+) encounters, you have to keep scrolling down to the bottom to find the more recent encounters. Second, is there some way that you could make a copy of the most recent parse every time it's uploaded in a file called "lastencounter.html", so we could just stay on that encounter and hit the refresh button, instead of going back to the index, hitting refresh, then clicking on last encounter? One more problem I've noticed is that if I'm playing on a different character than my main, the graph image shows my main's name, with no data, yet the lines of data show the current character (and group) that I'm playing on.

Great program by the way... love all the features!

Jh

Jhaerel wrote:

I posted this in another thread, but this spot seemed just as (if not more) appropriate... Why not have the program output an act-export.txt file for every 16 lines of the parse? So if there are 24 combatants, it could be handled with two separate /do_file_commands statements: /do_file_commands act-export1.txt /do_file_commands act-export2.txt Could bind each one of these to a macro and a hotkey, so to dump the whole raid parse, you'd hit the first key followed by the second key. This way we could dump out up to 32 lines (or more!) and get the complete raid parse for a 24 person group. The ability to make the files is already there... it just simply needs to be extended to dump out another file for every 16 lines in the parse.

I'm not imposing the limitation... the EQ2 servers are. You will not be able to send public chat even by normal means immediately after using a macro with a full 16 lines.

How soon after the first 16 lines could you send the remaining 8 or 9 lines though? If they were done as two separate macros, you could send the first 16 lines by pressing one button, then wait 2 or 3 seconds (Could even have a beep from the program that lets you know enough time has passed) and then press another button to activate the next macro that runs the second macro file with the rest of the parse.

Jh!

It might be less than 30 seconds... I never really studied it much. It's certainly not 2-3 seconds though.

Ok, so that might not be viable since anything more than about 5 seconds could be too late for some people...

What about the other ideas for the html output? Since we can't dump the whole raid out, the next best thing would be that one of the files that gets uploaded with the rest of the html stuff should be called "latestencounter.html", and should have a narrow view (or customizable) of the encounter, so that the raid members could keep the window small... Then they could just hit the refresh button after each encounter to get the info on it. (Or optionally, have the page auto-refresh itself, like your internal server does?)

Just some thoughts, trying to think of a way to make the whole raid output available to everyone in a format that they don't have to be too "technical" to use.

Jh!