Newline character (regex \n) in search interface not working properly
It seems that the newline char for regex searches isn't working properly. I stumbled upon this while trying to search for multi-resistance items with "resistance\n{2,}".
Something similar has been reported in another closed thread about a year ago. Trying a couple of things i noticed, that "resista\Nce" highlights all resistance items, which seems weird to me. Also other tokens like /w /W /d etc produce strange behavior, higlighting some items that should or should not match. But thats only to the copied text from items (ctrl alt c), I asumed the engine uses it. While im at it could sb enlighten me how quotation marks "/' and parenthesis are implemented. I guess with "normal" searches there is some special behavior? __________________________________________________________________________________ In case anybody is interested in a somewhat clumsy solution for multires searches: Since the Suffix order is always fire > cold > lightning > chaos as far as i know, one can use sth like "fire res"(?="cold res"(?="ing res")) to search for specific combinations or sth like "([2-4][0-9])% to f"(?="([2-4][0-9])% to co") for 2 res and their values (substitute required res in the right order eg "co" for "f" and "ca" for "co", to search for cold and chaos resistances) Last bumped on Jun 3, 2022, 11:29:19 PM
This thread has been automatically archived. Replies are disabled.
|
![]() |