Interesting.... searched for a bug which annoyed me on several macros and had a crash on !!!40+ clients over 3 PCs - heavy... here how it worked:
1. started the macro
2. got mq2 running in a loop: "undefined variable in MyBTLblxx" running xx through up 40 (I have mq2mybuttons running enhanced to 50, but only 40 are working - sadly.. I wished somebody would up this absolute genious plugin to more buttons!) -> second line is the error "/declare debug int outer 0" of the macro -> NO crash, only loop
3. removed MQ2mybuttons (because that label sounds like it) -> NO crash, only loop, no changes
4. changed "/declare debug" to "/declare xxxxdebug" -> NO crash, only loop
5. started to remove plugin after plugin (normally after a real long time this /debug-loop ends somehow) while this loop was running
6. was too much time wasted, so i remembered it was a gui to unload all plugins - I tried /gui out of lazyness to look up how the command was
7. instant crash on !!! ALL 40+ clients over 3 computers ->I have not all info but it seems Mq2eqbc has something to do with that. At the freezing screen there was something like "groupsay over eqbc (dont remember and dont like to repeat that)". It seems it interpreted /gui as /g ui and this somehow crashed all EQBC-instances including all EQ-instances.
8. started to check Mq2buttons XML/Ini -> no fault (btw.: I unloaded MQ2mybuttons and this error is still there - strangely)
I get this error with "/declare debug int out 0" on several macros - never cared, thought macro is bad. This time I started to search for the bug.
So there are three problems:
a) /declare debug int outer 0
b) plugin MQ2Mybuttons not working at 40+ and is somehow involved, even not being active as plugin
c) /gui crashes everything in EQBC
I can live with b) and c)
- b) accepting this plugin works only with 40 buttons
- c) not using /gui anymore even out of lazyness looking up commands
But it would be nice for an idea how the hell "/declare debug int outer 0" makes problems while even changing the var "debug" into something which is surely not twice on the system?
addon:
- tested on a test-account /gui with EQBC - no problem, only says something like "you say to your guild:" -> how can such a command crash everything?
1. started the macro
2. got mq2 running in a loop: "undefined variable in MyBTLblxx" running xx through up 40 (I have mq2mybuttons running enhanced to 50, but only 40 are working - sadly.. I wished somebody would up this absolute genious plugin to more buttons!) -> second line is the error "/declare debug int outer 0" of the macro -> NO crash, only loop
3. removed MQ2mybuttons (because that label sounds like it) -> NO crash, only loop, no changes
4. changed "/declare debug" to "/declare xxxxdebug" -> NO crash, only loop
5. started to remove plugin after plugin (normally after a real long time this /debug-loop ends somehow) while this loop was running
6. was too much time wasted, so i remembered it was a gui to unload all plugins - I tried /gui out of lazyness to look up how the command was
7. instant crash on !!! ALL 40+ clients over 3 computers ->I have not all info but it seems Mq2eqbc has something to do with that. At the freezing screen there was something like "groupsay over eqbc (dont remember and dont like to repeat that)". It seems it interpreted /gui as /g ui and this somehow crashed all EQBC-instances including all EQ-instances.
8. started to check Mq2buttons XML/Ini -> no fault (btw.: I unloaded MQ2mybuttons and this error is still there - strangely)
I get this error with "/declare debug int out 0" on several macros - never cared, thought macro is bad. This time I started to search for the bug.
So there are three problems:
a) /declare debug int outer 0
b) plugin MQ2Mybuttons not working at 40+ and is somehow involved, even not being active as plugin
c) /gui crashes everything in EQBC
I can live with b) and c)
- b) accepting this plugin works only with 40 buttons
- c) not using /gui anymore even out of lazyness looking up commands
But it would be nice for an idea how the hell "/declare debug int outer 0" makes problems while even changing the var "debug" into something which is surely not twice on the system?
addon:
- tested on a test-account /gui with EQBC - no problem, only says something like "you say to your guild:" -> how can such a command crash everything?