Collective Guide for Bosses

How to Use

For a thorough explanation, we encourage you to watch the provided instructional video here: https://www.youtube.com/watch?v=J3IOhJ13pgo.

Follow the steps below to understand and take advantage of the collective.

1. Go to the collective tab.
2. Enter in a key that someone gave to you OR generate your own.

1. Boss Collective Key Manager

• where you can manage multiple keys. Useful for users who want to use collective on multiple servers which require multiple keys.

1. Boss Key Nickname
   • You can add nicknames to the keys to make it easier for you to identify the purpose of each key.
2. Delete Key
   • You can delete any keys any time.
3. Generate Boss Key
   • You can generate a new key from here.
4. Add Existing Boss Key
   • To use the same pool of bosses shared from another user, enter in their collective key.
   • Any user who enters the same key as you will have their bosses shared to your collective. You both can then pull those bosses using the auto setter. This helps increase efficiency as other people you know can help you spot bosses!

2. Boss Collective Queue

1. Select a specific key then you can view what bosses are in them.
2. Update Sort Type
3. Sort by:
   1. Priority: Attacks bosses based on your prioritization list.
   2. Distance: Targets the nearest boss first.
   3. Priority then Distance: Sorts bosses by priority first, then by distance.
4. Reference Point:
   • For distance, you can enter reference points for X and Y, which is typically your keep coordinates.
5. Boss Collective Queue
   • Shows a list of bosses found.
6. Local Boss Queue
   • These are bosses stored on your local esb application and are the ones up to be set next.
7. Bosses Recently Set
   • Auto setter now takes into account the rally time and time to march to that boss. That time is added to the recently set list and those coordinates cannot be shared until that time expires.
   • Shows all the bosses recently set by all that share the same boss collective key.
8. Recently Shared
   • This shows the bosses the bot recently found and shared to the collective.
9. Bosses Set History
   • Shows the history of bosses you have set.
   • This will refresh every time the bot restarts.
10. Source of Bosses Found
    • App Source - Map, Alliance Chat, or Whisper are some of the values you would see so you can identify where it came from.
    • User Source - You can identify on bot username who sent the data.
11. Fast
    • True: Boss was found using Fast Search.
    • False: Boss was found using Normal Search.

3. Boss Prioritization

• You can now manage the order of priority of the bosses in your boss' collective queue.

4. Remove Bosses from Queue after Expiration

• Here you can set whether or not to remove bosses from the queue if the setter did not have a setting for the boss it pulled.

5. Boss Expiration (minutes)

• You can set the time a boss will remain in your queue.