Lailloken / Lailloken-UI

Path of Exile UI and QoL overlay. Emphasizes ease of use, minimalist design, and seamless integration.
MIT License
592 stars 28 forks source link

Track kills per map ? #251

Closed anon1278542390 closed 1 year ago

anon1278542390 commented 1 year ago

Hi,

I have a similar issue. My kill command result does not have the comma as thousands seperator. Each time i finish a map, I get 0 kill.

Do you need more info? Is this a bug?

Discussed in https://github.com/Lailloken/Lailloken-UI/discussions/120

Originally posted by **GrimDawn-max** November 12, 2022 Could you add a feature that tracks kills per map and include it in the loot stats export file. The stat exists manually of course via the /kills command but you also have to remember to execute it before you kill anything in a map and again at the end so an automated way to do so would be handy.
Lailloken commented 1 year ago

Can you upload a screenshot of when you first click the flashing timer after entering a new map, and another one of when you click it again after exiting a map? image

image

anon1278542390 commented 1 year ago

image image

Lailloken commented 1 year ago

Huh, that's interesting. Which language settings are you using in Windows (just out of curiosity)?

You can download this dev-version which should fix this issue. It also changes how the kill-tracker is started: instead of clicking the flashing timer, there will be a reminder-tooltip asking you to press the omni-key to activate the first /kills command.

There is no documentation of further changes at the moment, but I don't think there was anything major (it's been a while since I have worked on it because I suddenly lost interest in the league and took a break).

anon1278542390 commented 1 year ago

French (Canada).

anon1278542390 commented 1 year ago

Still 0 kills. I switched on the dev branch in github. image

Lailloken commented 1 year ago

Then it's probably using a character as thousands separator that's not rendered in the chat-box. I have updated the dev branch again, this time with a fix that should universally solve this issue.

anon1278542390 commented 1 year ago

Yup, it's fixed now. Got a nice drop with it too :) image