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
What's a stacktrace?
Edit:
Relating to the Original Post:
In the case of the Bucket of Clay Cement bug where it's uncraftable, there is no STACK TRACE present after looking through all the log files of a fresh unmodded vanilla session with the bug reproduced and -debug force crafting.included.
Found answer to Karee's own question in this reply (written out what she learned and how to find them):
STACK TRACE, to find them (if there are any) one has to look in the text document files named "log_1", "log_2", "log_3", "log_4", and "log_5"
Important note: Make sure you're in vanilla, no mods, get fresh instances of logs.
There are two different folders named "console" and "debug-log", both have their own different set of numbered log files listed above in quotes which contain different information.
Location of both the "console" and "debug-log" folders is:
This PC > Local Disk (C:) > Users > [your username] > Zomboid > logs
Doing one file at a time, open and search through each log using the CTRL+F "find" search, type in the "find what" entry field "STACK TRACE" in all caps (you only need to enter it once and it should stick around for searching through the rest of the files), make sure the search direction is set to "down", then click "find next."
If there's a pop-up saying: "Cannot find "STACK TRACE" ", that means there's no STACK TRACE present in the file, move to the next file and repeat the find search until you've looked through all 5 log files in both folders.
Finding no STACK TRACE in any of the logs means that it's a bug with no associated STACK TRACE to copy paste into a bug report.
If the a pop up doesn't appear after clicking "find" and you jump down through the document to a STACK TRACE (which is probably highlighted in blue or some kind of color) then you found a STACK TRACE.
If you find a STACK TRACE, include it in a bug report by copy and pasting the information starting at "STACK TRACE" and ending where the grouped up information of the STACK TRACE seems to end.
Important notes: Make sure the STACK TRACES are from fresh instances of vanilla (unmodded) game sessions with file times/dates you know for a fact are from game sessions where your mods were turned off.
If the STACK TRACE looks like it might be from a mod, don't use it in a bug report, make sure your mods are turned off in both Main Menu AND your save file, and try to create a new fresh vanilla instance of the log files with a date/time matching your most recent vanilla session/game exit.
Make sure before exiting a vanilla game session to reproduce the bug so that you will find a STACK TRACE in your find searches IF there is one associated with the bug.