Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can you change korean trade regexes? #297

Closed
luensys opened this issue Aug 19, 2022 · 1 comment
Closed

Can you change korean trade regexes? #297

luensys opened this issue Aug 19, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@luensys
Copy link

luensys commented Aug 19, 2022

🐞 bug report

Describe the bug
Korean trade regexes was changed several league ago.
So korean trade whilper is not working

To Reproduce

Steps to reproduce the behavior:
src > asserts > poe > trade-regexes.jon

Expected behavior
tradeBulk

^안녕하세요, (?.)리그의 (?\d) (?.)(을)를 (?\d([.|,]\d*)?) (?.)(으)로 구매하고 싶습니다(?.)?
ex)
안녕하세요, Standard 리그의 200 카오스 오브(을)를 520 지도제작자의 끌(으)로 구매하고 싶습니다.
https://regex101.com/r/u6TSKR/1

tradeItemPrice
^안녕하세요, (?.) 리그의 (?.)(을)를 (?\d*([.|,]\d*)?) (?.)(으)로 구매하고 싶습니다(보관함 탭 "(?.)", 위치: 왼쪽 (?\d*), 상단 (?\d*))(?.*)?
ex)
안녕하세요, 스탠다드 리그의 비호의 오로라 용사의 연모양 방패(을)를 3 chaos(으)로 구매하고 싶습니다(보관함 탭 "~price 3 chaos", 위치: 왼쪽 23, 상단 1)
https://regex101.com/r/67r6Qu/1

tradeItemNoPrice
^안녕하세요, (?.) 리그의 (?.)(을)를 구매하고 싶습니다(보관함 탭 "(?.)", 위치: 왼쪽 (?\d), 상단 (?\d*))(?.*)?
ex)
안녕하세요, 스탠다드 리그의 비호의 오로라 용사의 연모양 방패(을)를 구매하고 싶습니다(보관함 탭 "판매", 위치: 왼쪽 6, 상단 7)
https://regex101.com/r/jbOeJp/1

Screenshots

🌍 Your Environment

  • OS: Win11 x64
  • Version: 0.6.9 portable
  • PoE: �Daum Kakao, Korean
@luensys luensys added the bug Something isn't working label Aug 19, 2022
@WhiteFang5
Copy link
Member

Thank you for reporting this and providing us with the new regexes. The next poe overlay release (v0.8.20) will include the updated regexes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants