206
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 May 2024
206 points (98.1% liked)
Games
16845 readers
896 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
The first time I installed Vanguard, for the Valorant beta, it decided to disable my mouse and keyboard on each boot.
Well, you can't cheat if you can't do anything
This is why I absolutely refuse to install Valorant (and now LoL) - I could somewhat understand if an anticheat refused to boot up the game in question if something triggered it, but it going massively outside of its scope and wantonly disabling or killing other processes is just nuts to me.
To be fair, if they were typical RBG mouse and keyboard, and you used the brands software to change their settings, it blocked that software. Those programs were absolute dog shit in terms of security. I have no idea if it forced them to make better software, or Riot just started to allow them. Regardless it's all pointless because Vanguard has been defeated. Imagine making ring 0 anticheat that loads on boot, and it still isn't good enough, fucking LoL pun intended.
Both had optional software, and I only used the keyboard. The software didn't have to be running for either to work, it was only to configure it and then it wrote the configuration to onboard memory. It was the generic mouse and keyboard input drivers provided by Windows that was blocked and it affected a pretty significant number of users.