He's jesting by implying that Zathras means the LurkerTracker doing that before they die, I would assume.
Heheh, yeah. Try the new
LurkerTracker today! Now with Extra-Clairvoyance! That'd be great. 8-)
About the rest:
If they're town, find every time their name is in a line and color it. Then check that line for their role-name and color that. Might get buggy if there's a long line containing many players with a mafia and town player sharing the same role, so consider splitting the morgue into multiple lines with a townie line, mafia line, and a third-party line.Actually the code doesn't check to see if someone is dead and what role they are; the person using the lurkertracker actually feeds that information in a section of the script that replaces certain names with others, in order for the tracker to handle replacements and who is a mod and such.
I suppose a quick bridge that the user could do for this is to type it in the script as,
Dead_Scum => "[color=red]Dead_Scum[/color]: dead, scum"
in the Replacements Considered section, and then it would naturally come out as
"Dead_Scum: dead, scum" when the lurkertracker report is posted.
It's just that that particular solution is just more work for the person using the lurkertracker... It's probly viable, but I think Zath wants the lurkertracker to determine for itself who is dead and what role they were and such, which is a much harder task unless of course all moderators agree to use special keywords to indicate this stuff.
Arg is right. You
can colour them manually (or do anything you want with the BBCode) right now, when you record their flip. In fact, I did something like that in the last Sorcerer's with the school colours:
see here.What's hard is mostly because I've refrained from creating "fields" with extra information like death or day/night or anything else; right now it just uses substrings in the player's name/flip for its decisions. Painting a colour based on a substring is clunky but doable; starting to treat it like a database-aware thing on the other hand would be a major rewrite, but pretty much a prerequisite for all the other "hard" things.
The last easy goal, and hard goals #1 and #2 would be absolute blessings for the end-user. I would say focus on those first, and then once the LurkerTracker is easy, fun and safe to use, then work on the other goals (mostly because the other goals, especially
(Referring to config files, and real-time fetching)
Yeah, I should. The config files I know how to do, and will eventually be in, I'm just lazy about it and don't like the idea of start adding parameters. I used to like how the script was lean and simple, but that ship sailed a version or two ago, I guess.
About the others, getting the stuff in real time and doing without the preprocessing, I don't even know where to start. Maybe someone who knows more than I will give it a whirl, or I'll get some inspiration one day, but I wouldn't hold my breath.