Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Also the noises your character makes :D.
Head is "Perceptioncondition"
Ah found them, theyre in the gamebryo console page, rather than the specific FO:NV page.
This game is a broken mess :?
Was wondering why things were taking so long to die.
So now I need a way to fix my character because I dont have a pre ♥♥♥♥ up save to go back to :D.
You spend more time fecking about with the console trying to fix broken ♥♥♥♥ in this game than you do playing the game :(
I just provided a way to fix that, permanently.
To go back, simply remove the negative sign from the number in the commands and your limbs will be back to normal.
Its not your fault the game is a broken peice of ♥♥♥♥, those console commands did work to cripple my guy, just the game has ♥♥♥♥♥♥ up at some point.
thank you
The game didn't. You did, due to being provided with the incorrect information.
There's the total possible value and the current value. Think of it of it being a 100 gallon tank, with 100 gallons of water in it. What you did, was change the 100 gallon tank to 0 gallon tank, instead of emptying the tank of water. The correct commands are:
player.damageav leftattackcondition -100
player.damageav rightattackcondition -100
player.damageav leftmobilitycondition -100
player.damageav rightmobilitycondition -100
There's a lot of things broken in New Vegas, but this wasn't one of them.
Damageav didnt work, neither did setav. Thats why I was surprised modav worked at the time, but I hadn't tried it so did.
With how this game is though, ♥♥♥♥ knows what was actually causing the issues :D. Same way modding av back to 100 didnt reliably uncripple me. Theres some wonk in this game.
I know this is really late but just to save anyone else from screwing their game over, possibly permanently: do not use forceav - only use modav. Forcing actor values to a specific value will make it so that nothing else will ever affect that value again. As far as I know the only way to prevent this is by making a save before forcing such values.
10/10 wonderful analogy