Ugh, ARR is horrible for that. It really is a good game after all that bullshit, but it doesn't excuse the bullshit existing in the first place. Plus it's so weird for Final Fantasy, a story driven RPG, to have so many low quality quests in the first place (both story and side quests). I can't fault anyone not wanting to deal with that.
Best thing it has going for it is that the dungeons are really fun even when the story quests suck. But it's been years since I've played and my knowledge may be stale. Someday I'll go back, but no way I'll start with a new character lol.
Let's not pretend people acknowledge warnings, though. It's a popular meme that projects will have hundreds of warnings and that devs will ignore them all.
There's a perfectly valid use case for opinionated languages that don't let you get away with that. It's also similar to how go has gofmt to enforce a consistent formatting.
Honestly, I've been using Go for years and this unused variable error rarely comes up. When it does, it's trivial to resolve. But the error has saved me from bugs more often than it has wasted my time. Most commonly when you declare a new variable in a narrower scope when you intended to assign to the variable of the same name (since Go has separate declare vs assign operators).