@accelerator74 can you resolve the merge conflicts.
@psychonic do you know the latest on this stuff? I know it's been a minute since we looked at this stuff but you're way more present with the maxmind stuff than I am.

Thank you! The fallback to the server language looks good.

I'll wait for a comment from other maintainers about the const char[] lang vs. int client parameter question to determine which language to use as proposed in my previous comment. Deliberately choosing a different language than the player's selected one to display a message to them sounds like a very "niche" use case. And you could still use SetClientLanguage briefly to force it to something else..

Nevertheless, I made the definition of the language by the client index :) I see colleagues from the amxmodx team did the same :)

P.S.: By the way, yes, most of the code was borrowed from them, but it seems that everything is one team :)

@peace-maker do you need anything from me to help move this one forward?

@KyleSanderson No, this looks good. I didn't notice the changes after my last comment, so this is fine now from my side. If you don't have any strong feelings towards selecting the country language by string, 🚢
There are a couple of nits left like using .c_str() and then calculating the length again using strlen() while we could just use the length of the std::string and indentation issues in the include doc comments.

But above all this requires changes to the packaging scripts, since we can't ship the old GeoIp.dat with this anymore. We can't include the latest database either due to licensing requirements as you know. We can merge this and do a follow up to fix the packaging and documentation afterwards though, since that's not something Accelerator74 can do.