Modbot Release re: v5.02

[woobs]

ModBot community -

My apologies to all for the long delay in getting the latest update posted. I stubbornly wanted to get the StuckGems changes into the code and this was a difficult thing to test since I couldn't reliably reproduce the EQ bug. Basically, you just had to wait for it to happen. FWIW, it seems to be related to Bard's quicktime.

My next priority is the TLP-specific support issues, pulling, and charming. Please continue to post your issues, fixes, and suggestions. It is great to see MB used in so many different situations/combinations!

- Woobs

 

[devian12]

Does charm work in any capacity? I can caste allure once but won’t recast.

 

[swarmhost9922]

Does charm work in any capacity? I can caste allure once but won’t recast.

My enchanter, druid, necro, and bard all charm extremely well with modbot on TLP.

 

[Venun]

I use this for my charm settings. Not sure if it's right. I used to have TarCnt set to 1, so he would charm anything with the mindset that while I was out of camp pulling on my SK, he would recharm if it broke, but that wasn't always the case. Sometimes he recharmed, sometimes he didn't. I couldn't figure out why. Wasn't a mana issue. /shrug

[AD3]
Gem=3
Spell=Allure
SpellFoci=
DurMod=0
SpellAlias=charm
Announce=/bc [+u+]Charming[+x+] << %t >> with [+u+]%s[+x+]
SpellMinMana=50
SpellRecast=1
SpellCastonResist=tash
SpellDelay=0
TarCnt=2
TarType=12
TarBegHP=200
TarEndHP=85
IfSpellImmune=
UseHoTT=0
PreCondition=/if ({Target.Level} <= 51 && !{Target.Slowed.ID} && !{Me.Pet.ID}) /return TRUE

 

[woobs]

My enchanter, druid, necro, and bard all charm extremely well with modbot on TLP.

Would you care to post one of your ini's that have Charm working well? I have seen several questions on charming and I am sure it would help others

 

[swarmhost9922]

I will gladly post an example once I am finished slamming my face on the desk working out a CH rotation with modbot.

 

[kett73]

I set this up on test to run on rizlona. I have not checked it on tlp yet. Going to setup new ini's for 50 this week. However, it worked like a dream on test when I was trying it out. I had to do the initial charm, but after that i could keep a mob charmed.

 

[rural_gammie]

@kett73 Thanks for sharing that ini, it gave me a couple of ideas for my own. I am always looking at my ini files in an effort to improve them or make them more efficient.

 

[woobs]

I will gladly post an example once I am finished slamming my face on the desk working out a CH rotation with modbot.

Interesting problem. Did you get something to work for you? I'd be curious how you did it.

 

[TheDonkey]

I will gladly post an example once I am finished slamming my face on the desk working out a CH rotation with modbot.

Would you have time to share that example now?

 

[sebbun]

My ini isn't perfect, but it's made charm a lot less annoying. I'd say it works probably 50-75% of the time if I have no mobs pulled and probably 25-50% when I have mobs.

I have an event that's looking for Allure to wear off. When it does, it does the following:

1. I turn off debuffs and Melee so that MB doesn't decide to start on something else.
2. I stop casting incase I am midbuff
3. I clear my target
4. I tell me shaman assist the to cast Malo.
5. I then wait 3 seconds to make sure that the ex pet hits me.
6. I cast tash, stun and then re-charm.

If I had a wishlist for charming, I'd want the following:

1. Set Pet for recharm so that when charm breaks, I have some way to target the same mob that was charmed already. < If i had this I wouldn't have to get hit!
2. cast either a direct stun or AE stun depending on distance of the target
3. Cast tash and then a charm spell

I'm fairly confident reading over posts that the above is doable likely with the work you've already done with Modbot, but those of us not giftaed with coding experience aren't capable of doing it.

 

[sebbun]

I've updated this considerably and figured I'd include a copy for everyone. This does all of the following:

- It mezzes, but skips Xtarget 4 and 5. I set these as targets for (group Mark 1 and Mark 2). More on this later, but quick note on why: I run with another enchanter, so I added my Pet and hers to Xtarget so my enchanter doesn't try to mez her pet or my own.
- On charm break, it targets what is set to Xtarget 4 (mark 1).
- Enchanter casts Tash > stun > Allure, Shaman casts Malo
- If Allure is interrupted, it'll cast Stun > Allure again. This is a loop until the charm lands.
- Once charm lands, it targets the enchanters pet, and sets the group mark to 1. I have Group mark 1 set to Xtarget 4. This means that you find yourself charming a new pet, it'll mark the new pet for you.

In short, in-game, all you need to make sure is that Xtarget 4 is set to group mark 1. You'll want to set Xtarget 5 to something (Or remove this portion of the preconditional for Dazzle), otherwise, you'll risk skipping mezzes on mobs that land in this slot.