FuBar - LuckyCharms

The raid icons placed into a FuBar panel for easy access. Options to arrange the icons into a kill order and report them in chat. When in a party/raid only the leader/assistants can move the icons but they will sync so that everyone will have the same icon order on their screens.

A party/raid member can be assigned to an icon by name and a list of those assignments can be sent to chat. In a party you just have a list of members but for a raid the list is sub-divided by class.

How to use:
For ease of explanation any reference to a group will mean a party or raid. Likewise, all references to the leader will mean the party leader, raid leader, or a raid assistant.

When you right click any LuckyCharms icon in the FuBar panel a menu should come up. Go to Appearance -> Unlock and make sure its checked if you want to rearrange the order of the icons (which is the kill order).

If you are in a group and the leader is also using LuckyCharms then you will be in sync mode. While sync'd only a leader can move the icons around but everyone using LuckyCharms will see the same icon order.

You can disable syncing by opening the menu and going to Sync Mode and then selecting either Disable in Party or Disable in Raid. Disabling sync mode will let you move the icons around but they will no longer be in the proper kill order. Once you turn sync mode back on the icons will move back to the proper order again.

When you are a leader of a group the menu will change and the normal menu will be moved to a submenu at the bottom called Options. You will now have a Broadcast submenu which has the ability to send the kill order to the group through a raid warning and to be able to send any assignments (explained below) through normal group chat. Below that are (optionally) Pull Count and Ready Check which do just what you think.

Next should be the icon of the one you right clicked (or later moused over before moving the mouse into the menu) and some text saying for example "Assign skull to:" Following that is a list of everyone in the group. In a party it is just a list in alphabetical order but in a raid the list is subdivided by class to make it easier to find who you are looking for.

To assign someone just click on their name and they are assigned to that icon. They should get the icon next to their name and in a raid the icon will also be next to their class submenu. To reassign the icon simply click another person's name.

Once someone is assigned there will be a new entry at the bottom of the group member list called "None." Clicking that will set the icon back to having nobody assigned (and remove the "None" entry).

Just like with the kill order, member assignments are sync'd with the group.

If you are in a group but aren't a leader and right click an icon you will still see the list of all members but without the leader options or the ability to click to assign an icon.

Note: It is recommended that you delete the folder(s) for an existing addon when updating to a different version. This is to keep files that are no longer used from taking up space.

Version 1.8.6 (04/18/2009)
- Libarary update

Version 1.8.5 (11/19/2008)
- Attempt to correct an unreproduceable error

Version 1.8.4 (11/17/2008)
- Fixed an issue with FuBar panels that are unlocked

Version 1.7 (08/06/2008)
- Restructured with some recoding to remove a few bugs and to facilitate backward compatibility for future changes
- Debug code moved to its own independent module and no longer included to free up memory

Version 1.6 (05/02/2008)
- Fixed a display issue with FuBar panels that have auto-hide on
- Added a pull count feature
- Changed the addon's category to Raid.

Version 1.5 (04/16/2008)
- Corrected an initialization issue for new users that caused FuBar to not load LuckyCharms as well as many other plugins
- Debug mode will no longer be on by default (was an error) and if debug mode is turned off it will be off when you reload or restart

Version 1.4 (04/12/2008)
- Fixed a bug with syncing in a party and marking targets with icons
- Added the ability to assign group members to icons by name and report a list of those assignments to chat

Version 1.3 (04/10/2008)
- The 'None' icon is now moveable like the other icons and its position determines where a broadcast of the kill order stops
- Icons that are being moved will now always be on top of the other icons

Version 1.2 (04/09/2008)
- Overhaul of syncing to greatly reduce addon channel bandwidth and to be more stable
- Expanded syncing options

Version 1.1 (04/08/2008)
- Rewrote the code for moving the icons to better deal with them being so close together
- Added the ability to switch the 'None' icon to the far right
- Implemented kill order sync while in a party/raid with an option to disable it (incase its buggy)

