Ah yeah I saw that. I just felt bad for Sychotix, everyone was blaming him page after page about it, but not understanding the full issue with it. Didn't mean to come off as an ass hat if that's how it seemed.@ NoWayLol there is a work around for it so it isn't a town run to act 1 just to another act it was posted a few pages back and i understand it is a trinity/db problem not in this script
Yeah I was talking about spire 1, It must be something on my end it seems.
Other than that though iv'e run 4 act 4 bounties and claimed the caches flawlessly
Loaded profile Act 4 - Loader
[BountyProfile] Refreshing Cache!
Act 4 Bounties
Loaded profile Kill aspect of sin
Using Waypoint Waypoint-20781 Number:45
========== Grid segmentation resetting!!! ============
Found named but still not done, clearing some more.
[BountyProfile] Refreshing Cache!
========== Grid segmentation resetting!!! ============
========== Grid segmentation resetting!!! ============
========== Grid segmentation resetting!!! ============
========== Grid segmentation resetting!!! ============
[Trinity] Fully explored area! Tag Finished.
[Trinity] TrinityTownPortal started - clearing area, waitTime=2500, startHealth=378714
[Trinity] Town Portal timer finished
========== Grid segmentation resetting!!! ============
Loaded profile Act 4 - Loader
[BountyProfile] Refreshing Cache!
Act 4 Bounties
Loaded profile Kill aspect of sin
Using Waypoint Waypoint-22629 Number:45
========== Grid segmentation resetting!!! ============
Found named but still not done, clearing some more.
[BountyProfile] Refreshing Cache!
========== Grid segmentation resetting!!! ============
========== Grid segmentation resetting!!! ============
========== Grid segmentation resetting!!! ============
========== Grid segmentation resetting!!! ============
[Trinity] Fully explored area! Tag Finished.
[Trinity] TrinityTownPortal started - clearing area, waitTime=-1, startHealth=378714
[Trinity] Town Portal timer finished
Exception when terminating bot thread. System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
at System.IO.Path.GetDirectoryName(String path)
at Zeta.Bot.Profile.Common.LoadProfileTag.get_ProfileDirectory()
at Zeta.Bot.Profile.Common.LoadProfileTag.(Object )
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Common.HookExecutor.Run(Object context)
at Zeta.TreeSharp.Action.RunAction(Object context)
at Zeta.TreeSharp.Action..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.TreeSharp.PrioritySelector..()
at Zeta.TreeSharp.Composite.Tick(Object context)
at Zeta.Bot.BotMain.()
Anyone having 'path too long' errors:
That is an OS issue, the directory your DB (or the profile you are accessing) is in exceeds the built in character limit. Move it to a directory closer to root and you should be fine.
Please don't post your logs like that and read first post on this exact same page...
It does have something to do with the plugin, Sychotix has a fix but it's not on the SVN yet.Are you sure this isn't a bug with the LoadProfile tag? This error only seems to show up for me after it does 4-5 full bounty clears. This makes me think there's something weird going on when loading profiles and returning to a "root" profile.
this was the post right after i did what you did and the first post on page 29 is what he is refering too
I have no idea what is causing that "Path Too Long" error unless it is on the user's side. If I encounter it, I will try running Visual Studio's debugger to see where it occurs.
System.IO.FileNotFoundException: Path to profile element is not valid; file not found
File name: 'C:\D3 Bot\Scripts\db-bounty-profiles\Act4 by Zimble\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\..\.\Act4\../profile.xml'
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)
See you can use the quote optionAnyway i don't get what you trying to say
After 3-4 successful runs on ACT4 im getting "Path too long":
<LoadProfile file="profile.xml" />
<LoadProfile file="369900.xml" />
Think I found the issue with the to long error. It's stacking back because it every time it changes between Profile.xml and a Sub-Profile, it keeps that in memory. Something like Bounties/.../profile.xml/act4/subprofile.xml/.../profile.xml ect over and over.
All I think you need to do, is move the profile.xml into the same folder as all the sub scripts. Then it doesn't have to keep changing folders, everything is in the same place, and no more stacking.
Change all the Sub Profiles to this:
And for the main profile, you need to change all these as so: