I'm stumped! I'll have to try out Linux mint 21 in a VM and see if I can recreate it.

I do see a similar error after having installed eqalert with a venv and not sourcing the venv after trying to run in a new terminal session.

hrmm maybe I installed in the venv first... Thats possible.. anything I can try to check it out?

If you installed using the below command earlier in the thread using venv:

Then you would need to cd back into the eqalert directory, verify a .venv/ directory exists and source it before running eqalert using:

EQAlert version 3.6.1 is out:

Please submit any bug reports or problems to this thread or to github issues

Will this ever have kill spawn timers? just wondering as thats a feature I really like from GINA

There are automatic timers set by the encounter parser for a given mobs death, but it is based on a zone wide duration in seconds. The duration per zone is sourced from the config/zones.json file and the options to enable it can be toggled on the settings pane or in the settings.json. Pressing `y` while in the events pane will also toggle mob respawn timers.

Otherwise, you can use `/say parser timer [seconds]` to create a manual timer for mobs, or for misc use in hotkeys.

If it's neither of those, I'd be happy to add an issue to the repo and get what you have in mind added!

installed it today, and i get this error when i try to run it: write config line alert: Error on line26644: [Errno 13] Permission denied: '/home/username/.eqa/config/settings.json' -> '/home/username/.eqa/config/archive/unknown//settings.json'
config read: Error on line 69: Unexpected UTF-8 BOM (decode using utf-8-sig): line 1 column 1 (char 0)
Unfortunately, the startup step failed with: 76: 'NoneType' object has no attribute 'settings'# Sometimes this is solved by forcing config regeneration

It looks as though this is a bug in config generation, where it is attempting to archive an old set of config files which do not exist. Here is the section of code not behaving as it should: https://github.com/mgeitz/eqalert/bl...#L26623-L26644

I'll create an issue to track resolution here, there should probably be some added checks to ensure `old_version` and `config_name` exist prior to attempting to archive any old configs rather than just checking if a file with that name exists.

For the interim, try deleting all of `~/.eqa/config/` to force a regeneration of fresh config files. If a file with the config filenames don't exist, the parser shouldn't try to archive them before generating new ones.

Resolution of this bug will be tracked here: https://github.com/mgeitz/eqalert/issues/232

EQAlert version 3.6.2 is out - it is entirely bug fixes and project upkeep, no new features yet!

Thank you. I deleted the folder you mentioned and it created a new problem, but deleted the install folder and installed the new version and it is working finally. Time to play around with it :)