Alcs not saving properly.

Nerdy_2417-Ninja​ Can you upload a video or provide screenshots of what's resetting?

As you can see from One picture anytime I reload into the game. Defaults are white but then if you look at the other picture and where my cursor is anytime you hover over the cursor it fades back out. However, when you load into the game and you go play a game mode it won't actually be running whatever ALC. It doesn't matter if you have the alcs turned on or off. I have advanced look controls turned on what I'm assuming is happening is that instead of actually running advanced look controls? It's running bleed throughs so it's running defaults just like it would run defaults if you had ALC's turned off and you would have inputs like in ALCs but you turned alcs off and it would bleed through essentially what I think is happening it's instead of running custom look controls, it is running bleed-throughs. So basically every time I load into the game I have to reset everything and then reinput every value that I had in there before in order to start running ALCs again and what I have also noticed it is doing this mid-match. At one point of the match I'll be running. Advanced look controls the other minute I'm running bleed throughs. It's doing the same thing with per optics. In the default section.

These are the values that I'm trying to run but instead of running these advanced look controls, it is running a variation or a bleed through of 3/same classic with small dead zone. Even though I'm not using defaults and I don't have alcs turned off, I have alcs turned on and I am not trying to use bleedthroughs. And the only reason that I know it's not running my sensitivity is because I use the same sensitivity that I use in Apex that I use in aim Labs and they're completely different. In the middle of a match it doesn't like white out like it does when I first load into the game and then when I hover over it it fades back out. It doesn't do that, but one minute in a match I'll be running alc's the next minute I'll be running some kind of variation of three same classic with small dead sound when I'm running a custom response curve, a custom outer threshold zero dead zone or sometimes I run 2% or 3% dead zone with those values that I have for the extra yaw and the extra pitch and the pitch and the yaw and the extra ads pitch and an extra ads yaw and ads pitch and the ads yaw and the per optics that I have in alcs. And it's been extremely frustrating while I'm playing this game for me to go from using advanced lift controls to some kind of bleed-throughs of 33 classic when that's not what I want. Because that also makes micro adjustments incredibly inconsistent to go from using one thing to using something completely different that I'm not familiar with. I don't want to use defaults. I should be able to use custom sensitivity and create my own sensitivity to my preferred playstyle without having defaults interfere with that. And then it's the same thing. Let's say I switch everything to four three linear and then turn advanced. Look controls on and use the same values that I have in advanced look controls and then I leave advanced look controls. Turned on defaults affect alcs. They should not do that. If I want to run pure custom sensitivity, I should be able to run pure custom sensitivity without defaults interfering. And that has been a huge problem ever since bleed throughs ever accidentally became a thing. I have some experience in coding. Whenever there's a bug or a problem with the game, it's usually because code that was pushed broke the original code of the game that has happened multiple times throughout the entire time that this game has been a thing. I have never seen a developer team ever intentionally leave bugs in their game to the point where almost every single time they issue a patch or an update to the game. Something breaks. But at the same time I'm not going to act like I understand the process of what you do or how y'all are working on the on the game it it varies from place to place and from people to people and from company to company as well as from code to code. No matter what the player base thinks or how much they want a bug to stay in the game, you shouldn't leave bugs in the game. Because it affects how the game runs later on, especially when you're constantly pushing code. I'm sure a lot of players would love for duplication glitches to be left into Minecraft, but they don't do that. It's up to the developers to decide what stays in their game and what doesn't. Y'all did the same thing with punch boosting. Every a lot of people wanted punch boosting to stay in there. It was a bug. It was patched. Bleed through should have never been a thing. 

This has also been a thing since the last time where it was like completely resetting all of your settings where every time you would load it into the game. Basically all of your saved data would be gone. And you basically had to re-input every sighting that you had before and gameplay and in sensitivity. 

I made a lot of grammar mistakes there, but as far as everything goes I hope you basically get the gist of it.