SaruNi Posted February 13, 2018 Posted February 13, 2018 (edited) Apparently because it's stored as "Hammering Thoughts" rather than "Hammering_Thoughts" or "HammeringThoughts". The console command can only take one parameter so the space messes it up. Edited February 13, 2018 by SaruNi 1
0 AndreaColombo Posted February 13, 2018 Posted February 13, 2018 Have you tried using just “Hammering”? It’s a shot in the dark but it worked for me with a companion name that had two words; using the first one made the console pick him up. "Time is not your enemy. Forever is." — Fall-From-Grace, Planescape: Torment "It's the questions we can't answer that teach us the most. They teach us how to think. If you give a man an answer, all he gains is a little fact. But give him a question, and he'll look for his own answers." — Kvothe, The Wise Man's Fears My Deadfire mods: Brilliant Mod | Faster Deadfire | Deadfire Unnerfed | Helwalker Rekke | Permanent Per-Rest Bonuses | PoE Items for Deadfire | No Recyled Icons | Soul Charged Nautilus
0 Boeroer Posted February 13, 2018 Posted February 13, 2018 (edited) No, that doesn't work, but you can put in in quatation marks like so: addabiliy <whoever> "hammering thoughts" This can be done with everything that has a space in between, also player names. Anyway: if you don't know what the correct command is you can always start with the first letters like "ham" (without quot. marks) and then hit [tab] - the console will try to complete your command. In this case I just type (withoput quat. marks): "addab"->[tab]->"play"->tab->"ham"->[tab]->[enter]. This will be completed to AddAbilty Player_<whoever> "Hammering Thoughts". Edited February 13, 2018 by Boeroer 1 Deadfire Community Patch: Nexus Mods
Question
SaruNi
Apparently because it's stored as "Hammering Thoughts" rather than "Hammering_Thoughts" or "HammeringThoughts". The console command can only take one parameter so the space messes it up.
Edited by SaruNi3 answers to this question
Recommended Posts