Hi, great macro, thank you for making it. I'm having a few issues, need a little help, maybe useful feedback, maybe it my settings.
I ran this with a 110 Rogue so far. Getting task and heading to the hallway to set the 'camp' works great, they run to each council person with Hide/sneak on, but do not attack any unless the mobs are in their walking around script. I see a mwssage about "Done fighting. Mob is dead." when they go to each mob, the sleeping ones, the sitting ones is the same. I have to manually hit attack when they run to each mob (unless they are in walking script, as many of them all get up and walk around every so often which then makes the fight dicey as its too many for my guy to solo/molo).
After killing 10 I hide/sneak up and run back but the Frosthoof Braxi see through Sos 2 (Rogues are new to me so I am unsure if thats normal). After killing the frosthoof I have to run back to the camp spot to restart the run back to questgiver. It does not just continue, sound odd? I'm dying a few times and trying to figure out what might be wrong. Ideas anyone?
There are a couple things that can prevent your character from attacking after it gets to a mob
- The target was cleared by the time you got there (as in, you don't have anything targetted)
- MQ2Melee issue with having /attack off (or on?) that prevents you from swinging. Common issue for casters running MQ2Melee.
Do you have a healer merc up? I designed this mac originally on my 115 Rogue. Sometimes if I'm not getting lucky on assassinates they can get a bit rough w/o a healer.
My macro gets hung up after requesting a new task, it will sit there at the quest NPC.
Any thoughts on what I can do to help push it along?
Edit: removed levi, and it still ends after getting a new task. Running the macro again will make everything work again. I have not yet once been able to run two quests back-to-back in the 10 or so that I have completed.
What did you do to get the macro to keep going?
I ran this on my 115 Gnome Rogue right now to test, here's exactly what I did (with MQ2Melee on/off):
- Zoned into Shard's Landing from Guild Hall
- No buffs except Lev
- Type /mac fragmentfarm
- Hands off the keyboard the entire time
Then he:
SoS'd up and ran to NPC, got quest, SoS'd again and ran to first spot in hallway. Started killing a pather, then went through the list. Quest finished, ran to first point, then ran back to quest NPC, turned in, requested, repeat.
I thought it might have been a race issue, but I've watched one of every race run the gamut several times.
Yeah. Since there's numerous folks running the exact same script in the exact same zone, you'll have timing issues where 2-10+ bots are making their way to the same newly-spawned mob.
I give it a week, maybe less, before GMs are watching people automate this and passing out vacations like Halloween candy.
It's really obvious when people are running, unmounted, across the zone back and forth, camping in the same spots, etc. And since SL won't be populated enough to open additional /pickz instances, and this is the base zone for an expansion, everyone will notice it.
To your original point about certain kill credits -- that's possible, I put "extra" mobs in the default kill list for testing. Can remove whatever doesn't work from validTargets in that case.
Those are the primary locations the mission wants you to be. If people are conflicting, the locations can be added/removed from ObjectiveCoordinates and the ObjectiveRadius can be reduced so that you're effectively just camping a certain spot. The macro draws a blue circle to indicate where you're killing.
Another guild on my server formed a raid and had folks sitting at the quest NPC/entrance. One dude was running and everyone got credit. That's what I did for Hunter in PoP.