SpellSetLoader v1.0 by Vayeco Dynn (8/10/04)

Vayeco Dynn · Post by **Vayeco Dynn** » Sun Oct 10, 2004 9:49 pm

Easy, fast, memming spell sets. Nuff said.

| Macro :        SpellSetLoader  |
| Created By:    Vayeco Dynn     |
| Release Date:  Oct 10, 2004    |
| Version:       1.0             |
|--------------------------------|

|----------------------------------------------------------------------|
| Usage:                                                               |
|                                                                      |
| In Sub Main, change the spells to whatever you want them to be. Then |
| save the macro as something that you'll remember for that spell set. |
| For example: MemDefaultSpells.mac                                    |
| To then memorize this set of spells, use: /macro MemDefaultSpells    |
| or whatever you saved the file as. You can make as many spell sets   |
| you'd like!                                                          |
|----------------------------------------------------------------------|

|-------------------------------------------------------------------------------- 
|SUB: Main
|-------------------------------------------------------------------------------- 
Sub Main

   |:: Change these to your liking ::|

   /call MemSpell 1 "Smite"
   /call MemSpell 2 "Poopie"
   /call MemSpell 3 "Kaakaa"
   /call MemSpell 4 "Feign Death"
   /call MemSpell 5 "Gate"
   /call MemSpell 6 "Snoop Dogg"
   /call MemSpell 7 "Christina Applegate"
   /call MemSpell 8 "Amputate Leg"
   /delay 5

/return

|-------------------------------------------------------------------------------- 
|SUB: Memorize A Spell
|-------------------------------------------------------------------------------- 
Sub MemSpell(int GemSlot, string SpellName)

   /if (!${Defined[GemSlot]} || !${Defined[SpellName]}) {
      /echo /call MemSpell [GemSlot] [SpellName] failed, parameters not given.
      /endmacro
   }

   /if (${Me.Gem[${SpellName}]} == ${GemSlot}) {
      /return
   }

   /if (${Me.Book[${SpellName}]}) {
      /echo Memorizing ${SpellName} into Gem ${GemSlot}
      /memspell ${GemSlot} "${SpellName}"
      /delay 5
      :MemWait
      /if (!${Me.Gem[${GemSlot}].ID}) {
         /delay 1
         /goto :MemWait
      }
   } else {
      /echo Error: You do not have ${SpellName} memorized in your spell book. Ending macro.
      /endmacro
   }
    
/return

Shenlon · Post by **Shenlon** » Mon Oct 11, 2004 2:10 pm

Any reason why you would use this over the standard built in EQ spellsets?

peach · Post by **peach** » Mon Oct 11, 2004 2:54 pm

to have more than the max amount

Shenlon · Post by **Shenlon** » Mon Oct 11, 2004 4:17 pm

Ahh didn't know there was a max amount as I only use ~5 for me.

blueninja · Post by **blueninja** » Mon Oct 11, 2004 4:34 pm

I use something similar in a few of my macros so I can put the spell set in the ini file for the macro. That way I don't have to copy the EQ ini files between computers, I just keep the macro ini in a shared folder and it works on all computers.

magictiger · Post by **magictiger** » Mon Oct 11, 2004 5:38 pm

That's why there's a MQ2SpellSet plugin :)

Vayeco Dynn · Post by **Vayeco Dynn** » Mon Oct 11, 2004 6:08 pm

magictiger wrote:That's why there's a MQ2SpellSet plugin :)

Yeah, I know. I figured a lot of people (like me) hate compiling, and this is just a lot easier. Short term, anyway.

Night Hawk · Post by **Night Hawk** » Tue Oct 12, 2004 7:55 pm

1) I don't see how this makes you have any more spells sets, besides just the one you define in the macro.

2) Why would you make a new sub for meming a single spell one by one, when you can already do this?

ex. /memspell 1 "Complete Healing"

*Edit* the only thing that /memspell doesn't havea check for is if your already meming a spell, but that's a simple fix.

Vayeco Dynn · Post by **Vayeco Dynn** » Tue Oct 12, 2004 10:32 pm

Night Hawk wrote:1) I don't see how this makes you have any more spells sets, besides just the one you define in the macro.

2) Why would you make a new sub for meming a single spell one by one, when you can already do this?

ex. /memspell 1 "Complete Healing"

*Edit* the only thing that /memspell doesn't havea check for is if your already meming a spell, but that's a simple fix.

1) You can make as many "macros" out of this sort-of template macro as you'd like.

RaidSpells.mac
HealSpells.mac
SoloSpells.mac
etc...

2) I personally like to make a new sub out of any task that is used in multiple situations. That way if you need to change something about how its done, you only need to make one change, rather than search it out every time you use it and fix it. Its called "encapsulization" - the logical isolation of a function from the rest of your code.