Bugreporter

Ah, btw. I like stars and reviews ;-)

Could I something made better?

I hope, I understand you right.

1) The Baron as killed, but the loot-a-range would not be used ?

2) Or is the loot-a-range used, but there was no drop?

at 1) no idea at all, but did you see the quest-entry in your Log (debug=on)

[D] ti:me:01 - [Quester] RunLuaCode: local function UseContainerItemByName(search)

...

[D] ti:me:02 - [Quester] Wait: 5000 ms

at 2a) this could happened if the Baron is behind you, (bad luck, next time will be better)

at 2b) if the loot windows is opened, but auto-loot is off (auto-loot must be on)

at 2c) or isnt used in a time of 5 sec (increase wait 5000 sec to 7000 (i.e.) or edit Quester to redo the RunLuaCode and Wait a second time)

Did you use Blizzard or private server? Blizzard changed the Scenario ID. A privat server maybe not. If you use a Blizzard server send me the log of a run via pm.

They changed the ID of the Scenario Criteria (Kill Baron) in 6.1. I have uploaded a new Version (2b)

P.S. the file without the "GotoDungeonLong" is newer.

The problem is, that I work with hotspots. And I tell the bot that there is a hotspot (for teleport) behind the Dungeon-Gate. This works most of the time, but sometimes the bot reach the hotspot, didnt find the teleport (the one near Slabhide), and runs back to the second (real) hotspot. Try to modify the second hotspot moderatly (+/-0.5) in the first and or second coordinate (x,y). I will have a look later but not htis week.

Start the Easy Quest Editor

Open the File

Menu Tools / Quest Order Editor

the waits need to be modified. In v1 you find the "Big Wait" (3 min) at position 9

Or, faster:

- go to the log-window.

- enable debug (ON)

- start

now you see the spells that are known and unknown. Check, why the spells are unknown (wrong talent, race-specific,...) and do the changes that you want and can do.

P.S.: And change your petname in the fightclass editor, if your pet ist not namend "Wolfmother"

- open the file in the fighclass editor

- General settings (the window upper left)

- scroll down

- call pet spell name: <change this>

I have considered, to use the waittime (1/2 hour) to wait for Aeonaxx. But I have changed my mind, because its very difficult to test and to find the right time to enter the dungeon again.

Maybe.... ;-)

Happy... after 6 hours I get my mount :-) . But I will update to v2, if the problems/Suggestions are solved.

Maybe I have a solution with multi-scenario-sriterias

_, _, completedObj,_,_,_,_,_,critID = C_Scenario.GetCriteriaInfo(1); if critID ~= 24922 then completedObj = 'true'; end;

instead of

_, _, completedObj = C_Scenario.GetCriteriaInfo(1);

In the second step (syntax not checked) I check also the critero ID. Is the ID wrong, then is the criterio gone (so my hope). Is it true, ComleteID will do the job.

But did I see it right, thart completeObj is not local? (critID also, but this is only one line more.)

A good sample. I can work with this if the target is a boss. but in one case the targets are mobs (farming for a very rare drop). With this i didnt found a good condition to break the loop. And there is also a door on the farm way.

Maybe a good break condition would be something like "no mobs found" or "in the near of position x,y,z". But my c# is bad . Any Ideas ?

Just tested on Stratholme: In this case, you have more then one Scenario Criteria Info: (First the 3 Ziggurate - Bosses, second the 9 Monster, third the Baron.). Wrobot checks the criterias for exit to fast and because of this, the Profile stops to fast. The Stratholm Profile has some other Problems, but this is at first my Problem (I Think)

the download off this file takes longer then "farming" the SCRAP-E Card whitout it.