[party]

Gave it an hour run through. Results are as follows

Gyazo - 1ad3ed2a2df00495f8bb9e26b5e2962a.png

it would do my bank run, then sit at the door after phasing into the wintertodt room spamming between "moving to roots" and "wintertodt combat manager" then when time got too low to get the 500 points, it would move to the middle of the wait area and have the time < 500 points message up. Had 1 good run before this started happening.

You mean it would go to the middle of the room mid-fight?

When waitiing for a game it just kept walking in and of the doors

Spoiler

[00:00:00 [ DEBUG ] To enable verbose output, run Spectre with -verbose as a program argument
00:00:00 [ WARN ] SettingsRegistry has not been loaded properly
00:00:00 [ DEBUG ] [PlayerSense] key="p_fatigue_factor" value=0
00:00:00 [ DEBUG ] [PlayerSense] key="p_prediction_delay" value=197
00:00:00 [ DEBUG ] [PlayerSense] key="p_camera_while_stepping" value=0.21001367996988002
00:00:00 [ DEBUG ] [PlayerSense] key="p_common_modifier" value=0.9241489178508817
00:00:00 [ DEBUG ] [PlayerSense] key="p_afk_breaking" value=0.284687751768104
00:00:00 [ DEBUG ] [PlayerSense] key="p_actionbar_spam_chance" value=0.5868278971531391
00:00:00 [ DEBUG ] [PlayerSense] key="p_break_spacing_min" value=37
00:00:00 [ DEBUG ] [PlayerSense] key="p_break_spacing_max" value=133
00:00:00 [ DEBUG ] [PlayerSense] key="p_break_duration_min" value=5
00:00:00 [ DEBUG ] [PlayerSense] key="p_break_duration_max" value=35
00:00:00 [ DEBUG ] [PlayerSense] key="p_antipattern_spacing" value=13
00:00:00 [ DEBUG ] [PlayerSense] key="p_idling_average" value=144
00:00:00 [ DEBUG ] [PlayerSense] key="p_area_roaming_precision" value=6.19430784738227
00:00:00 [ DEBUG ] [PlayerSense] key="p_shift_drop_mouse_moving_timeout_average" value=335.5748570977445
00:00:00 [ DEBUG ] [PlayerSense] key="p_shift_drop_release_delay" value=487.30369346007484
00:00:00 [ DEBUG ] [PlayerSense] key="p_fast_mouse_click_delay_average" value=51.07364794540665
00:00:00 [ DEBUG ] [PlayerSense] key="p_fast_key_press_delay_average" value=56.23939612685364
00:00:00 [ DEBUG ] [PlayerSense] key="p_enter_amount_number" value=66
00:00:00 [ DEBUG ] [PlayerSense] key="p_minimum_run_energy" value=68
00:00:00 [ DEBUG ] [PlayerSense] key="p_minimum_entity_visibility" value=89.97154433977855
00:00:00 [ DEBUG ] UI loaded in 4 milliseconds
00:00:00 [ DEBUG ] file:/C:/Users/famil/RuneMate/bots/storage/PrimeWintertodtSale/primera.css
00:00:00 [ INFO ] Waiting for start...
00:00:18 [ DEBUG ] Start button pushed
00:00:18 [ INFO ] Starting
00:00:18 [ DEBUG ] successfully invoked start
00:00:20 [ INFO ] Waiting until next spawn, not enough time to reach 500 points.
00:00:59 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:00:59 [ ERROR ] Brazier actions: [Fix]
00:01:00 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:00 [ ERROR ] Brazier actions: [Fix]
00:01:00 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:00 [ ERROR ] Brazier actions: [Fix]
00:01:00 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:00 [ ERROR ] Brazier actions: [Fix]
00:01:01 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:01 [ ERROR ] Brazier actions: [Fix]
00:01:01 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:01 [ ERROR ] Brazier actions: [Fix]
00:01:01 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:01 [ ERROR ] Brazier actions: [Fix]
00:01:33 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:33 [ ERROR ] Brazier actions: [Fix]
00:01:33 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:33 [ ERROR ] Brazier actions: [Fix]
00:01:33 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:33 [ ERROR ] Brazier actions: [Fix]
00:01:34 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:34 [ ERROR ] Brazier actions: [Fix]
00:01:34 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:34 [ ERROR ] Brazier actions: [Fix]
00:01:34 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:34 [ ERROR ] Brazier actions: [Fix]
00:01:35 [ ERROR ] Failed to assigned: Brazier [1638, 3997, 0]
00:01:35 [ ERROR ] Brazier actions: [Fix]
00:02:30 [ INFO ] Walking to preferred side: Area[center=Coordinate(1620, 3993, 0),radius=8.0]
00:03:28 [ INFO ] Moving next to brazier
00:03:32 [ INFO ] Spam-clicking brazier
00:03:37 [ INFO ] Chopping roots
00:03:48 [ INFO ] Eating food
00:03:52 [ INFO ] Chopping roots
00:03:58 [ INFO ] Eating food
00:03:59 [ INFO ] Chopping roots
00:04:12 [ INFO ] Eating food
00:04:20 [ INFO ] Chopping roots
00:04:43 [ INFO ] Using knife on Bruma logs
00:04:47 [ INFO ] Fletching
00:04:51 [ INFO ] Eating food
00:04:53 [ INFO ] Fletching
00:04:54 [ INFO ] Using knife on Bruma logs
00:04:58 [ INFO ] Fletching
00:05:01 [ INFO ] Eating food
00:05:02 [ INFO ] Fletching
00:05:03 [ INFO ] Using knife on Bruma logs
00:05:07 [ INFO ] Fletching
00:05:31 [ INFO ] Eating food
00:05:32 [ INFO ] Fletching
00:05:33 [ INFO ] Using knife on Bruma logs
00:05:39 [ INFO ] Fletching
00:05:55 [ INFO ] Using knife on Bruma logs
00:05:59 [ INFO ] Eating food
00:06:01 [ INFO ] Fletching
00:06:02 [ INFO ] Using knife on Bruma logs
00:06:06 [ INFO ] Feeding Brazier
00:06:12 [ INFO ] Maintaining brazier
00:06:13 [ INFO ] Feeding Brazier
00:06:25 [ INFO ] Retreating to bank
00:06:25 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:28 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:28 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:29 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:29 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:30 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:30 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:31 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:31 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:32 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:33 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:33 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:34 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:06:42 [ INFO ] Continuing dialog
00:06:44 [ INFO ] Retreating to bank
00:06:45 [ INFO ] Waiting until next spawn, not enough time to reach 500 points.
00:06:49 [ INFO ] Retreating to bank
00:06:49 [ INFO ] Walking to bank
00:06:49 [ INFO ] Retreating to bank
00:06:50 [ INFO ] Walking to bank
00:06:50 [ INFO ] Retreating to bank
00:06:50 [ INFO ] Walking to bank
00:06:50 [ INFO ] Retreating to bank
00:06:50 [ INFO ] Walking to bank
00:06:51 [ INFO ] Retreating to bank
00:06:51 [ INFO ] Walking to bank
00:06:51 [ INFO ] Retreating to bank
00:06:51 [ INFO ] Walking to bank
00:06:52 [ INFO ] Opening Bank
00:07:00 [ INFO ] Bank Pin has been activated!
00:07:07 [ INFO ] Withdrawing: ^Hammer$
00:07:14 [ INFO ] Withdrawing food
00:07:17 [ INFO ] Closing Bank
00:07:20 [ INFO ] Walking to doors
00:07:28 [ INFO ] Entering the Doors of Dinh
00:07:31 [ INFO ] Retreating to bank
00:07:31 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:07:33 [ INFO ] Waiting until next spawn, not enough time to reach 500 points.
00:07:44 [ INFO ] Retreating to bank
00:07:44 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:07:45 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:07:45 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:07:46 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:07:47 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:07:51 [ INFO ] Walking to doors
00:07:55 [ INFO ] Entering the Doors of Dinh
00:07:58 [ INFO ] Retreating to bank
00:07:58 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:00 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:00 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:00 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:05 [ INFO ] Walking to doors
00:08:19 [ INFO ] Entering the Doors of Dinh
00:08:21 [ INFO ] Retreating to bank
00:08:21 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:22 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:23 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:23 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:24 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:24 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:24 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:25 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:25 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:26 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:26 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:26 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:27 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:27 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:28 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:28 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:08:28 [ INFO ] Eating food
00:08:30 [ INFO ] Chopping roots
00:08:44 [ INFO ] Eating food
00:08:48 [ INFO ] Chopping roots
00:08:56 [ INFO ] Eating food
00:09:03 [ INFO ] Chopping roots
00:09:09 [ DEBUG ] Start button pushed
00:09:09 [ INFO ] Starting
00:09:09 [ DEBUG ] successfully invoked start
00:09:09 [ INFO ] Chopping roots
00:09:12 [ INFO ] Moving camera towards brazier
00:09:12 [ INFO ] Chopping roots
00:09:33 [ INFO ] Fletching

Thanks, that's actually helped me verify a pretty important bug.

Can you add a feature to the bot where it can use redemption for health regen when blow 10 %
 

Thanks
 
There a way you add a feature where once a game is over you use duel ring to tp to clanwars and restore stats and then tp back to wnderttodt via neckless , also if you die is it possible for you to make it so the bot can tp back to windertodt ( by getting amy out of bank or using the one your wearing)

The bot should never allow itself to fall below ~50% health. It's a little too risky to rely on the bot letting your health fall that low, especially if using on an account with higher total HP.

@Gengsta actually recommended the dueling -> clan wars -> wintertodt option. I'll give it a look.

 

[party]

Party updated Prime Wintertodt - Sale! with a new update entry:

Prime Wintertodt - Sale! v1.1.1 Released!

Prime Wintertodt - Sale! updated to v1.1.1.

Read the rest of this update entry...

 

[oxygenthief]

When using cake's (Currently 10hp so makes the most sense) would it be possible to make it eat 2/3 cake and slice of cake as well? Seems that it only eats the first slice currently from my first kill. Or would that just require me to add all three food names in to make it do so?

 

[prodigy]

is it at all possible for the bot to start burning logs to get to 500 pts rather than keep cutting the logs and run out of time? Happened a couple times where if it had deposited the logs instead of continue cutting i would have had 500 points. Basically it stops cutting logs when it has enough for 500 then goes back into cutting

Other than that the bot is running amazing

 

[party]

When using cake's (Currently 10hp so makes the most sense) would it be possible to make it eat 2/3 cake and slice of cake as well? Seems that it only eats the first slice currently from my first kill. Or would that just require me to add all three food names in to make it do so?

That'd require a Regex pattern. I can make one for you now if you want then maybe add a list of defaults in the bot UI for people to choose from, or specify their own?

For cakes you'd need:

^(\d\/3 slice of )?(c|C)ake$

is it at all possible for the bot to start burning logs to get to 500 pts rather than keep cutting the logs and run out of time? Happened a couple times where if it had deposited the logs instead of continue cutting i would have had 500 points. Basically it stops cutting logs when it has enough for 500 then goes back into cutting

Other than that the bot is running amazing

Yes, @Serene actually recommended this above, it'll require a little bit of work but I can make it happen.

 

[oxygenthief]

That'd be awesome if possible I also think a list of defaults in the UI would make it more user friendly but either way would be well used for HCIM and skillers/low levels as such.

 

[prodigy]

That'd require a Regex pattern. I can make one for you now if you want then maybe add a list of defaults in the bot UI for people to choose from, or specify their own?

For cakes you'd need:

^(\d\/3 slice of )?(c|C)ake$

Yes, @Serene actually recommended this above, it'll require a little bit of work but I can make it happen.

Im still getting 100k fm xp without it, but not any of the pyro gear+ with the 500 pts xp could be increased a lot.

Still super happy with how the bot is doing, but if you could implement that feature, it would be the absolute best

 

[haris01211]

When using this bot your health will never go below 10% anyways, so this would be useless :>

Yeah it went belove 10% cause I forgot to equip iteams for warmth

 

[party]

That'd be awesome if possible I also think a list of defaults in the UI would make it more user friendly but either way would be well used for HCIM and skillers/low levels as such.

Make sure I got the spelling right...

^(\d\/3 slice of )?(c|C)ake$

Im still getting 100k fm xp without it, but not any of the pyro gear+ with the 500 pts xp could be increased a lot.

Still super happy with how the bot is doing, but if you could implement that feature, it would be the absolute best

Yeah I'll get it done tonight.

 

[oxygenthief]

I've also found that the % health it thinks is too low to get 500 points when you're fletching and getting constantly hit may be too high, I've paused it and made it to 500 points comfortably a few times

 

[party]

I've also found that the % health it thinks is too low to get 500 points when you're fletching and getting constantly hit may be too high, I've paused it and made it to 500 points comfortably a few times

When it gets to that point, does it wait in the middle or retreat to the bank? The difference is important because one is a genuine logical defect and the other is just me being a little too careful.

 

[oxygenthief]

When it gets to that point, does it wait in the middle or retreat to the bank? The difference is important because one is a genuine logical defect and the other is just me being a little too careful.

I'll check this next kill. Currently it's been getting 3/4 of the way through fletching an invent and then running back without putting any in the brazier and I've been manually finishing the fletching and lighting but I'll let it do it's own thing this next kill and let you know

Update: It's just running to the middle of the waiting room and not retreating to bank. Just did it at ~55% even though it has enough kindling in the inventory to reach 500 points.

Update2: Got half way through fletching first inventory and then at 55% stopped fletching and went back to waiting room again. Manually fletched and lit the one inventory and hit 500 points with 25% left to go.

 

[haris01211]

When fletching the bot randomly runs down the side of the path.
Here logs of when it happened hope it helps.

Spoiler

00:13:32 [ INFO ] Eating food
00:13:33 [ INFO ] Chopping roots
00:13:33 [ INFO ] Moving camera towards brazier
00:13:33 [ INFO ] Chopping roots
00:13:34 [ INFO ] Moving camera towards brazier
00:13:34 [ INFO ] Chopping roots
00:13:45 [ INFO ] Eating food
00:13:47 [ INFO ] Chopping roots
00:13:48 [ INFO ] Eating food
00:13:49 [ INFO ] Chopping roots
00:13:54 [ INFO ] Moving camera towards brazier
00:13:54 [ INFO ] Chopping roots
00:13:54 [ INFO ] Eating food
00:13:56 [ INFO ] Chopping roots
00:14:06 [ INFO ] Eating food
00:14:07 [ INFO ] Chopping roots
00:14:36 [ INFO ] Eating food
00:14:39 [ INFO ] Chopping roots
00:14:39 [ INFO ] Retreating to bank
00:14:40 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:41 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:42 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:43 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:43 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:44 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:44 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:45 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:45 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:46 [ WARN ] RegionPath was null, reverting to BresenhamPath

 

I've also found that the % health it thinks is too low to get 500 points when you're fletching and getting constantly hit may be too high, I've paused it and made it to 500 points comfortably a few times

Yeah this has happened to me a few times , This is why i suggest a feature in which if you die it come back and loots and and the bot starts over again
 

When it gets to that point, does it wait in the middle or retreat to the bank? The difference is important because one is a genuine logical defect and the other is just me being a little too careful.

For me it goes back to the bank
 
Also when on like 300 points , the bot is fletching but windertodt is on like 1-12% the bot keeps fletching and does not use the logs on fire i have missed out on a few creats due to this.

I suggest you make it so the bot just dumps everything in the fire so it can make the 500 pts mark

 

[party]

I'll check this next kill. Currently it's been getting 3/4 of the way through fletching an invent and then running back without putting any in the brazier and I've been manually finishing the fletching and lighting but I'll let it do it's own thing this next kill and let you know

Update: It's just running to the middle of the waiting room and not retreating to bank. Just did it at ~55% even though it has enough kindling in the inventory to reach 500 points.

This one's the genuine defect. When was the last time you restarted the bot? An updated went out in v1.1.1 that should have fixed that about 50 minutes ago. (Would require a Spectre restart)

When fletching the bot randomly runs down the side of the path.
Here logs of when it happened hope it helps.

Spoiler

00:13:32 [ INFO ] Eating food
00:13:33 [ INFO ] Chopping roots
00:13:33 [ INFO ] Moving camera towards brazier
00:13:33 [ INFO ] Chopping roots
00:13:34 [ INFO ] Moving camera towards brazier
00:13:34 [ INFO ] Chopping roots
00:13:45 [ INFO ] Eating food
00:13:47 [ INFO ] Chopping roots
00:13:48 [ INFO ] Eating food
00:13:49 [ INFO ] Chopping roots
00:13:54 [ INFO ] Moving camera towards brazier
00:13:54 [ INFO ] Chopping roots
00:13:54 [ INFO ] Eating food
00:13:56 [ INFO ] Chopping roots
00:14:06 [ INFO ] Eating food
00:14:07 [ INFO ] Chopping roots
00:14:36 [ INFO ] Eating food
00:14:39 [ INFO ] Chopping roots
00:14:39 [ INFO ] Retreating to bank
00:14:40 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:41 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:42 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:43 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:43 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:44 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:44 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:45 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:45 [ WARN ] RegionPath was null, reverting to BresenhamPath
00:14:46 [ WARN ] RegionPath was null, reverting to BresenhamPath

 

Yeah this has happened to me a few times , This is why i suggest a feature in which if you die it come back and loots and and the bot starts over again
 

For me it goes back to the bank
 
Also when on like 300 points , the bot is fletching but windertodt is on like 1-12% the bot keeps fletching and does not use the logs on fire i have missed out on a few creats due to this.

I suggest you make it so the bot just dumps everything in the fire so it can make the 500 pts mark

As I've mentioned in previous posts I'll be working on a solution to that tonight.

 

[oxygenthief]

This one's the genuine defect. When was the last time you restarted the bot? An updated went out in v1.1.1 that should have fixed that about 50 minutes ago. (Would require a Spectre restart)



As I've mentioned in previous posts I'll be working on a solution to that tonight.

That's running V1.1.1 reset it pretty much 45-50 minutes ago with a spectre restart.

 

[party]

That's running V1.1.1 reset it pretty much 45-50 minutes ago with a spectre restart.

feelsbadman.jpg

Alright I'll get some proper debugging done tonight. Appreciate you spending the time with this, though if you have any logs for the sessions (Help > View Logs in Spectre) then dump the files on a post, would be great help!

 

[oxygenthief]

feelsbadman.jpg

Alright I'll get some proper debugging done tonight. Appreciate you spending the time with this, though if you have any logs for the sessions (Help > View Logs in Spectre) then dump the files on a post, would be great help!

No problem, more than happy to help when I'll be using this as my first prime and to 99 fm
I'll chuck my log on after this game update so you can have a look at it.

 

[archnemesis]

Ok,

I have used the bot for 5 runs or so. What I tend to find is that it will decide, half way between fletching the logs, that it will not be able to get the required 500 points for the rewards and therefore proceed (without even offering the logs) to stand in the waiting area with 70% game energy left. I have continued playing after the bot has stopped the current game and have got up to 700 points, so it is possible. I think it may be forecasting that if it had to chop a full invy of logs again and then fletch all of them before offering them to the brazier, the time taken would be over the game time limit. However, I could be wrong as the bot has completed some games with no issue.

EDIT - I would like to add that I have plenty of food, ruling that out as being the cause of the bot stopping.

Secondly, in a hypothetical scenario when there is 10% energy left and the bot has finished offering the current load of kindling to the brazier, it will proceed to go and cut another full inventory of logs rather than cutting'x' amount of logs and leaving enough time to offer those collected logs to the brazier for maximum xp before the energy timer runs out.

Someone earlier in this thread mentioned something along the lines of the bot's efficiency and I believe that could be the case?

Otherwise, I get a feeling that the build of this bot is very robust and could lead to some nice xp gains if I could get it to run right!

 

[party]

Ok,

I have used the bot for 5 runs or so. What I tend to find is that it will decide, half way between fletching the logs, that it will not be able to get the required 500 points for the rewards and therefore proceed (without even offering the logs) to stand in the waiting area with 70% game energy left. I have continued playing after the bot has stopped the current game and have got up to 700 points, so it is possible. I think it may be calculating that if it had to chop a full invy of logs again and then fletch all of them before offering them to the brazier, the time taken would be over the game time limit. However, I could be wrong as the bot has completed some games with no issue.

Secondly, in a hypothetical scenario when there is 10% energy left and the bot has finished offering the current load of kindling to the brazier, it will proceed to go and cut another full inventory of logs rather than cutting'x' amount of logs and leaving enough time to offer those collected logs to the brazier for maximum xp before the energy timer runs out.

Someone earlier in this thread that mentioned something along the lines of the efficiency and I believe that could be the case?

Otherwise, I get a feeling that the build of this bot is very robust and could lead to some nice xp gains if I could get it to run right!

Yeah all of those points were addressed in the previous few comments (so some things aren't working like I intended them to). I'll try get through addressing them all tonight.

 

[archnemesis]

Yeah all of those points were addressed in the previous few comments (so some things aren't working like I intended them to). I'll try get through addressing them all tonight.

Thank you!