Now that last statement/question is, in all likelihood, an exaggeration but it should get you to thinking from our prospective and how we have to look at the bigger picture. Should we cater to the three that are asking for this mod to be included because they need it, while telling the remaining 700+ to skip it in the Guide? I think that's a bit unreasonable, don't you all? If not consider this, we had over 700 users who downloaded the v0.1.0b Patch on Nexus. Hopefully that explains the reasoning of not including this mod.

Install this mod = breaks things for all users who install it not running at the right resolutions.

Installing ENB or Havok Fix = does no harm to anyone who installs them.

However, this mod doesn't fit into the same niche as ENB or Havok Fix because it should only be installed by those users running the resolutions it's made for and no one else. Though it may not benefit everyone, it's still a mod that can be used by all users regardless of their screen resolution. Fixed issue that could prevent certain MCM mods from registering correctly. It can also be used by just about anyone that meets the system requirements listed on the Guide. Now Havok Fix is the same as ENB. Contribute to schlangster/skyui development by creating an account on GitHub. When I say subset, I mean really small subset: ĮNB, in contrast, is used by far more users and is why it's mentioned in the Guide. If we catered to every small situation, then the Guide would be a bloated mess. I do appreciate your arguments for this mod's inclusion, however, I think we're missing the bigger picture.on a product that is used by hundreds, we have to cater to the majority. although, I would like both mods to be included in STEP, I'm just trying to make a point. So following the logic for not including widescreen fix mod, we should also exclude havok fix. In addition, technically havok fix mod is only used by subset of users that have high refresh rate monitors.

Skyui 2.2 special edition