First issue is the GMOTD feature. Whether disabled or enabled, it blocks the original GMOTD from ever being shown. In 4.0.6, the feature properly didn't block the message when it was disabled.
BCM doesn't touch the gmotd, only replicate it. The default WoW client itself will NOT show the gmotd if it's not available at the time of login (due to lag, etc). The difference is BCM will try and wait until it is available to display it. Also hence why it happens when the module is disabled (not loaded).
Bigger issue is something in this now is interfering with other things that may post messages to chat at logon (might be the GMOTD thing). Specifically with Mitsugo. Any saved whispers by that mod that are normally posted to chat when you log on again are never shown (GMOTD feature on or off). Disable BCM, that mod functions again. All other chat mods tested (incl. multi-featured ones) don't interfere. BCM didn't interfere either in WoW 4.0.6.
This is most likely due to the introduction of the chat history module. Calling SetMaxLines clears the chat frame even if you're simply increasing the number of lines. For this reason I load the chat history module first. Nothing I can do other than advise you to disable the History module. I will look into having that module save and restore chat when calling that function.
BCM doesn't touch the gmotd, only replicate it. The default WoW client itself will NOT show the gmotd if it's not available at the time of login (due to lag, etc). The difference is BCM will try and wait until it is available to display it. Also hence why it happens when the module is disabled (not loaded).
Tested through 6 relogs on two different days with both BasicChatMods enabled & disabled as well as that feature enabled & disabled. No lag problems. BasicChatMods enabled (and that feature either enabled or disabled): the default GMOTD never shows up. BasicChatMods disabled: the default GMOTD always shows up (yes, there was an actual GMOTD present on all occasions).
But BasicChatMods' copy of the GMOTD never failed to show up when enabled. This behavior is consistent whether Chatter's "DelayGMOTD.lua" is active or not at the same time.
So something different is happening on this end in 4.1.
This is most likely due to the introduction of the chat history module. Calling SetMaxLines clears the chat frame even if you're simply increasing the number of lines. For this reason I load the chat history module first. Nothing I can do other than advise you to disable the History module. I will look into having that module save and restore chat when calling that function.
Hope it can be improved. Chatter's "Scrollback" (history) module doesn't cause that issue.
Hope it can be improved. Chatter's "Scrollback" (history) module doesn't cause that issue.
Any addon that calls SetMaxLines will experience this issue, Chatter probably just calls it earlier, or restores chat after calling it. Disable the History module.
v6.6
EditBox: Allow hiding of the background.
EditBox: Allow modification of size.
Config: convert some dropdowns into sliders
History: don't clear all chat at login (removing gmotd, etc)
URLCopy: attempt at improving pattern matching
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorBCM doesn't touch the gmotd, only replicate it. The default WoW client itself will NOT show the gmotd if it's not available at the time of login (due to lag, etc). The difference is BCM will try and wait until it is available to display it. Also hence why it happens when the module is disabled (not loaded).
This is most likely due to the introduction of the chat history module. Calling SetMaxLines clears the chat frame even if you're simply increasing the number of lines. For this reason I load the chat history module first. Nothing I can do other than advise you to disable the History module. I will look into having that module save and restore chat when calling that function.
Tested through 6 relogs on two different days with both BasicChatMods enabled & disabled as well as that feature enabled & disabled. No lag problems. BasicChatMods enabled (and that feature either enabled or disabled): the default GMOTD never shows up. BasicChatMods disabled: the default GMOTD always shows up (yes, there was an actual GMOTD present on all occasions).
But BasicChatMods' copy of the GMOTD never failed to show up when enabled. This behavior is consistent whether Chatter's "DelayGMOTD.lua" is active or not at the same time.
So something different is happening on this end in 4.1.
Hope it can be improved. Chatter's "Scrollback" (history) module doesn't cause that issue.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorNothing is different is 4.1 and it's quite possible that both issues you are reporting are the exact same issue.
Any addon that calls SetMaxLines will experience this issue, Chatter probably just calls it earlier, or restores chat after calling it. Disable the History module.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderatorv6.6
EditBox: Allow hiding of the background.
EditBox: Allow modification of size.
Config: convert some dropdowns into sliders
History: don't clear all chat at login (removing gmotd, etc)
URLCopy: attempt at improving pattern matching