ExilebuddyBeta Forsaken Masters Guide

Ok dude, looks like you copied it to an old folder.
Download a new fresh copy here
https://www.thebuddyforum.com/exilebuddy-forum/174957-exilebuddybeta-forsaken-masters-guide.html
Extract it to a clean, new folder and run it. Should work.

 

I used the automatic update but ill test that out thanks alot for help mate!

 

Jesus what happened to the old style bot?? I think its time for me to sit and wait for the full update lol this is confusing and extremely rudimentary.

 

a new PoE patch came out today Bot no longer working

 

Beta #881 was just built. This version adds some configurable settings to BasicGrindBot to make non-town based looping possible.

To loop an area, you basically need to select an area that isn't bordered by a town or a blocked area transition, and change the BasicGrindBot settings (Settings tab in the GUI). You need to travel to the zone yourself, and start the bot once there still.

For example, to loop Ledge:
GrindZoneDifficulty: your difficulty
GrindZoneName: The Ledge
FullExplore: unchecked
StopExplorationAfter: Something low, like 25
IgnoreStartingLocationAreaTransition: checked
PrimaryExplorationCompleteBehavior: AreaTransition
SecondaryExplorationCompleteBehavior: PortalToTown

That will pretty much make it loop area transition to area transition. The limitations of not being able to use towns is just temporarily until town stuff is added this weekend. Please remember this stuff is still Beta, and with the new 1.2.1 patch, some things might have broken and have gone unnoticed.

There is no quest logic or handling of interact items, so the bot will not do the Mud Flats quest for you. It does still use the Area Pather from before, so it will make its way though areas that you don't have a waypoint for (it will not tag a waypoint yet, no logic). If you start the bot in The Lower Prison with settings similar to above, except you grind The Upper Prison, it will (should) make its way to Brutus. As long as your combat range is not too low, the bot will also fight Brutus using its simple face tanking logic. It will, however, go to town afterwards, and stop.

 

I noticed that the bot takes forever to get started in an area now as well as when it goes to loop it has to load the navmesh of the area its not going to be clearing even though its not going to stay there. During this time you can be attacked and the bot doesnt do anything about it. Kinda dangerous!

 

Longer pathfinding generation is an unfortunate result of the larger or more complex terrain changes made in 1.2 for Forsaken Master stuff spawning in tilesets.

Upon spawning in an area you have the 20s grace period, and as long as you're not running on a slower PC, it should be able to finish. Some extra safe guards will be put into place to help avoid cases of longer loading and the bot just sitting there if a mob is close by, but as with the game itself, slow loading an area can lead to your death by design.

 

Trying it now. Why "StopExplorationAfter: Something low, like 25" ?
Still not using flasks like quicksilver correct?

yikes, got this after 2 transitions when trying the third:

Code:

[Logic] Now moving towards the monster True because [canSee: True][pathDistance: 50.81077][blockedByDoor: False]
[HandleLeavingAreaThroughAreaTransition] HighlightObject failed for the area transition.
[HandleBehaviorFail] The second behavior has failed. Now logging out.
[LogoutToCharacterSelection] Now logging out to Character Selection screen.
<log4net.Error>Exception during StringFormat: Index (zero based) must be greater than or equal to zero and less than the size of the argument list. <format>[GrindTask] EscapeState.LogoutToCharacterSelection returned {0}. Now stopping the bot.</format><args>{}</args></log4net.Error>
[Stop] Now requesting the BotThread to stop.
[BasicGrindBot] OnStop
[AutoFlask] Stop
[ExampleRoutine] Stop

and more....can't really do more than 2 loops.

Code:

[GetPathfindingData] Now creating the pathfinding data.
[Tick] Exception during execution:System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 2128
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.ReadBytes(IntPtr addr, Int32 count)
   at Loki.Game.LokiPoe.LocalData.()
   at Loki.Game.Utilities.PerCachedValue`1.get_Value()
   at Loki.Game.LokiPoe.LocalData.
()
   at Loki.Game.LokiPoe.LocalData.
()
   at Loki.Game.LokiPoe.TerrainData.
()
   at Loki.Game.LokiPoe.TerrainData.
(Int32 , Boolean , Byte )
   at Loki.Game.LokiPoe.TerrainData..()
   at Loki.Game.Utilities.PerCachedValue`1.get_Value()
   at Loki.Game.LokiPoe.TerrainData.GetPathfindingData(Int32 layer, Boolean includeBlockages)
   at Loki.Bot.Pathfinding.ExilePather.Reload(Boolean force)
   at Loki.Bot.Logic.Bots.BasicGrindBot.BasicGrindBot.Tick()
   at Loki.Bot.BotManager.(IBot )

 

it seems like im getting alot of lag now with the bot. constant jerks and jumps. I tried to set it as a higher priority on my task manager to see if that made a difference but it doesnt.

also it skips opening strong boxes

 

Is the bot ver.881 working with current client?

I still got information about the client version is unsupported.

 

And that is exactly what it means, you got to wait till the bot is updated.

 

Does the loop work for you guys?

Edit: I think we are down again cause POE patch....better be patient for a while

 

Please make a support thread with a full log or at least tell me the area you were in and which transition.

Quicksilver on movement is not back in, correct.

As for the memory exception, there's a few cases that need to be handled where the bot is logged out, but other normal logic still runs, because it's running a coroutine. The bot should recover from that, but the bigger issue is the area transition failing (which can happen in this game). The logic is a little more over-protective right now to make sure it doesn't do anything over and over and potentially trigger any bot-like detection.

The reason for the Ledge and setting a low %, is because if you start at the waypoint and explore one direction, the actual % explored can be anywhere from 30-60%. If by the time you reach the area transition, the exploration threshold is not reached, the bot will simply walk back though to the other side. I have done a lot of loop testing though, so the feature did work for me.

 

Thanks.
Pushedx are we down cause of patch?

 

Nope, all working.

 

Only Beta is updated and working currently, as there is no Release build post-1.2. After Beta gets some more basic features, and all the after effects of the 1.2 patch seemed to be smoothed out, a normal Release build will be made from the latest Beta.

 

With new version character instantly returns to town, I am not too familiar with exile bot, must I change settings? Thanks for any help!

 

Yes, before you start the bot, you need to change the BasicGrindBot settings (Settings -> BasicGrindBot) to the area you are currently grinding. By default, its set to something like Mud Flats, I think, and if town stuff was in, it'd travel to the grind zone via town.

 

Hi

if I set PrimaryexplorationCompletionBehavior to area transition, will it actually change level? as an exemple if the same map have multiple level will it do level 1 then 2 ans so on ?

thanks

 

much thanks