EQ Alert - Log Parser
EQ Alert - A Configurable and Context Driven Project 1999 Log Parser with NCurses Interface (for Linux)
I've been periodically chipping away at a parser over the last 5 years with the goal of putting something together that can eventually understand every type of line in this games log file, and sometimes doing something about that. https://i.imgur.com/TtUwq12.png Features as of 3.1.3: - All python - TUI - google TTS - config.json to customize alerts - character state - encounter parsing - /say commands - default zone timers - metronome Installation: $ pip3 install eqalert or $ git clone git@github.com:mgeitz/eqalert.git $ cd eqalert $ python3 setup.py install --user More Information: Source code & Readme: https://github.com/mgeitz/eqalert Road Map: https://github.com/mgeitz/eqalert/projects Contributing: If you're interested in contributing in any way to this project, please do! As of version 3.1.3 there are ~598 elif statements! Issues & Requests: https://github.com/mgeitz/eqalert/issues Contributing: https://github.com/mgeitz/eqalert/bl...ONTRIBUTING.md |
|
This looks immense!
|
|
Just about all spell text should be matched by the parser now as of version 3.2.5!
|
Impressive!
|
Looks promising! Will try it out
|
Version 3.3.5 added features:
If you have any thoughts, feature requests, or issues please let me know - I'll get anything not yet on the road map added! |
Quote:
Code:
write config line alert: Error on line13130: not enough arguments for format string Edit: missed a "s" |
I'm using python version 3.7.3 when running locally. Looking at the error it seems like the following might not be working as expected:
``` import pkg_resources version = str(pkg_resources.get_distribution("eqalert").vers ion) print(version) ``` I'll get an issue added to the repo to track this down; there's probably a better way to report the package version than the first thing I found through google and the python requires in setup.py should be narrowed to a tested range rather than >3. Just in case it's helpful, here is a gist to each generated config file. Everything should be set to directly copy down sans the settings.json file, you'll want to spot check the paths set in there. If it is an issue with pkg_resources, I'd expect starting things up with the configs will get it far enough to initialize logging and might provide better debug output in ~/.eqa/log/eqalert.log EQ Alert 3.3.5 Config Files (Settings has placeholder values): ~/.eqa/config/settings.json ~/.eqa/config/zones.json ~/.eqa/config/line-alerts/chat-received.json ~/.eqa/config/line-alerts/chat-received-npc.json ~/.eqa/config/line-alerts/chat-sent.json ~/.eqa/config/line-alerts/combat.json ~/.eqa/config/line-alerts/command-output.json ~/.eqa/config/line-alerts/emotes.json ~/.eqa/config/line-alerts/group-system-messages.json ~/.eqa/config/line-alerts/loot-trade.json ~/.eqa/config/line-alerts/other.json ~/.eqa/config/line-alerts/pets.json ~/.eqa/config/line-alerts/spell-general.json ~/.eqa/config/line-alerts/spell-specific.json ~/.eqa/config/line-alerts/system-messages.json ~/.eqa/config/line-alerts/who.json I think that should be each of the config files which keep the version string in them for regeneration following new versions. |
All times are GMT -4. The time now is 03:58 AM. |
Powered by vBulletin®
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.