devtrackers.gg
I was searching random stuff in the shop and found this out. I understand why "spooky ghosts" causes Twin Shadows to appear. Why pee pee poo poo though?
External link →I was searching random stuff in the shop and found this out. I understand why "spooky ghosts" causes Twin Shadows to appear. Why pee pee poo poo though?
External link →pee matches "speed" in the item stats and poo matches "spooky" in the item active description, I would imagine
I sure hope this is the real reason lol
Don't pretend like you don't know the true origins of this buddy!
How did you know that I have Sasquatch arms???
pee matches "speed" in the item stats and poo matches "spooky" in the item active description, I would imagine
This is accurate!
The item shop’s behavior can be recreated with a bit of data. Notably: http://ddragon.leagueoflegends.com/cdn/9.24.1/data/en_US/item.json and http://ddragon.leagueoflegends.com/cdn/9.24.1/data/en_US/language.json (or as appropriate by patch and language).
This is a reflection of some of the data the game uses. We’d just need to combine it a bit.
The League item shop makes a “searchable key” out of: An items name (“name”), colloquialisms for that item (“colloq”, which you’ll notice is often “;”, this is important), adds a “;”, and then goes through each tag (“tags”) of the item and matches the localized name for that tag (found in the language json above), as well as the colloquialisms for that tag (e.g. for Armor, there’s also “armour” as a colloquialism, or for Attack Damage, there’s “ad” as a colloquialism). There’s also a step to add the “hat” tag to boots if you’re Nami. This is very important.
Then it does some transformation to that key. Such as removing diacritics, lower casing and/or finding a common character base (e.g. “ß” becomes “ss” or both dotted and dotless “i” of all cases become just “i”), and removing Korean partial characters.
Once you have a search key for each item, you can then complete a search against the item by:
Splitting up the input by a few various markers (spaces, commas, periods, full stops, arabic reverse commas, semi-colons, and so forth). Then with each individual split up string, do the same transformation we did to generate the searchable key (exception: If you’re in a Chinese localization, and it finds you’ve completed at least 1 Chinese character, it will also strip out pinyin from your search), it then simply matches “does the searchable key contain the contained string part”. If this is true for all the search parts... then the item will be matched.
Hopefully with all this info you all can find more amusing searches that technically complete.
