Dynamic Loot Filter, Reloading Local Filter File Automatable?

Question

I've been considering writing a script that will allow for "dynamic" loot filters, i.e. modifying the filter file on the fly, while in game. For example, you might be looking for a R-R-B linked wand for your build while leveling, so you want to highlight wands with those links. However, after you find such a wand, you may never need to find a similar item again, so you'd then like to turn the highlighting off. Another example would be if you're low on Wisdom Scrolls, you may want to unhide them temporarily until you pick up enough.

The above is fairly simple to do—just programmatically modify a local .filter file as needed and reload it in the game client. However, my concern is whether fully automating the filter reload breaks ToU, as it may be a server action. Since settings are mostly clientside (aside from changing lockstep/predictive or loading a remote filter), I'd expect that reloading a local filter would not be an issue. That said, I wanted to check here first, just in case someone knows whether such automation is permissible.

Posted Jul 30, 2021, 11:26 AM UTC

85
akithebrony•

i sadly cant answer your question regarding if its "legal" but id guess it is, assuming it actually is i would LOVE that, thanks for the idea!

2
rogueyoshi•

i believe it's legal to automate a settings change (filter reload). also, i was considering making the same kind of thing, but monitoring the chat log for my commands.

1
ofb•

how would you force a filter reload automatically? Did they add a chat command to do it?

1
TonexusOP•

I was going to do it the old-fashioned way: have a script open the options menu, click the UI tab, and refresh the filter. It's a bit intrusive, but I assume that it wouldn't be a frequent action.

1
ofb•

thank you for sharing. You're right that is a bit intrusive. I had asked support for a chat command a long time ago but it never materialized, maybe if more devs asked for one we could get one! (we can dream)

for some reason I always assumed automating menu changes would be against TOS, but given it likely only results in a single server action (if any) taking place, perhaps this is acceptable!

1