What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Exilebuddy (SotV) Release/Beta Revision Guide

Status
Not open for further replies.
its still saying "this version of the game is not supported for this build"

and a buddy of mine said i should use that and he gave me another key (cdpatcher)

either way it doesnt work even the legit way
 
SpaceNL said:
its still saying "this version of the game is not supported for this build"

and a buddy of mine said i should use that and he gave me another key (cdpatcher)

either way it doesnt work even the legit way
Click to expand...

Close everything down and click on "Packcheck" in the game folder. I know it's not the download link since I did it multiple times today, so it is probably your game being slightly out of date (plenty of hotfixes recently).
 
did that but still no result D:
i dont have a qlue what im doing wrong

does the screen size or options affect the bot?
 
SpaceNL said:
did that but still no result D:
i dont have a qlue what im doing wrong

does the screen size or options affect the bot?
Click to expand...

Yes but only in a minor way. It works better on 800x600 but can work well enough on any res. As for options turn graphics down and sound off to get higher TPS. I'm at 13-14 on max graphics and 15-16 on lowest without sound.
 
I just noticed the FPS thingy on the initial post. I've been wanting to talk about this since the beginning but I kept forgetting. Whenever I have the bot on the FPS gets really odd, yet whenever I stop it gets good.

Here's a picture showing it. Red is when the bot is running, Green is when I stop it.

View attachment 120381
 
Last edited:
SpaceNL please make a support thread with your issue, as this thread is not for support. Based on a few of your posts, you are using 3rd party software that is not supported here. You need to have and use a legit EB key from us to receive any further support.

tozededao said:
I just noticed the FPS thingy on the initial post. I've been wanting to talk about this since the beginning but I kept forgetting. Whenever I have the bot on the FPS gets really odd, yet whenever I stop it gets good.

Here's a picture showing it. Red is when the bot is running, Green is when I stop it.
Click to expand...

There is considerable overhead introduced to the game when the bot is used. A lot of memory has to be read each frame, since it works out of process, so between that and other logic that runs that takes up time, the game performance is affected. The memory reads have to be synchronized with the client though, since things move around in memory a lot in this game, so that's the main reason.
 
tozededao said:
I just noticed the FPS thingy on the initial post.
Click to expand...

The next beta version should run a little smoother, if it's even noticeable. Something changed in the client and that was causing the bot to throw a lot of exceptions which were internally being handled, but I'm pretty sure it affected performance some.
 
Is there a way to change the range of said abilities? For instance, I use different skills- one of them being EK. When setting the range from 45 to 20, it gets stuck on certain things (aka stairs, etc. etc.) If i set it to 10, it continually keeps switching targets from one to another (i assume the best target and the current target are conflicting?)
 
Nexic said:
Is there a way to change the range of said abilities? For instance, I use different skills- one of them being EK. When setting the range from 45 to 20, it gets stuck on certain things (aka stairs, etc. etc.) If i set it to 10, it continually keeps switching targets from one to another (i assume the best target and the current target are conflicting?)
Click to expand...

The current target is determined by the best target in Exile. The best target is determined by a weight system that uses distance and a few mods to try and not target things that shouldn't be attacked.

If you want a more "stable" target list, you'd have to change the target list to something that is more consistent. If you look at the "public Monster BestTarget" in Exile, you'll see where the current target comes from. The reason why targeting is re-evaluated, is because monsters move, de/buffs are applied/expire, and sometimes you want to kill something first pretty much all the time (Necromancers, for example). As a result, sometimes the target switches to something else, because that target would be the new best target.

Here's an example of something you could do to make the bot pick one target, and kill it, as long as it's in the target list.

Code: 
private int _bestTargetId;

 public Monster BestTarget
        {
            get
            {
                var targets = Targeting.Combat.Targets;

                // If we have an id stored, validate it first.
                if (_bestTargetId != 0)
                {
                    // The last target is now gone, so reset the id.
                    if (!targets.Any(t => t.Id == _bestTargetId))
                    {
                        _bestTargetId = 0;
                    }
                }

                // If no id is set, take the first target's id.
                if (_bestTargetId == 0)
                {
                    _bestTargetId = targets.FirstOrDefault().Id;
                }

                // Return the monster with the consistent id we have.
                return targets.FirstOrDefault(t => t.Id == _bestTargetId) as Monster;
}
}

I made sure to test it first, and it should solve your target switching issue, but doing something like that will come with its own side effects. There's a lot possible, but it really depends on your build and what kind of behavior you want out of the CR.
 
pushedx said:
The current target is determined by the best target in Exile. The best target is determined by a weight system that uses distance and a few mods to try and not target things that shouldn't be attacked.

If you want a more "stable" target list, you'd have to change the target list to something that is more consistent. If you look at the "public Monster BestTarget" in Exile, you'll see where the current target comes from. The reason why targeting is re-evaluated, is because monsters move, de/buffs are applied/expire, and sometimes you want to kill something first pretty much all the time (Necromancers, for example). As a result, sometimes the target switches to something else, because that target would be the new best target.

