Page 1 of 1
Character index crash
Posted: Thu Dec 16, 2010 10:56 am
by Joramun
Hi,
When indexes are skipped for champions, DSB crashes.
(example: add a test character to DM or CSB with index 100 instead of index 25 -- since 24 is the last used one)
It took me some time to understand what was causing it because ESB works almost fine.
(in the party/character toolbox it shows "unused" character slots between 24 and 100 with the above example).
Also: For some reason, it is impossible to put champions with index greater than 6 to mirrors.
Re: Character index crash
Posted: Thu Dec 16, 2010 8:21 pm
by Sophia
Joramun wrote:When indexes are skipped for champions, DSB crashes.
(example: add a test character to DM or CSB with index 100 instead of index 25 -- since 24 is the last used one)
I can't reproduce this. Can you paste the stack dump?
Joramun wrote:It took me some time to understand what was causing it because ESB works almost fine.
(in the party/character toolbox it shows "unused" character slots between 24 and 100 with the above example).
I really can't do anything better, because trying to automatically consolidate the id numbers will mess things up if you have exvars that refer to a champion by id (such as in a mirror) and I don't want to risk messing anything up by trying to automatically change those.
Joramun wrote:For some reason, it is impossible to put champions with index greater than 6 to mirrors.
Oh, it's not drawing a scroll bar. I'll fix this. For the time being, though, it's not impossible, just annoying-- you can still scroll through the list with the arrow keys.
Re: Character index crash
Posted: Thu Dec 16, 2010 9:07 pm
by Joramun
It crashes only when said character is added to the starting party !
Ok for the mirror. I don't use the keyboard much.
Re: Character index crash
Posted: Sat Dec 18, 2010 1:35 am
by Sophia
Joramun wrote:It crashes only when said character is added to the starting party !
I still couldn't make it crash.

Are you sure there isn't some other problem with your dungeon, specifically?
Without a crash log I can't investigate the problem at all, unfortunately.