Page 1 of 1

[ToME 1.5.9] Lua error: attempt to call method 'sortHotkeys'

Posted: Thu Jun 07, 2018 5:24 pm
by BugReporter
Short description.
Lua error: attempt to call method 'sortHotkeys' (a nil value).
Actual result.
An error window appeared.
Expected result.
No error.
Steps to reproduce.
N/A.
Game version.
1.5.9 for windows from ToME site.
Error report contents.

Code: Select all

error = "Lua Error: /engine/interface/ActorTalents.lua:322: /engine/interface/ActorTalents.lua:295: /engine/interface/ActorTalents.lua:162: /mod/class/Party.lua:297: attempt to call method 'sortHotkeys' (a nil value)\
stack traceback:\
\9/mod/class/Party.lua:297: in function 'setPlayer'\
\9/mod/class/Party.lua:310: in function 'findSuitablePlayer'\
\9/mod/class/interface/PartyDeath.lua:45: in function 'die'\
\9/mod/class/interface/ActorLife.lua:33: in function 'takeHit'\
\9/mod/class/Actor.lua:2870: in function 'takeHit'\
\9/data/damage_types.lua:491: in function 'defaultProjector'\
\9/data/damage_types.lua:775: in function 'projector'\
\9/data/damage_types.lua:1482: in function 'projector'\
\9/engine/interface/ActorProject.lua:219: in function 'project'\
\9/data/talents/spells/air.lua:43: in function </data/talents/spells/air.lua:38>\
\9[C]: in function 'xpcall'\
\9/engine/interface/ActorTalents.lua:160: in function </engine/interface/ActorTalents.lua:149>\
  At [C]:-1 \
  At [C]:-1 error\
  At /engine/interface/ActorTalents.lua:322 useTalent\
  At /mod/ai//tactical.lua:418 runAI\
  At /mod/ai//tactical.lua:446 doAI\
  At /mod/class/NPC.lua:75 act\
  At /engine/GameEnergyBased.lua:129 tickLevel\
  At /engine/GameEnergyBased.lua:64 tick\
  At /engine/GameTurnBased.lua:51 tick\
  At /mod/class/Game.lua:1489 "
seen = true
reported = false
Comment.
The character (level 25 yeek summoner) died in Dark crypt(1), the error message appeared and control switched to yeek maindslayer. Creatures alive after death: 3 yeek mindslayers, 1 elven warrior (dominant will). The character used Psiblades and Master Summoner.
I guess that's all I have for this issue. I know it's not much, but the error window asked to report it. So there's that.