Seer is a server bot that tracks monster kills, player deaths and quite a bit of other information.
It was recently discovered that the "kill log" function wasn't working. For reasons we are not sure of, the bot stopped updating this log.
Going forward, the kill log is functioning as expected but the historical data is not available at this time.
Please keep this in mind when using the reporting function from Seer.
kills <name> to see what a player or monster has killed and how
numkills <name> to see how many times someone killed
how killed <name> to see how someone prefers to kill
deaths <name> to see who killed a player or monster and how
numdeaths <name> to see how many times someone died
who killed <name> to see who killed someone
what killed <name> to see what attack caused someone to die
Thanks.
Problem with tracking kills with Seer
Moderators: Board moderators, Metalforge staff
-
Leaf
- Forum Aficionado
- Posts: 1994
- Joined: Tue Apr 29, 2003 5:55 pm
- Location: Minnesota, USA
- Contact:
Problem with tracking kills with Seer
"Put another, more succinct way: don't complain, contribute. It's more satisfying in the long run, and it's more constructive."
Eric Meyer
Eric Meyer
-
Leaf
- Forum Aficionado
- Posts: 1994
- Joined: Tue Apr 29, 2003 5:55 pm
- Location: Minnesota, USA
- Contact:
Seer went a week without any issues or problems with logging monster kills.
Seer is currently residing on a new host with more processing power and that appears to have been the problem.
Parsing a 12Mb log file was a little much for the Celeron 700Mhz.
Seer is currently residing on a new host with more processing power and that appears to have been the problem.
Parsing a 12Mb log file was a little much for the Celeron 700Mhz.
"Put another, more succinct way: don't complain, contribute. It's more satisfying in the long run, and it's more constructive."
Eric Meyer
Eric Meyer