[Plugin] I Want Movement - Use LazyRaider CR's with afk bot bases

Hey Millz I know this is not the reason you made it but it didnt work for me in bg's. It does work if im using bg buddy etc and very well but not if im using lazyrider and the plugin for melee in bgs. Is there any way to add this feature? Would certainley donate extra if it is doable hehe

 

Tapatalk needs a double thumbs up button just for this plugin :thumbup::thumbup:

 

It should do it, but you'll need to check some settings...

In LazyRaider
-> Uncheck 'Disable Plugins' - You want to allow them.

In IWM
-> Enable Movement (disable targeting - facing is up to you..)
-> Change Movement Throttle Time to something like 300-500ms (to check where the target is and click faster when chasing someone down).
-> Change Stop Distance to 1, Max Distance to 3 (so it keeps on the move). It'll give you a warning that stop distance is too low but just ignore it.

Let me know how you get on.

 

Hey Millz,

Did all that still no luck I use death grip and the cc cuts in but the bot still doesn't move at all from the spot I tried tyrael as well but same thing. I tried it with pure rotation as the cr just to make sure that it wasn't a conflict between tuhanahs cr and the plugin but it didnt move with pure rotation either. So im assuming its a lazyrider, tyrael interface problem. Thanks for trying to help though

 

Can you post the log please? May have enough detail that I can resolve it, otherwise i'll have to wait until later to try it out.

 

See if that log helps otherwise ill make another one for you

View attachment 4896 2013-05-01 20.09.txt

 

Ah that looks like a meshing issue. Honorbuddy can't work out how to get from where we are to where we want to go.

Could not generate path from {2083.559, 141.2155, 29.33632} to {2069.948, 137.8253, 16.66765} (time used: 0 milliseconds) @ FindStartPoly

Was it in a battleground (if so, which one?). Does it not work in any battleground?

 

Doesn't work in any bgs I have tried as yet Millz.

 

Oh, that's interesting. I'll have to try it out later and see what I can do.

 

Update;

- Clear target if friendly player
- Prevent plugin pulse if dead/flying/on transport/mounted


Still need to look over PvP stuff. Haven't had a chance to look into it yet.

 

this doesend works it gives me an error

[RoutineManager] ReloadRoutineAssemblies called.
Compiler Error: error CS0006: Het metagegevensbestand System.Runtime.Caching.dll is niet gevonden for questing

 

Post een logfile dan ... Zo kan Millz er niks mee.

 

You need to install net 4.0 mario

 

its working now i needed frame work 4.5 i didnt had that yet its nice thnx for this awsome plugin

 

Thanks for this wonderful plugin Millz, iv been running it in LFR/Dungeonbuddy with my Priest. I just have 1 small thing Iv noticed while running it, im not sure if it can even be fixed.
Thing is when Dungeonbuddy runs its scripts on bosses, IWM wants to do its own thing. It stutters foward and sideways like the two are fighting over where to go next.

It is very noticeable in LFR as people are so close to one a nother. Im not sure what a good fix would be for this, but if its possible to fix it that would make it flawless in my eyes.

Thanks in advance.

/Mupp

 

Same seems to happen with some questbehaviors, other then that it works great

 

Hmm I think Dungeonbuddy controls all of the movement and targeting itself anyway, you should be good to just disable movement and targeting within the plugin, then leave facing and rest enabled.

As for the quest behavior stuff, I'm not really sure. A potential solution is to hook the main 'Combat' call for the CR, and perform the movement there rather than doing standalone checks on the plugin pulse. In theory it should be as acurate as the CR controling the movement.

I'll have a play about with it tomorrow if I have time.

 

[IWM Warning]: Current Combat Routine is null - Override behavior may not work correctly.

I always get this when running with PureRotation. Does it actually mean anything or can I continue to ignore it?

 

It's fine, it's because it tries to hook to the routine before its loaded, the next pulse it hooks fine. Ill remove the message, was more for me when developing.

 

Omfg thank you !