I think that not any profile is flawless,basically no stuck,then think about what you need,for high XP? or a long route to farm more and more loots. anyway,thank your work!
Will this be working for 1.0.7? There is a change in the way resume game functions from my understanding, that may adulterate profiles operating under that prereq
Haha too true, there is currently an issue with sometimes getting lost in keeps 3, but for the most part, it works pretty well, the new TrinityExplore is great for pathing more directly to exits with much less backtracking, I saw a 15+ percent increase in efficiency when switching to TrinityExplore, even with the occasional hiccups. If you'd like to try it out, it's available in the dev branch of the git repository at this link. Just chose the single xml file, the randomized beta isn't really working so well at the moment. Yeah the new change doesn't hurt too much. There will be a portal to your most recent checkpoint when starting a new game. All that I'll have to change is to make it take that portal if it is there. Even without the change the profile should still work, it will simply run core the other way and TP out
Everything works now with the new patch... Tested even from v2 still works fine. also picks up essences?? Thought it did
There is a common stuck (v 7 )somewhere to the end of arreat crater level 2. I am guessing it has to do with 1.0.7, otherwise it is working beautifully as usual.
What changes can we do if we want essence to get picked up from this version7 ? I am running a wizard at the moment and once I change to archon mode It changes back to normal rightaway. Is there a setting for this?
Hello, I have this error constantly: [14:21:28.348 N] Loaded profile YAR Profile Kickstart: TinnkaizerRelogLoader.xml [14:21:28.348 N] Game joined, Resetting profile caches. [14:21:28.373 N] ProfileOrderManager.OnGameJoined, Reloading profile. Can you give me some advice?
YAR won't work now anyway without the d3starter.. unless you have isboxer to start it multiple times or you have different instances of d3 obviously
1.0.7 now forces everyone to start in town. No more starting at checkpoints. Profiles will have to be updated, though I thought Tinn's profile handled this already.
Hmm i have similar problem to other people here - 2 of my bots are running fine (full fresh instal) but 3rd DB crashes b4 it logs in :/ im using 3 different instances of d3. ive tried deleting some JAR folder in appData or w/e + ive copied my DB folder and tried to run my 3rd bot with this new folder but same shit happens any suggestion what to do ? im not using jar kickstarter and d3starter. just tinkazier and jar + some random plugins. plz help me im running out of ideas what to do next edit: ups wrong thread sry
Don't work now ... 19:33:54.125 N] Failed to load profile: Element TrinityMoveTo is not supported. Please check your XML and try again. (<TrinityMoveTo questId="101758" stepId="1" x="1140.686" y="732.1945" z="0.1000002" pathPrecision="10" navigation="True" unsafeRandomDistance="15" name="Arreat Core-01" />) Line 11
Ok for reference: clean instal of newest DB + newest trinity + experimental JAR (clones from original d3) + tinnkaizer 0.7 and everything works just fine Is 0.8 out already ? how is it going ?
Well ive noticed some problems with bot - quite a lot of backtracking and sometimes bot just stops and do nothing. from time to time he starts at town and do nothing
Make sure you have trinity loaded in plugins, this usually happens because trinity failed to load. This can also happen when trying to upgrade folder. Make fresh DB 300 install, fresh trinity, make sure you use new trinity routine. You will be working 100%
Just to make sure everyone is up to date, D3 1.07 changed it so that you always start the game in town, but there will be a TP to your last checkpoint. v0.8 now accounts for this TP, see link below. v0.8 has a small bug currently where in keeps 3 it can get lost around 15% of the time. Many times, Trinity unstucker will set it straight, but sometimes not. This is the main reason that v0.8 is not released yet. The link below also has a folder for v0.8 random beta. This is super buggy right now, but if you'd like to try it out, feel free. You can try v0.8 here, it is still BETA, however: https://www.assembla.com/code/tinnkaizer/git/nodes/development
