-
Notifications
You must be signed in to change notification settings - Fork 8
Home
A Configurable and Context Driven Project 1999 Log Parser with NCurses Interface for Linux
Install from pypi
$ pip3 install eqalert
or install manually from github
$ git clone [email protected]:mgeitz/eqalert.git
$ cd eqalert
$ python3 setup.py install --user
Start things up
$ eqalert
You should now see ~/.eqa/
with the following structure
$HOME/.eqa
⎿ config/
⎿ line-alerts/
⎿ data/
⎿ encounters/
⎿ log/
⎿ debug/
⎿ sound/
Spot check these default paths generated in config/settings.json
"settings": {
"paths": {
"eqalert_log": "[$HOME/.eqa/]log/",
"data": "[$HOME/.eqa/]data/",
"encounter": "[$HOME/.eqa/]encounters/",
"everquest_logs": "[$HOME]/.wine/drive_c/Program Files/Sony/EverQuest/Logs/",
"everquest_files": "[$HOME]/.wine/drive_c/Program Files/Sony/EverQuest/",
"sound": "[$HOME/.eqa/]sound/",
"tmp_sound": "/tmp/eqa/sound/"
},
Press
0
to reload your configs or restart the program if any changes were made. Though generally, it's a good idea to stop eqalert before manually editing your config files.
EQ Alert will generate a file for spell timers in ~/.eqa/data/spell-timers.json
by default by parsing spells_us.txt
in your EverQuest directory.
This file will only regenerate if it is missing, malformed, or a newer spells_us.txt
file is present.
- 0 : Reload config
- 1 : Events
- 2 : State
- 3 : Parse
- 4 : Settings
- q / esc : Quit
- h : Help
- c : Clear event box
- d : Toggle debug mode
- e : Toggle encounter parsing
- m : Toggle global audio mute
- p : Toggle encounter parse save
- r : Toggle raid mode
- t : Toggle automatic mob respawn timers
- up : Up in selection
- down : Down in selection
- right : Selection options
- left : Selection options
- space : Select
- enter : Select
- tab : Cycle category
Note: WASD or arrow keys will work
You can control some parser settings using /say
in-game. This is better suited for one monitor setups.
/say parser raid
- Toggle raid mode
/say parser debug
- Toggle debug mode
/say parser mute/unmute
- Toggle global mute/unmute
/say parser mute/unmute speak
- Toggle mute/unmute on all speak
alerts.
/say parser mute/unmute alert
- Toggle mute/unmute on all alert
alerts.
/say parser mute/unmute line
- Mute all sound alerts from a type of line
example: /say parser mute engage
/say parser mute/unmute line player
- Mute all sound alerts of a given line type from a specific source
example: /say parser mute tell indef
/say parser mute clear
- Clear all muted line types and players
Does not effect global mute
/say parser encounter
- Toggle encounter parsing
/say parser encounter clear
- Clear the encounter stack
/say parser encounter end
- Sometimes, your logs don't catch an encounter end. Use this command to fix that!
/say parser metronome [seconds]
- Set a tick/tock metronome with interval of [seconds]
/say parser metronome stop
- Stop the metronome
/say parser timer [seconds]
- Set a timer for [seconds], says "times up" when done
/say parser timer clear
- Clear all timers
/say parser timer respawn
- Create timers for the default current zone time after seeing an experience message. Timer response is "pop [zone name]"
/say parser timer respawn stop
- Stop creating mob respawn timers automatically
/say parser consider
- Toggle consider evaluation
/say parser what context
- Speak context state
/say parser what state
- Speak everything in the state object
/say parser hello
- Hello
/say parser who
- Who am I?
/say parser where
- Where am I?
Modify ~/.eqa/config/line-alerts/*.json
to customize alerts.
Due to how many line matches there are, the configuration for their reactions have been split into several json files under [$HOME/.eqa]/config/line-alerts/*.json
Anything matched by the parser not found in configuration is automatically added to [$HOME/.eqa]/config/line-alerts/other.json
Modify line_type
values to customize alerts accordingly.
Example configuration for a line type:
"line_type_name": {
"alert": {},
"reaction": "false",
"sound": "false"
},
-
false
: Disable alerting for this line type -
alert
: Alert for matching strings inalert
for the line type using the set sound -
all
: Alert for all lines of a given line type using the set sound
-
solo
: Alert when solo, grouped, and raiding -
solo_only
: Alert only when solo -
group
: Alert when in a group and raiding -
group_only
: Alert only when grouped -
solo_group_only
: Alert only when not raiding -
raid
: Alert when in a raid -
afk
: Alert only when afk
alert
can be populated with key value pairs. The key here is any string you would like an alert for within that line type.
Alert for the word hey
when someone else /says
it:
"say": {
"alert": {
"hey": "true"
},
"reaction": "alert",
"sound": "hey"
},
Alert for the word run
when someone else /says
it and you are grouped or in a raid:
"say": {
"alert": {
"run": "group"
},
"reaction": "alert",
"sound": "oh god run"
},
Alert for a spell not taking hold only when grouped:
"spell_not_hold": {
"alert": {},
"reaction": "group_only",
"sound": "true"
},
Alert for the item Hand Made Backpack
when someone else /auctions
it and is selling:
"auction_wts": {
"alert": {
"Hand Made Backpack": "true"
},
"reaction": "alert",
"sound": "wow buy that"
},
More examples can be referenced in the default config
-
false
: Disable alerting for the string (does not negate line type reactions) -
true
: Alert for the string
-
solo
: Alert when solo, grouped, and raiding -
solo_only
: Alert only when solo -
group
: Alert when in a group and raiding -
group_only
: Alert only when grouped -
solo_group_only
: Alert only when not raiding -
raid
: Alert when in a raid -
afk
: Alert only when afk
-
true
: When an alert is raised speak the entire line -
false
: Play no sound when an alert is raised
Any other sound value will be spoken as the audio trigger for that line type
This line type behaves the same as any specific line type configuration, but configuration here will be used against all log lines.
For example, the below configuration will alert if the word help
is found in any line while in a raid context, even if that line isn't matched to a type by the parser.
"all": {
"alert": {
"help": raid
},
"reaction": "alert",
"sound": "help is needed"
},
This can be helpful if you would like to alert for something not yet matched by the parser, though your contribution to a new line type match in the parser would also be welcome!
Zone data is stored in config/zones.json
-
false
: If enabled, auto-disable raid mode in this zone -
true
: If enabled, auto-enable raid mode in this zone
-
#
: The value in seconds to associate to a default timer in a given zone
Note: No support for zones with multiple default timers, stick with the manual timer command for those for now. For zones with tiered default timers, the shortest timer was set as the default. You can change this value to be any number in seconds you prefer.