Here's an example of something you could do to make the bot pick one target, and kill it, as long as it's in the target list.

Code: 
private int _bestTargetId;

 public Monster BestTarget
        {
            get
            {
                var targets = Targeting.Combat.Targets;

                // If we have an id stored, validate it first.
                if (_bestTargetId != 0)
                {
                    // The last target is now gone, so reset the id.
                    if (!targets.Any(t => t.Id == _bestTargetId))
                    {
                        _bestTargetId = 0;
                    }
                }

                // If no id is set, take the first target's id.
                if (_bestTargetId == 0)
                {
                    _bestTargetId = targets.FirstOrDefault().Id;
                }

                // Return the monster with the consistent id we have.
                return targets.FirstOrDefault(t => t.Id == _bestTargetId) as Monster;
}
}

I made sure to test it first, and it should solve your target switching issue, but doing something like that will come with its own side effects. There's a lot possible, but it really depends on your build and what kind of behavior you want out of the CR.
Click to expand...

"You're like... a wizard" -Gilly
 
Casting and removing aura completely on the #767

Ignoring Shagreen Boots [623D] from loot targeting. (No Filter Match)
Ignoring Thief's Garb [3A1A] from loot targeting. (No Filter Match)
Ignoring Crypt Armour [2D3D] from loot targeting. (No Filter Match)
Input error casting Grace at {619, 1104}. MouseNotInRange
We need [Grace] but cannot cast it yet.
Cleared POI: Aura
POI set to Type: None, Location: {0, 0}, Distance: 0, Name: None, Hash Code: 888371759
We need [Grace] but cannot cast it yet.
POI set to Type: Explore, Location: {634, 1467}, Distance: 351, Name: Explore, Hash Code: -223954122
MoveToCoroutine moving to {634, 1467}. Reason: Exploration
We need [Grace] but cannot cast it yet.
Pressing bound movement button.
We need [Grace] but cannot cast it yet.
We need [Grace] but cannot cast it yet.
We need [Grace] but cannot cast it yet.
We need [Grace] but cannot cast it yet.
We need [Grace] and can cast it.
POI set to Type: Aura, Location: {617, 1116}, Distance: 0, Name: Aura, Hash Code: -2070255165
[HandleAuras] We do not have [Grace] and will try to cast it.
Input error casting Grace at {617, 1116}. MouseNotInRange
Cleared POI: Aura
POI set to Type: None, Location: {0, 0}, Distance: 0, Name: None, Hash Code: -961314348
POI set to Type: Explore, Location: {634, 1467}, Distance: 351, Name: Explore, Hash Code: -324825160
MoveToCoroutine moving to {634, 1467}. Reason: Exploration
We need [Grace] but cannot cast it yet.
Pressing bound movement button.
We need [Grace] but cannot cast it yet.
We need [Grace] but cannot cast it yet.
We need [Grace] but cannot cast it yet.
Navigation path index moved to 1
We need [Grace] and can cast it.
POI set to Type: Aura, Location: {617, 1128}, Distance: 0, Name: Aura, Hash Code: -1388005033
[HandleAuras] We do not have [Grace] and will try to cast it.
Input error casting Grace at {617, 1128}. MouseNotInRange
Ignoring Fencer Helm [29F0] from loot targeting. (No Filter Match)
Ignoring Cutthroat's Garb [46F8] from loot targeting. (No Filter Match)
Ignoring Gemstone Sword [3626] from loot targeting. (No Filter Match)
Input error casting Grace at {617, 1128}. MouseNotInRange
Stopping the bot. Reason: UI Button Pressed
Removed hook [BotBehavior] fd036e2a-e4e8-4a98-b769-a9aa99280276
Cleared POI: Aura
POI set to Type: None, Location: {0, 0}, Distance: 0, Name: None, Hash Code: -1602088205
Removing memory patches.
 
Aura logic will be adjusted for 1.1.1.1. It'll be broken for a few versions until the issue is solved.
 
Last edited:
Latest beta (768) doesn't work for the current version of the game (1.1.1).
 
krone6 said:
Latest beta (768) doesn't work for the current version of the game (1.1.1).
Click to expand...


768 Is not what you download when you click on the download beta link, Its 767 (wich is not supported with 1.1.1)

Not sure why 768 is not available to download.

Devs ?
 
Thecamel said:
768 Is not what you download when you click on the download beta link, Its 767 (wich is not supported with 1.1.1)

Not sure why 768 is not available to download.

Devs ?
Click to expand...

No wonder. I figured with an update to the patch notes they'd update the download link as well.
(Hopes the devs are still awake to fix this problem :))
 
Last edited:
Status
Not open for further replies.
Back
Top