Originally posted by xteroid Is there an option to hide the icons when I am not in a group?
It will be even better if you can hide the icons if you are in a group but you are not the group leader and your sync is off. (You can't use them anyway)
It is very convenient but I am afraid that it is taking up too much space in my FuBar even when I am solo questing, especially with all my non-tank alts.

Why not just make all your FuBar plugins disply only an icon, or only text? I have over 100 LDB/FuBar plugins and they all fit just fine on mine, even when I was on a smaller screen.

Hi, I posted this on DockingStation's comment too, just in case. Broker_Currency displays several icons next to their respective informational texts, and I thought that this might be a solution to the LuckyCharms issue. Maybe you could have a right click menu where you can reorder things, or a window that pops up to reorder the icons, then when you press "okay" the icons rearrange on the display. However Broker_Currency's author does it, there are more than one icons displayed, but I cannot change the order of icons. Perhaps this is a limitation to the libraries or just a coding oversight, but I thought that a bad idea is better than no idea, since I'm going the Opie way of marking and its really not as fast as I'd like it to be.

Is there an option to hide the icons when I am not in a group?
It will be even better if you can hide the icons if you are in a group but you are not the group leader and your sync is off. (You can't use them anyway)
It is very convenient but I am afraid that it is taking up too much space in my FuBar even when I am solo questing, especially with all my non-tank alts.

Originally posted by Vrul I could break it up but then it would just be icons that placed a raid icon on your target or that you could make an assignment to. You would lose the sync order of the icons as a kill order and the ability to drag and drop them into a kill order.

Originally posted by xtoq I get this error when trying to open a mailbox, without ANY options being set for OpenContainer.

I'll look into this asap.

Originally posted by xtoq For the record, I actually love the theming capabilities of BagBar/OpenContainer.

Then you'll probably like OpenContainer more. It has the same options but I modified the Bank and Keyring files to allow for a better appearance when changing colors. The money section at the bottom matches the themes too.

Originally posted by xtoq In other words, if I want Fubar_LuckyCharms, I have to have FuBar?

Yes. Funny thing is I wrote an LDB display but still only use FuBar.

Originally posted by xtoq That being said, what about display functionality similar to picoButtons? It creates a separate LDB button for each micro menu button. Would that mess up the functionality of the synch and assign modes in LuckyCharms?

I could break it up but then it would just be icons that placed a raid icon on your target or that you could make an assignment to. You would lose the sync order of the icons as a kill order and the ability to drag and drop them into a kill order.

For the record, I actually love the theming capabilities of BagBar/OpenContainer. I don't need the auto open/close 'cause I have another mod. But whichever has the theme options I'll be using. XD

____

LuckyCharms requires FuBar to be enabled to work. However, to display it in an LDB you have to have FuBar2Broker enabled, which causes the new LDB compatible version to break. In other words, if I want Fubar_LuckyCharms, I have to have FuBar?

That being said, what about display functionality similar to picoButtons? It creates a separate LDB button for each micro menu button. Would that mess up the functionality of the synch and assign modes in LuckyCharms?

Originally posted by Vrul Short version: Use the old version since I didn't really do anything of importance other than update the libraries.

Since 3.0 went live in Oct I made a seperate copy of FuBarPlugin-2.0 and called it FuBarPlugin-2.1. There was no real difference between the two except the original still used the global args (this, arg1, arg2, ...) and the other one relied only on passed values. When I was fixing FuBar-MicroMenu I decided to check for newer versions of all the libraries and noticed the latest revision of FuBarPlugin-2.0 was updated to no longer use the globals so I didn't need to include a seperate version any more. So I am now in the process of changing all my FuBar plugins to go back to using the official version of the library.

The issue now is Fubar2Broker assumes all plugins will only ever have an icon and text, just like LDB, so it removes the ability to create frames. To work around this I either have to put in a check that "FuBarPlugin-2.0" is returning frames when it should and abort if it doesn't or rename FuBarPlugin-2.0 to something else.

The first solution will not allow you to use the plugin at all with Fubar2Broker installed. The second solution potentially forces a library to take up twice the resources that it normally would and has resulted in complaints in the past. A third option would be to ask the author of Fubar2Broker to make it more friendly to non-LDB compliant plugins, but I could see that not going over well depending on who it is since I've been told in the past that my plugins violate some secret rule of what a plugin should be.

Ah, I see, this does explain a lot. So, now that LuckyCharms is updated, I should be able to run it without FuBar or Fubar2Broker installed and it will show up in an LDB display, correct? That's a relief; the only mods I was waiting on for LDB functionality were yours, funnily enough. I can't live without BagBar, and when I tried to use Open Container, I got an error (pre 3.1). I just went back to BagBar since I couldn't get rid of LuckyCharms anyways. I'll try it with the new version and no FuBar. Thanks for your quick response Vrul!

Short version: Use the old version since I didn't really do anything of importance other than update the libraries.

Since 3.0 went live in Oct I made a seperate copy of FuBarPlugin-2.0 and called it FuBarPlugin-2.1. There was no real difference between the two except the original still used the global args (this, arg1, arg2, ...) and the other one relied only on passed values. When I was fixing FuBar-MicroMenu I decided to check for newer versions of all the libraries and noticed the latest revision of FuBarPlugin-2.0 was updated to no longer use the globals so I didn't need to include a seperate version any more. So I am now in the process of changing all my FuBar plugins to go back to using the official version of the library.

The issue now is Fubar2Broker assumes all plugins will only ever have an icon and text, just like LDB, so it removes the ability to create frames. To work around this I either have to put in a check that "FuBarPlugin-2.0" is returning frames when it should and abort if it doesn't or rename FuBarPlugin-2.0 to something else.

The first solution will not allow you to use the plugin at all with Fubar2Broker installed. The second solution potentially forces a library to take up twice the resources that it normally would and has resulted in complaints in the past. A third option would be to ask the author of Fubar2Broker to make it more friendly to non-LDB compliant plugins, but I could see that not going over well depending on who it is since I've been told in the past that my plugins violate some secret rule of what a plugin should be.

It is from Fubar2Broker. If you have only Fubar, Fubar_LuckyCharms and Fubar2Broker (all the latest versions) you get this error. If you disable Fubar2Broker you don't get the error. I didn't verify on a clean WTF folder, but I did verify on a clean toon. I also tried with Fubar2Broker and DockingStation, just to make sure it wasn't some "I don't know where to show this" sort of thing, same error. Turning off Fubar2Broker fixes it.

Ok, so another question. Any idea why this doesn't port to LDB with Fubar2Broker installed? MicroMenu does perfectly, but not this and one other mod I have. I'm using both Fortress and DockingStation, and neither of them show LuckyCharms.

Good to hear. I had to guess the cause and looks like I was right. One of the add-ons you're using is polluting the global namespace, more specifically, a variable named 'profile' that I'm guessing is of the type 'frame' or 'table'.