Left "Surprise" Middle "In Spite of it All" Right "Good to be Bud" Can you let me know when you have it updated with these before I run through?
Still need Skyfire 1 info? 1) Daring Harrier 2) Giant Loggers 3) Shoalspine Sahagin 4) 5th Cohort Vanguard 5) Synthetic Doblyn 6) 4th Cohort Hoplomachi 7) Zanr'ak Pugilist 8) Milkroot Cluster 9) Basilisk 10) 2nd Cohort Hoplomachi
Can you grab the latest plugin and run it and then send me the log. Added some logging. Just cant see how that would be happening.
Not sure if this helps you at all, but Skywind I did the Sylph Snarls okay...when it went to the Amaljaa Thamaturges it did 12 for some reason (2 extra), it didn't seem to be due to aggro it looked like it went after them before any aggro. Log attached. Also, I already updated to your latest 13 plugin before running. I did start/stop/start it due to an S rank in the area, but this was before I had even arrived/killed any Amaljaa.
Another problem I found as blm is, Trenchtooth Sahagin is out of LoS (has a wall) so it won't cast on them, any fixes for this? Any way I can set a caster to run up to the mob with Kupo or Ultima? I can't seem to get Magitek range to change (so it's useless for BLM since the default range always puts me too far away for routine to begin).
These FATEs did NOT start after the enemies were complete like my other book did, and nothing I did would get them to run. Attached log. Still need these FATE so I'll wait until after maintenance and hopefully you can have a fix by then. Thanks for your time on this Plugin!
after I updated to ver.131, the bot show below message once and once again... there is no problem when I use ver12 [14:23:19.923 N] Book ID - 7 [14:23:19.923 N] Current Kill Index - 1 [14:23:19.923 N] Current Fate Index - -1 [14:23:20.004 N] Book ID - 7 [14:23:20.004 N] Current Kill Index - 1 [14:23:20.004 N] Current Fate Index - -1 [14:23:20.071 N] Book ID - 7 [14:23:20.071 N] Current Kill Index - 1 [14:23:20.071 N] Current Fate Index - -1 [14:23:20.145 N] Book ID - 7 [14:23:20.145 N] Current Kill Index - 1 [14:23:20.145 N] Current Fate Index - -1 never stopped...
Sounds like the same problem I was having once I got to FATE section of Skywind I, as mentioned in my previous post.
Please replace the file below in your animusbook plugin folder. I had a check to stop the books that were not complete in the code still. . I have removed the check and should be ok now for your problem. Let me know. View attachment Movement.cs
I have just added some logging. Please Ignore for now. Other than the message, is it continuing to kill the mobs? Once I remove the BETA, the logging will stop.
Skyfire 1: Should be killing (for #6, according to your mapping) "4th Cohort Hoplomachi" Instead it is killing "2nd Cohort Hoplomachus". I don't know if this is a technically correct solution as I really didn't crawl in very deep. Just switched which profile numbers it was linked to... Code: //Book Done SkyfireI.Add(1, "Mor Dhona - Daring Harrier.xml"); SkyfireI.Add(2, "Coerthas - Giant Logger.xml"); SkyfireI.Add(3, "Western La Noscea - Shoalspine Sahagin.xml"); SkyfireI.Add(4, "Mor Dhona - 5th Cohort Vanguard.xml"); SkyfireI.Add(5, "Outer La Noscea - Synthetic Doblyn.xml"); SkyfireI.Add(6, "Western Thanlan - 4th Cohort Hoplomachi.xml"); SkyfireI.Add(7, "Southern Thanalan - Zanr'ak Pugilist.xml"); SkyfireI.Add(8, "East Shroud - Milkroot Cluster.xml"); SkyfireI.Add(9, "Northern Thanalan - Basilisk.xml"); SkyfireI.Add(10, "Eastern La Noscea - 2nd Cohort Hoplomachi.xml"); SkyfireI.Add(11, "Giant Seps"); SkyfireI.Add(12, "Make it Rain"); SkyfireI.Add(13, "The Enmity of My Enemy");
So there is a assumption here that seems to be working for far. From the API point of view we know that MOB1KILLED = true or false and similarly MOB2KILLED = true or false. What we dont know is what is Mob1 or Mob2. So the order that everyone seems to be working on is going from the left to right, top to bottom as a index from 1 - 10. Looking at your mob section in the book, Column 1, row 1 is Mob Index 1. Column 1, Row 2, would be Mob Index 2. Then Column 2, Row 1 would be Mob Index 3. Going with that pattern, the dictionary in the code is mapping the index to the mob from 1 - 10. Hoping this is making sense. If you have skyfire I now, what index is 4th Cohort and what index is 2nd Cohort mobs? If they are not correct, then let me know and what you changed is probably correct.
According to the previously posted image: #6, and number #10 were switched around, Think it was just a typo since they both have very similar names. The rest of the grinding profile completed correctly for me after switching them, As per the following quote (from me), I believe I labeled them correctly according to the picture, and upon digging through the file and switching those two myself, it completed for me just fine. After all, it's the same exact name with just a different number in front of it, no big deal, quite easy to misread! The numbering I listed was as per the chart in the above linked picture Quote: You need to register and have one post to see spoilers! More importantly this very moment, I'm having issues with it automatically doing the FATE, it just says that the book is complete and refuses to move. I have done none of the fates for this book ("Giant seps", "Make it Rain", "The enmity of my enemy".) Any ideas? Log: View attachment 6072 2015-04-14 13.29.txt
Now that I am finished with my plugin, I can take a looksy at your beautiful piwce of work over in here. I got everything downloaded and installed to begin my quest for the books and saw your logging addition. I wanted to note though: With the amount of data that you're logging is taking up on every pulse, you are generating more than 200 Kb or .2 Mb worth a data (disk space) a minute. Leading to 12Mb an hour. And that's before any combat and navigation logs. Just my two cents, but, some people might have some issues with disk space.
As long as people clear their logs (don't really need old logs >.>) it shouldn't really be a huge problem I would wager. That's like 1 GB in 4 straight days, and most people don't need to run this for four straights days in succession. He did say though, that logging was going to be fixed up after it was out of beta.
I'm not saying it's all that much to most people. But I am saying it can be significant and a lot of people may not know they can even delete their logs judging by the number who cannot figure out how to post them. It also creates issues with SSD life span, and HDD activity/usage with the number of writes you are doing /sec. Once more, that is before any combat/movement as well, Ultima can very easily take up a meg just by itself in a matter of hours. I'm not that concerned for myself, or most of the people participating actively in this thread, but I did want to give an insight as I noticed it. Just for information's sake. Keep up the good work.
