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
I will however, use them on rare cases where a dead body in in the way of an item.
If you delete the wrong item by accident, there is no way to reacquire the item, it is gone forever.
There are also many items tied to quests that if deleted will break the game.
MarkForDelete Should NEVER be used.
But it is your game and the consequences for using bad commands are yours to discover.
I discourage use of disable otherwise, because the item it disables is still being loaded, it's just not accessible.
MarkforDelete is only for when something isn't being cleaned up when it should, I have never used it, and given that the only thing that doesn't disappear is those piles of ash, I doubt I ever will.
Regards