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
This is for a Server btw, I verify game files often.
unwillingness to remove mods for testing of which one is the problem removes the possibility of solving your problem.
game developers routinely change the way things work in their vanilla game. some core features change in a way that mods no longer work as they did. that is up to the mod dev to fix.
I appreciate and understand your comment though I wish these crash reports would show which mods are causing issues. I was hoping to learn if there was a way to understand the gibberish :)
The other problem is these errors happen randomly but can potentially take days to replicate which will be a severe waste of time testing mods one at a time. long story short was hoping to convert this crash log into basic english.
in your case this entry "execInstance Variable" is typical of a crash caused by mods. could be a stack mod or something like S+ or SS
i am no expert at deciphering these crash logs but a quick search of "execInstance Variable" on the ark forum will give results to a heap of crashes containing this "execInstance Variable" and 99% of them are mod related.