FatalLog not works

Results 1 to 5 of 5
  1. #1
    Newbie lolkabolka is offline
    MemberRank
    Jul 2012 Join Date
    3Posts

    FatalLog not works

    Hi guys!

    We have problems with the unique ranking.
    As i see, every midnight, the server creates the fatallog.

    Yesterday we summoned a unique monster (a war golem), and killed him with a GM.
    Today i checked the logfile, the fact of summoning is in the file, but the kill is not.

    Somehow, the unique kills not logging.

    My questions:
    - what makes this error?
    - is there a tool, what can make a fatalLog file for me? not good to wait a day always, if i want to test.
    - if no tool, where can i find theses informations. is the server store it in the DB?

    thx


  2. #2
    Elite Member benike1 is offline
    Member +Rank
    Dec 2006 Join Date
    163Posts

    Re: FatalLog not works

    when a gm kills a unique, you won't see it in fatallog.

  3. #3
    Elite Member antoha is offline
    Member +Rank
    Oct 2007 Join Date
    Ukrain, KievLocation
    153Posts

    Re: FatalLog not works

    Aiight so here's the deal: Fatallogs aint logging unique kills since ur probably using evagilion patch to gm, in witch case the logs are being saved inside a txt file in evalog folder. Log them and insert to database u can use my php tool to log uniques (look for it in the release section) or any other simular tolls, there are some of them out there.Like if I helped.

  4. #4
    Elite Member K4bo is offline
    Member +Rank
    Apr 2012 Join Date
    EgyptLocation
    239Posts

    Re: FatalLog not works

    if you kill a unique with a command or even a weapon you won't see it in the game
    Note: the server saves from the GS and the GS doesn't save GM kills.

    got it ?

  5. #5
    Newbie lolkabolka is offline
    MemberRank
    Jul 2012 Join Date
    3Posts

    Re: FatalLog not works

    thank you guys.

    unfortunetly, there are not any unique kills in the files. somehow, it doesnt't logged.
    Last edited by lolkabolka; 23-07-12 at 03:03 PM. Reason: misspelled



Advertisement