WARNING: Only use console commands as a last resort

[talm bout dang ol bugs man]

Or at least be cautious, since people clearly don't have bad experiences with it. For me, my first console command ruined a 60 hour game.

I had 130 mods running very well for around 30 hours (first 30 hours were spent setting up the mods). I slept in a bed and noticed my carry capacity was buffed by 1000 space when I woke up.

Since my last save was 30 or so mins prior to this, I save a separate file and decide to run console command player.modav carry weight -1000 since that was the advice I found. I leave the interior and notice my companions are bugged running on spot; and when I talk to them - crash.

I reload the save that was before the change, exit interior again, notice companions bugged and try to reload. When I press ESC, it crashed.

I purged all the mods and started a new game. Crash. Tried 4 more times, consistent crashes before the Vigotester.

So now I'm in the long process of moving all my mods from Vortex to MO2 while following extensive modding guides so I can clean reinstall everything and really gauge what's going on.

It could've been Vortex not loading in the essential mods and it's a vanilla crash
Or the console command changing/corrupting a main file ini
I don't know dude, still trying to figure it out

[Ladez]

I find it unlikely that this specific command caused you any major issues. More likely, your game was already about to go tits up, and you were just seeing it begin to manifest.

In any case, I stand behind the advice to be careful with console commands, because the console is a debugging tool and not a plaything. Ideally you should never touch it whatsoever.

[talm bout dang ol bugs man]

Originally posted by Ladez:

I find it unlikely that this specific command caused you any major issues. More likely, your game was already about to go tits up, and you were just seeing it begin to manifest.

In any case, I stand behind the advice to be careful with console commands, because the console is a debugging tool and not a plaything. Ideally you should never touch it whatsoever.

I doubt that because it persisted on a purged modlist on a completely new save file and applying the needed mod removers for Open Freeside. Like yeah heavy modded games can't last forever, but it was no where near its time and modders can usually feel when it's time.

Only way to fix it was reinstalling the game/clearing cache/reinstalling mods and only time will tell if it was the modlist or not. It was running better than vanilla for the entire playthrough until that moment. No crashes outside of Freeside and some scripted events, but that's normal even without mods.

[talm bout dang ol bugs man]

Lmao the only person I saw warn about console commands breaking games got downvoted to hell on Reddit and I already get a clown.

Why is the Bethesda community so angry when being warned about console commands?

[Ladez]

Originally posted by double barrel daryl:

Why is the Bethesda community so angry when being warned about console commands?

Cargo cultism. They need muh cunsul to fix their broken game, oblivious to the fact that they're breaking it even more.

[talm bout dang ol bugs man]

Originally posted by Ladez:

Originally posted by double barrel daryl:

Why is the Bethesda community so angry when being warned about console commands?

Cargo cultism. They need muh cunsul to fix their broken game, oblivious to the fact that they're breaking it even more.

Hey! Super random but I ended figuring it out lmfao

1000+ weight bug was caused by mod DT Multiplier and DR Adder when changing an armor types' weight values while wearing that armor type. When I recreated the bug, I was carrying 180 weight and put my carrying cap to 125 from 1125, yet it was acting as if I was not encumbered so I know that number isn't real.

Fixing it with the console put a negative value somewhere in the main files for sure since it persisted with all mods off with proper uninstalls on a new save. I didn't try to find the error, but the crash felt like it was trying to calculate an infinite/impossible value.

I clean reinstalled, added 20 more mods to push it to 150, and 20 hours of gameplay later I have yet to experience a crash. Not even in scripted quests, modded quests, or Freeside.

[Vomit Heart]

If you are not thick as ♥♥♥♥ there is no problem using commands SAVE b4 you try something if quest is bugged try movetoqt

[Sana-kan]

Blown out of proportion, since the game can't go this level of tits up by merely using a command. However, there is some merit as some commands should never be touched, as those directly affect the game's files.

[talm bout dang ol bugs man]

Originally posted by Vomit Heart:

