ToME: the Tales of Maj'Eyal

Everything about ToME
It is currently Fri Oct 18, 2019 4:21 am

All times are UTC

Post new topic Reply to topic  [ 3 posts ] 
Author Message
 Post subject: Bug Reports for Dummies
PostPosted: Sat Dec 27, 2014 2:19 am 
Perspiring Physicist

Joined: Sun Sep 09, 2012 7:43 am
Posts: 5940
This is a quick guide for you to get the most out of your bug posts.

The more useful the information you provide, the more quickly you will get help.

So what is useful?

If the game doesn't run at all, or the graphics are messed up, say what your OS is and try disabling the shader options.
This game uses OpenGL shaders which are not always properly supported by your drivers.

If the crash happened in game, the MOST important thing you can post here is the error message.
Even if you submitted it via the in game error popup, still post it, as only DarkGod can see those.
Even if you don't think there was an error message, there likely was: 99% of all freezes are a lua error, it will be in the log file.

NB: Every time you run the game, the log file is erased and a new one is started. So if you tried changing areas and the loading bar never stopped. Do not run the game again until you have copied the log file, or the error will be lost forever.

Finding the log file:
For Windows users, it will be called te4_log.txt and it will be in the same folder as the t-engine.exe.
For Mac users, I think it is called te4_log.txt and it will be in the same folder as the t-engine program.
For Linux users, the log is not automatically generated. You will need to run the game with something like > /home/te4_log.txt added to it. You can also add this to the launch options via Steam if you are using it.

What to copy from the log file:
You are looking for something like this:
Lua Error: /engine/interface/ActorTalents.lua:175: /engine/interface/ActorTalents.lua:153: .../addons/verdant/superload/mod/class/interface/Combat.lua:89: attempt to perform arithmetic on local 'add_chance' (a nil value)
stack traceback:
   .../addons/verdant/superload/mod/class/interface/Combat.lua:89: in function 'physicalCrit'
   /mod/class/interface/Combat.lua:465: in function 'attackTargetWith'
   ...wandir-weaponry/superload/mod/class/interface/Combat.lua:312: in function 'attackTargetWith'
   /mod/class/interface/Combat.lua:168: in function 'attackTarget'
   ...wandir-weaponry/superload/mod/class/interface/Combat.lua:203: in function 'attackTarget'
   /data-verdant/talents/gifts/sharkaspect.lua:41: in function </data-verdant/talents/gifts/sharkaspect.lua:32>
   [C]: in function 'xpcall'
   /engine/interface/ActorTalents.lua:148: in function </engine/interface/ActorTalents.lua:135>
   At [C]:-1
   At [C]:-1 error
   At /engine/interface/ActorTalents.lua:175 useTalent
   At /engine/interface/PlayerHotkeys.lua:169
   At /engine/interface/PlayerHotkeys.lua:161 activateHotkey
   At /mod/class/Game.lua:1967 f
   At /mod/class/Game.lua:1562 fct
   At /engine/interface/PlayerHotkeys.lua:316
   At /engine/KeyBind.lua:229

Both the Error and the stack traceback are needed.

In some situation it can be useful to have a page of lines before the error message so that it can be determined what talent/weapon was being used to cause the error.

If the error message is repeated a hundred times, it usually means the error happened in the UI code. You only need to post one copy of the error.

Sometimes the log file is cut off before the error occurs. In which case, you should enable flush logging (there is an option in the launcher for windows, or there is a command line option (--flush-stdout)). Then if possible, you do whatever you did before and the log will print correctly. Remember to turn off flush logging afterwards, as it makes the game run slowly.

My feedback meter decays into coding. Give me feedback and I make mods.

Last edited by HousePet on Fri Oct 05, 2018 10:11 pm, edited 2 times in total.

PostPosted: Sat Jan 03, 2015 11:02 pm 
Low Yeek

Joined: Sat Jan 03, 2015 10:56 pm
Posts: 7
Hello, this is from my cursed nightmare character. I get a lua error when I win, where it tries to suicide you.

Lua Error: /mod/addons/ashes-urhrok/superload/mod/class/Player.lua:24: attempt to call upvalue 'die' (a nil value)
At [C]:-1 die
At /mod/addons/ashes-urhrok/superload/mod/class/Player.lua:24 die
At /data/chats/sorcerer-end.lua:84 action
At /engine/dialogs/Chat.lua:93 use
At /engine/dialogs/Chat.lua:46 fct
At /engine/ui/VariableList.lua:123 onUse
At /engine/ui/VariableList.lua:106
At /engine/KeyBind.lua:229 receiveKey
At /engine/ui/Dialog.lua:566 keyEvent
At /engine/ui/Dialog.lua:339

PostPosted: Tue Oct 15, 2019 3:33 pm 

Joined: Wed Sep 28, 2016 8:07 pm
Posts: 56
Don't know if this applies to all mac users, but for me, the log file is at Macintosh HD/private/tmp/te4_log.txt. It isn't searchable, so to find it, navigate to macintosh hd, show hidden files by pressing command+shift+. and you should see a folder labeled private

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC

Who is online

Users browsing this forum: No registered users and 5 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group