It was working ok last night. Would try and loot before re-stealthing and breaking it about 50% of the time. I can't test it until I get home to see how its working with the newest update.
This is the error of the jobs part of the bot itself, I cannot edit the loot part of the profile to loot then stealth as it is a separate file outside of the routine. It could be fixed with some help from admins but currently this is not on my end to fix. I will try to look into editing the loot file somehow to add in stealth if it is possible after looting.
nice, Altec. I knew looting was bot-side, not profile-side, I just didn't know if there was some way from the profile to add a delay. I almost wish that the bot would slow down a little bit when looting, as it does seem to loot and move on at super-human speed. Good for a bot, bad if its being logged.
Well, the bot does 4 basic jobs and keeps cycling through those while on a profile. The routine just goes from top to bottom checking to see what the conditionals are met during the jobs. There is a delay between the abilities on the routine but if he is out of combat it will stealth no matter what job it is on, sometimes looting happens before it gets a change to stealth, sometimes it doesn't
After new ryfto patch it's getting stuck with multiple mobs trying to cast spells on cooldowns, for example side steps and poison malice or shadow assault / shadow stalk. Any suggestions what could cause this?
Could be a code that was changed due to the recent update? haven't tested it yet. Will when I get home though
After reading this a few times, it could be done to where the bot waits x to y seconds, say 1 second to 5 seconds before moving to it's next job, which can in-turn be adjusted to fit to your normal target / kill / loot cycles when you play your toon. More on that later on though!
Any chances you would update the routine? It's an awesome CC and it's the only stealth routine at the moment. The latest patches have just broken it badly, as it spams wep barrage and the two warps constantly if they are all on cooldown, even on single mobs.
Kinda hard to test everything on my end, haven't got around to leveling a new rogue so all I have is basic lvl 8 skills
In development: a configurable "delay" that you can set yourself. IE: You kill a mob, you have it set to wait between 500ms and 120000ms (.5 sec to 2 min) before moving to the next mob after combat exit. Also, planning on getting a ghetto mount option(IE: non "official") for long travel distances.
Ok, I have this working, somewhat, I need more minds checking this out to help me. Inclosed in the .ZIP is the .INI and .DLL for this routine. The .INI has to be placed so opening the address: C:\RogueTest.INI works correctly. the .DLL is a normal routine so place it with those. do not edit the .INI filename, only the MIN_DELAY and MAX_DELAY values. Any other changes will error the routine. Also, note that this "freezes" the game + bot for the duration of the delay, nothing more. Feedback is required to fine-tune this. ------ edit: What this will do is perform a delay when combat ends between the MIN_DELAY and MAX_DELAY to give the image of not 100% bot grind fest we all know and love and hate about botting.
so the delay is the time until the bot attempts to stealth again, or the time to loot? I take it its stealth, but does the bot still loot at the normal speed? What goes in the mount field?
mount i have not got around to, been focusing on the delay. Think of the bot doing this, non-stop 100% of its' cycle: Code: target => kill => loot => target => Now, the delay adds in a variable that makes it look like a player is playing, as in: Code: target => kill => delay timespan => loot => target => I know the code used for the delay time span is archaic in comparison to another command I am trying to understand how to use, but it is all I have to use for now until I can fully understand how to use the wait command. --- edit: And since you put in a MIN_DELAY and MAX_DELAY, your actual delay will be between these two numbers, getting extremely hard to log a routine if they were checking you, at least from that point of view.
1.3 Added variable GCD to all actions, no .INI file required, too much of a headache working the code on that. This is similar with a nice varied GCD wait timer, added some minor bug cleanings as well. Have fun, and tell me what you think! ----- EDIT: Coded a line wrong, fixed minor bugs of the like. Here is the up-to-date one: ----- EDIT 2 Added more DoT's to the list, more minor bug fixes. View attachment 481
I believe I fixed the issue when using AoE, the bot will now only use AoE when the AoE will hit more then 1 target. If it uses AoE and it only hits 1 target please inform me. View attachment 483
[8:19:26 PM] Hawker: ask him to post source as well ^^ since you won't post it (as the text in your 1st post says) - pm him the source i'm sure it's too long, so I think you can email him the source at Hawker@ryftomate.com (if ryftomate doesn't work, i know @honorbuddy.com will)
Ah ok, I will post the source if needed, I just didn't want to upload the source every time it got changed, which is quite often. I sent a PM with it attached.
