is the plugin currently working with the beta? cause when i get the svn into the plugins library I get hit with a wall of red text and prior to the import EB was working fine I've been away from the world of botting for some time now, so many changes....
My notes for revision 324: After getting all the organs in the harvest it does not deliver to piety, just starts new harvest. Also there seem to be crashes where the bot just dcs the client, in sceptre of god, just after entering the temple and loading the stuff there, or after going up the stairs, does not always happen dont know what the problem is, has happened in all previous revisions as well must be a bot thing. If the organs thing with not delviering/not doing malachai happens again I'm gonna post a lot, but Im pretty sure it will, happened on all 4 bots. It used to work in some previous revision.
Do you just extract the root folder into a new folder and put it into Plugins? How did you get this pluggin to work?!
No Logs, I cannot help. I haven't updated quest in about a week or so, so Idk what can break.. I just finished a few sets on Hardcore talisman and I'm at Merc, IDK.
np, just saying, maybe someone else has the same problem, I'll bring logs if it happens again in cruel.
How do I run this? I've installed the plugin, but as soon as I click Start, it just says: "[OldGrindBot] OnStop [CommonEvents] Stop [AutoFlask] Stop [Chicken] Stop [GemLeveler] Stop [ItemFilterEditor] Stop [LowFpsHelper] Stop [ObjectExplorer] Stop [QuestPlugin] Stop [Stats] Stop [StuckDetection] Stop" Can't change OldGrindBot to Quests.
Without logs there is no way to know whats happening. But im going to take a guess that you didnt open up the Quest Plugin Config and use the check boxes to select which quests you want to do. Also, make sure you only pick the Main Quest Line OR the Side Quest Line. You can not enable both at the same time.
2015-12-18 12:40:36,703 [19] ERROR CustomLogger (null) - [UpdateQuestStates] Please Choose One Choice , Main or Optional for Act 1
EB crushes if quest plugin there Hi. Can't start EB at all due this plugin is in plugins directory. Log is attached. Thank you in advance Cheers.
Ok so I've had this issue before on normal now its happening again on cruel, it goes to belly of the beast, does not go kill piety it just teleports out and stops the bot. Restarting it from town gets the same results. Attaching log, also did dump the quest state, not sure what the problem is. Soon I'm going to check the harvest issue I'll have to manually do piety etc. edit1: apparently it was related to the inventory being full and that somehow conflicted with the quest plugin, I went to town thought it was worth a try, sold stuff came back to restart the bot and it continued onward. Now I will be testing the harvest issue with the organs again. edit2: another bot stopped somewehre in belly of the beast lvl1 because inventory full and it teleported to town but wouldn't sell and bot stopped. manually sold, teleported bot and it continued again. Attaching log 2 from that bot.
Making a separate post now with logs regarding the harvest organ issue. 1st bot got all 3 organs, cleared a bit more of harvest, when area was cleared tp'd back to town. Did not deliver organs to piety, started a new harvest and was going for the bosses again. Attaching first log with this, 3 other bots will get there as well very soon, will post their logs as well if issue happens with them as well. I also want to mention that if I deliver organs manually to piety and open up the block ore and start the bot, the bot will not go inside the core to start the malachai event, this used to work in some previous revision even if the organs wouldnt work, even if starting the bot inside the black core during the malachai event, when the bot dies, it does not re-enter the area to continue the fight. edit: attached logs from the other bots, same issue has occurred on all of them. Not sure what the problem is, everything else seems to be working fine, including the arena that had issues in the past. So far all I can figure is that it's like it doesn't recognize piety there and the black core entrance, it seems to be aware of the quest state, maybe something is off with piety/core id, can't think of anything else.
Do you know what revision you're using? I'm using the latest 324 and I get the issues I've mentioned in the above posts. I'd like to test out your revision to see if these issues are present there as well.