Ahh ok, so he is using memory to find out how many daily quests instead of RoMScript. I like it.
Well now I see the address for it in 4.0.0 I should be able to find it in 4.0.1 I'll just need to check how it looks in 4.0.0 I still have an old version of game I can open from Olly. I'll have a look tomorrow to see if I can find the new address.
For now you can just use RoMScript
repeat
player:target_NPC("npcName");
yrest(1500);
sendMacro("ChoiceOption(1);");
until waitForLoadingScreen(7);
Before I updated (had to due to the 4.0.1 patch) it worked perfectly fine. Now, the bot talks to the NPC, uses option 1, then waits and finally reports "The loading screen didn't appear...", yet I just finished watching the game client go to a loading screen for about 3-5 seconds, then load the area like it should and always has. Worked before the changes to waitforloadingscreen, doesn't work afterwards. For now I'm going to manually revert back to the old waitforloadingscreen function so the bot continues working until this is fixed.
Mushroomstamp wrote:Does anyone have the new dailycomplete_ptr and dailycomplete_offset addresses? Or care to tell me the best way to go about figuring them out myself? I'm still not good with CE. =(
The way he's using it
dailycomplete_ptr should be 0x9CD1E0
Although I don't know why he's using an address and offset. The address it points to is static. You could just read address 0x9DD54C.
Please consider making a small donation to me to support my continued contributions to the bot and this forum. Thank you. Donate
I check all posts before reading PMs. So if you want a fast reply, don't PM me but post a topic instead. PM me for private or personal topics only.
CrimsonSoul wrote:waitForLoadingScreen not working right.....
I did make a change to waitforloadingscreen but I don't see why it doesn't work. It checks to see if your address has changed and as far as I know it always does when teleporting. Hm... maybe the address changes before waitforloadingscreen is called. But you said it showed the loading screen for 3.5 seconds.
We could do a double check. Would you try something for me?
CrimsonSoul wrote:That seemed to work flawlessly, hit the NPC option 1, loading screen appeared for about 3 seconds, bot continued on along its normal waypoints.
Updated in rev 628.
Please consider making a small donation to me to support my continued contributions to the bot and this forum. Thank you. Donate
I check all posts before reading PMs. So if you want a fast reply, don't PM me but post a topic instead. PM me for private or personal topics only.
SpiralV wrote:I take a look at the endless feedbag harvest problem.
In any case only Objects in distance can harvested again, i insert 2 lines to prevent them.
Updated in rev 628.
Please consider making a small donation to me to support my continued contributions to the bot and this forum. Thank you. Donate
I check all posts before reading PMs. So if you want a fast reply, don't PM me but post a topic instead. PM me for private or personal topics only.
Use File->'save as', now you can select the character encoding.
By default player.lua saved with UTF-8 may be the file contains some special characters.
Change it to ANSI and ignore the warning.
Found it ^^ in Line 3132
-- id 110502 Dan (Gemischtwarenh�ndler