Request for Same Size Chat Window
Moon_Wizard, I was talking to some of my players last weekend in one of my 4E games on syncing up the shown die rolls on the server and clients. I had several players suggest there be an option that all client chat window sizes be locked to the same size as the host's chat window on the understanding that this would usually mean everyone would see the same roll. The players in that game cared more about everyone seeing the same rolls show up on the dice than having a individually re-sizable chat windows.
After your improvements to the chat window, does having everyone with the same size chat window make it more likely everyone in the group will see the same number on a throw die? And if so would it be possible add an option to slave chat window size on the clients to the master in 2.9? I was thinking the Host would resize the chat window on his machine and then after the players all told him it fit on their FG desktop the host would just lock the size and forget it until someone new joined the group with a smaller screen size.
Rolemaster Classic Ruleset Errors with FG v2.9
I've been testing the Rolemaster Classic ruleset with version 2.9 and I've noticed 2 issues so far. One of them is minor but the other one is major.
The minor issue occurs when trying to open a spell list. I was able to track it down to when it is trying to create a windows to fill in the missing levels of the spell list. The error occurs in the onInit function of the spelllist windowlist within the spelllist windowclass of adventure_spelllists.xml. I've been able to validate the error on line 214 of adventure_spelllists.xml. I am pretty sure the error would occur on lines 219, 223 and 227 but I couldn't find any spell lists that were missing level 25, 30 or 50 spells.
The major issue occurs when trying to open the combat tracker. FG crashes before the window loads. I was able to track it down to line 71 of the getSummary function of the combattracker_effects.lua file.
The problems might be from the same root cause but I am unsure why the combat tracker error crashes FG except for possibly the fact that it uses a lot more resources and takes more cycles to fully load the combat tracker.
Did something change in how the windowlist.createWindow function works? I noticed that there was an issue with the windowlist.createWindowWithClass function that occurred with the nWoD ruleset so it might be related to that. Please let me know if you have any questions or need any more information.
Thanks,
Dakadin