[Linux] Add anticheat information when possible

[arielj]

This PR adds anticheat information when possible using the information from AreWeAntiCheatYet.com.

It downloads the games.json from https://github.com/Starz0r/AreWeAntiCheatYet/blob/master/games.json at boot in the background only on Linux, to keep the information up to date (it's less than 100kb).

I left this message It may not work due to denied or broken anticheat support on purpose without interpolation of the actual status to help translations (also, I don't know how to handle translations based on a variable).

I went over all the games in the json and looked for them in the epic store to create the map of names for games that have differences but I might have missed something, we can always add more or update when needed.

Denied:

Supported:

Broken:

Denied in install modal:

---

Use the following Checklist if you have changed something on the Backend or Frontend:

• Tested the feature and it's working on a current and clean install.
• Tested the main App features and they are still working on a current and clean install. (Login, Install, Play, Uninstall, Move games, etc.)
• Created / Updated Tests (If necessary)
• Created / Updated documentation (If necessary)

[flavioislima]

Looks pretty good!
Left just some small comments :)

[Nocccer]

Besides what Flavio found, looks good to me. We can actually implement tests for the backend functions. But maybe in another pr.

Just an idea: Maybe a new logprefix Anticheat ?

[JakobDev]

It might be good to include informations like the reference link notes and updates from the JSON file if present.

[arielj]

It might be good to include informations like the reference link notes and updates from the JSON file if present.

I tried, but the information varies between games and it was really difficult to consider all the cases in a consistent design (you have games with multiple updates with different references, the main reference may not even match the last update reference so I can't use the main reference always without the updates) and without making it overwhelming. It felt like too much information, the average user might not care about all the details.

I did add the link to open areweanticheatyet to see those details for the people that do want to know.

[flavioislima]

Looks good.
I am curious to collect info on that from the next beta because some things might match and some others might not. But if we are not impending the user from installing the game then its fine.

[Curve]

It might be good to include informations like the reference link notes and updates from the JSON file if present.

I tried, but the information varies between games and it was really difficult to consider all the cases in a consistent design (you have games with multiple updates with different references, the main reference may not even match the last update reference so I can't use the main reference always without the updates) and without making it overwhelming. It felt like too much information, the average user might not care about all the details.

I did add the link to open areweanticheatyet to see those details for the people that do want to know.

Currently, the Reference is mostly used for games where there is official word from the developers or there have not been more than 1 changes to the status in the past (Mostly the reference is also the most straight to the point).

Updates is what's used for the most recent additions and contains more precise information than the reference link, if I were to show any information in Heroic I'd go for the latest update.

However the reference links are sometimes not really in sync with the updates at all, I will try to improve that and keep things more consistent

[Curve]

It might be good to include informations like the reference link notes and updates from the JSON file if present.

I tried, but the information varies between games and it was really difficult to consider all the cases in a consistent design (you have games with multiple updates with different references, the main reference may not even match the last update reference so I can't use the main reference always without the updates) and without making it overwhelming. It felt like too much information, the average user might not care about all the details.
I did add the link to open areweanticheatyet to see those details for the people that do want to know.

Currently, the Reference is mostly used for games where there is no official word from the developers or there have not been more than 1 changes to the status in the past (Mostly the reference is also the most straight to the point).

Updates is what's used for the most recent additions and contains more precise information than the reference link, if I were to show any information in Heroic I'd go for the latest update.

However the reference links are sometimes not really in sync with the updates at all, I will try to improve that and keep things more consistent

Alright, I've update the list.
If you still want to display relevant information on the Anti-Cheat Status you should:

• use reference if set, it should be preferred over the updates
• in case reference is not set use the last recorded update

[arielj]

I updated this to use the namespace and to show a link to the latest reference for a given status:

@felipecrs can you test this again with these changes?

Thanks you both @felipecrs and @Curve for the initiative and the quick addition of this info!

[arielj]

Just an idea: Maybe a new logprefix Anticheat ?

I was going to add this but then I saw I only use this in one place and the string always says AreWeAntiCheatYet on it. I'll skip this, seems too much to add that new logprefix for this single use.

[felipecrs]

I updated this to use the namespace and to show a link to the latest reference for a given status:

@felipecrs can you test this again with these changes?

Thanks you both @felipecrs and @Curve for the initiative and the quick addition of this info!

Hey, great to see this. Unfortunately, I don't have an environment to test it, I trust you.

By the way, I think if you display:

Source: AreWeAntiCheatYet

I think it would look a little better.

[arielj]

I updated this to use the namespace and to show a link to the latest reference for a given status:

@felipecrs can you test this again with these changes?
Thanks you both @felipecrs and @Curve for the initiative and the quick addition of this info!

Hey, great to see this. Unfortunately, I don't have an environment to test it, I trust you.

By the way, I think if you display:

Source: AreWeAntiCheatYet

I think it would look a little better.

Thanks, I'll change that, I think it will also make translations easier

[Curve]

I updated this to use the namespace and to show a link to the latest reference for a given status:

@felipecrs can you test this again with these changes?

Thanks you both @felipecrs and @Curve for the initiative and the quick addition of this info!

No problem, always an honor ^^