If you are not thick as ♥♥♥♥ there is no problem using commands SAVE b4 you try something if quest is bugged try movetoqt

Read.

[talm bout dang ol bugs man]

Originally posted by Vera: Garnet:

Blown out of proportion, since the game can't go this level of tits up by merely using a command. However, there is some merit as some commands should never be touched, as those directly affect the game's files.

It was because of a console command.

[psychotron666]

Bro your game was broken beyond all repair to begin with if your carry capacity was going up to 1000. The console command was a bandaid repair to disemboweled intestines. It's not fixing the underlying problem and just adding fuel to the already burning dumpster fire

[Cadillac]

If you touch the console, but reload a saved file where you had not used the console...the problem should not exist, right?

[talm bout dang ol bugs man]

Originally posted by Cadillac:

If you touch the console, but reload a saved file where you had not used the console...the problem should not exist, right?

Unless it messes with your main files, no.

Originally posted by psychotron666:

Bro your game was broken beyond all repair to begin with if your carry capacity was going up to 1000. The console command was a bandaid repair to disemboweled intestines. It's not fixing the underlying problem and just adding fuel to the already burning dumpster fire

I figured it out, and it was the console command. The 1000 bug was caused by mod DT Multiplier and DR Adder, yes, but the crashes were caused by the command rendering that value incalculable in the main files. That's why it persisted even with a purged modlist and new save file.

25+ hours in a brand new game with the same mods + 30 (so 150 in total) and have experienced 0 crashes. Not even in scripted quests, modded quests, or Freeside.

It was not the modlist. Don't use console commands.

[Vex Hilarius]

I've been using console commands for almost a decade with this game, modav included. Mods cause crashes, not the console. Stop spreading crap you know nothing about.

If you install a mod that causes issues, its the mods fault, not the console. You probably did not uninstall your mods correctly (most likely since you're using vortex) and some left over stuff stayed. In order to do a complete wipe, you have to delete your entire data folder.

[Ladez]

Originally posted by double barrel daryl:

I figured it out, and it was the console command. The 1000 bug was caused by mod DT Multiplier and DR Adder, yes, but the crashes were caused by the command rendering that value incalculable in the main files. That's why it persisted even with a purged modlist and new save file.

I guess it's plausible that the command caused a state that lead to a crash, but there's no way this had an effect that carried over into a new save file, or even the same one unless you saved it while in that state.

Originally posted by double barrel daryl:

25+ hours in a brand new game with the same mods + 30 (so 150 in total) and have experienced 0 crashes. Not even in scripted quests, modded quests, or Freeside.

Well, that's good, but no crashes does not mean that everything is fine.

Originally posted by double barrel daryl:

It was not the modlist. Don't use console commands.

Well, this is a bit silly. If you're saying that console commands just somehow break your game as a rule because they mess with your "main files" whatever that is, you're terribly misinformed.

[talm bout dang ol bugs man]

Originally posted by Vex Hilarius:

I've been using console commands for almost a decade with this game, modav included. Mods cause crashes, not the console. Stop spreading crap you know nothing about.

If you install a mod that causes issues, its the mods fault, not the console. You probably did not uninstall your mods correctly (most likely since you're using vortex) and some left over stuff stayed. In order to do a complete wipe, you have to delete your entire data folder.

I did, with the same exact modlist + 30 mods (so 150 now), and 25+ hours so far no crash even in scripted quests, modded quests, or Freeside. It was not the modlist that caused the crash, it was the modlist that required the fix from the console, and it was the console that crashed it. I guess you didn't read that it persisted even with a brand new game with no mods and needed a clean game reinstall for it to work again.

I was able to recreate the +1000 bug after installing the mods on MO2. If you're interested to recreate it, get DT Multiplier and DR Adder, wear any armor type, and then change the weight of that armor type. The mod makes a logical error (+1000) but it still runs the game, while the console command turned that value into something incalculable immediately causing the crashes.

Why are you so mad lmfao how are you gonna tell me what happened to my game when I already properly debugged, recreated, and fixed the problem.