The interface lag. on. every. single. button. press. Why do we have to wait 1.5 seconds every time we tap any menu item? There's no good reason.

Because most of these invoke API calls to the servers. The servers verify your data before okaying the next view. Sometimes these contain large payloads too.

This would take at most a few minutes to implement.

Again, this would take minutes to implement...

...that would take virtually zero effort to add...

So that means you've fixed these right? Because that's how you'd know how simple the fixes are.

I'm always cautious of people claiming how much work it would take who haven't done it. I know that my programs get these comments, "just add blank, it should only take 5 minutes." No, it requires a lot of re-factoring because the code flow doesn't support what they're asking for. Does that mean that we shouldn't want these improvements? No, we should ask for them. But it's not always as simple as it looks until you've read the code (which maybe you've done, I don't know). But be cautious of making statements like these.

All of that said, I would like to see the improvements that you suggest and I am not against the spirit of your post.

You're right, and when I said I could do it in minutes I was exaggerating and appealing to emotion. I'm well aware that most any hack will take some time and creative problem solving.

As for the API calls to the servers, I suspect they're updating data server side every time you, say, equip a piece of armour. Instead they could have all of the operations like equipping, un equipping, swapping a party member out, assigning an ability etc. could all be done lagless client side before things are finalized (a confirm changes prompt for example).

I have a proof of concept for my loot screen mod already working. Right now I'm experimenting and researching how the app communicates with the server in hopes of cutting back the interface lag.

I appreciate your input though, so thank you!