Ok,
So I made that new installation.. here is versions of the first and the second (latest) installations:
/*Installation one*/
DB: v1.0.994.250
GilesMonsterPriorityChanger 1.5.6
GilerTrinity 1.4.9.1
GIlesWorldObjectHandler 1.7
RadsProfileManager 0.9.0
/*Installatino Two*/
DB: v1.0.994.250
GilesMonsterPriorityChanger 1.5.6
GilerTrinity 1.5.2
GIlesWorldObjectHandler 1.7
RadsProfileManager 0.9.0
So the only difference seemed to be GilesTrinity. (I didn't check all the plugins .cs files with "diff" program, but I can esure that tomorrow moring)
So There was still some stuckerings, but I thinkg Giles Unstucker was/would have triggered for all of those.
When I tested my latest installation (the new one) with that "GilesTirinity 1.4.9.1."(old) everyting seemed to (also) work ok
Ok, so the images:
"stucked_two_times_this_place.png" - actually it got stucked to that place to 3 times, it got out there with little help.
All other places seem also similar there is always "U" shaped place where the character is stucked if this helps Giles or DB anyhow.
"stucked_no_new _log_entries.png" example shows place where bot was stucked longer than 20secs, without any log entries.
Here is my all DB logs from this new installation:
https://www.dropbox.com/s/k8ql2us41oj9cpw/Logs.7z
latest log entries contain information also from "Trinity 1.4.9.1"
"stuckerin_with_act3_also.png" - In this place bot did get "stuck" with 2 times / 2 tries (100%)
Didn't wait for Trinity unstucker. Bot tried to get to that door below, after little help bot continued.
There was also few non "U" shaped places where bot did get stucked, without any reason (logical), check the images.
So actual conclusion for this, because "Trinity 1.4.9.1" and "Trinity 1.5.2" provided good experience with CLEAN new installation of DB I think that problems were caused by DB update somehow..
(Cannot be 100% sure for that, but it seems to be so, because "Trinity 1.4.9.1" worked fine with new installtion, and I didnt got lot of those "hops. (true) -messages")
*edit*
To make sure for all "When I tested my latest installation (the new one) with that "GilesTirinity 1.4.9.1."(old) everyting seemed to (also) work ok",
Tests with latest versions were good and test with latest versions with/using "GilesTrinity 1.4.9.1" were also good.
"latest log entries contain information also from "Trinity 1.4.9.1""; Last entries last or second last are made with this version, others are made with lates version "1.5.2"
*Edit2*
Finally now.. bot is again stuck with "Crypt of the ancients" in very same place that my previous images shows.. and Giles Unstucker did trigger... but I think when bot again goes to that location it will get stuck...