The game keeps track of the normal weapons, but I think the Mk2 and other special weapons from GTA:O need to be respawned. Not sure if a mod exists to keep track of those newer weapons, though.

No idea! Depends on what the website owners want to do. Might end up like GTA4-Mods.com, or just stay forever like older games on NexusMods.com.

Who knows.

@Mcarden2006
If they are images/screenshots, save them as (high-quality) JPGs. Most stay well under 1 MB, even when 2560x1440 high-quality.

If it's vector art or something, PNG should be fine, as PNGs are small for simpler images.

Wrong section, moved.
Also, English.

ScriptHookV itself shouldn't be able to crash anything. Just download the up-to-date version and extract the ScriptHookV.dll to your main game folder.

There's absolutely no need to maintain an MP-only installation if you have used the mods folder. Simply disabling/renaming/removing dinput8.dll disables all mods (since dinput8.dll loads the .asi files such as OpenIV).

If the game crashes if you enable dinput8.dll, some mod crashes the game, NOT the asi loader itself.

To identify the culprit, disable the .asi files until the game starts loading properly. What I like to do if I have no idea what crashes my game:

1. Move all .asi files to a backup folder.
2. Start the game
3. Exit the game after verifying everything works
4. Add essentials like trainers, repeat 2 & 3
5. Add .asi mods I know are non-trivial, repeat 2 & 3
6. Add the rest of the .asi mods, repeat 2 & 3
7. Add ScriptHookVDotNet.asi, repeat 2 & 3

If you replaced all files when you updated it, of course the existing configurations are wiped. You'll need to set up the wheel in the menu again.

You only need to replace Gears.asi when updating, unless the changelog tells you to also update configuration files.

You probably have something like -scOfflineOnly in your commandline.txt. (It's not a mod, just some additional arguments when starting the game.)

Disabling (renaming) dinput8.dll should disable all mods, with a few exceptions.

Exceptions:

• Graphics mods come with their own additional DLL
  • ENB: also disable d3d11.dll
  • ReShade: also disable dxgi.dll
• Some old mods use dsound.dll

Also, if you've modded game files but not with OpenIV's mods folder, you'll need to restore the original files (by getting your game launcher to reverify the files, or something).

What's being asked is unreasonable and not feasible to map out.

1. Some mods are constantly updated, some are just left there and continue to work.
2. Some mods depend on other mods. These may not need updating, but the mods they depend on, do need updating.
3. Some mods may or may not interfere with some other mods. Which these are is annoying to figure out at best, impossible at worst.
4. Some mods may only touch a small part of the game/files, some change a lot of things.

The reason the "guides" should be superficial is to build some understanding. It's almost certain any "comprehensive complete" guide will just be obsolete in a year, if not sooner.

Generally, this holds:

• Mods from different categories should not interfere, e.g. vehicle mods and graphics mods
• Conversely, mods that change a lot of gameplay-related files are quicker to break, and are incompatible with eachother.
• Add-on type mods should just work fine, e.g. map mods and vehicle mods
• Be sure to grab a gameconfig that supports more content, and the Heap Adjuster