Fatebot attacking boss despite 5% Minimum Setting

[scorpinot]

View attachment 3692 2015-08-23 20.01.txt
Fate: bubble trouble
Mob: Bubbly Bernie
Area: Horizon
Level requirements on: lv0, +5 current level
Engage Boss Fates: 5%

Noticed the char attempting to solo this boss after a few deaths.

 

[scorpinot]

Same area, different problem:

[05:01:51.712 V] [Poi.Clear] Reason: Targeted unit is dead, clearing Poi and carrying on!
[05:01:51.779 D] [POI Set] Type: Kill, Name: Doomed Gigantoad, ObjectId: 40054A31, NpcId: 865, Location: <154.8638, 17.53689, -19.39423>
[05:01:51.846 D] Requesting path on 140 from <139.7253, 57.12996, 5.857985> to <154.8638, 17.53689, -19.39423>
[05:01:51.917 D] Generated path to <154.8638, 17.53689, -19.39423> in 00:00:00.0707408 ms
[05:01:53.961 N] [Ultima] Resting...
[05:02:12.043 D] Moving to next hop: <92.68665, 56.21912, -29.55578> (Kill Target) D: 1.954314
[05:02:12.244 D] Moving to next hop: <92.29829, 56.12321, -32.33616> (Kill Target) D: 3.517222
[05:02:12.710 D] Moving to next hop: <92.23725, 56.06081, -32.93808> (Kill Target) D: 1.313128
[05:02:12.843 D] Moving to next hop: <92.44958, 55.83264, -35.44931> (Kill Target) D: 3.030275
[05:02:13.244 D] Moving to next hop: <92.4749, 55.60654, -37.4992> (Kill Target) D: 2.680849
[05:02:13.510 D] Requesting path on 140 from <92.4537, 55.5877, -36.42564> to <153.5429, 17.53689, 
...
-12.89392>
[05:02:51.707 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0644852 ms
[05:02:51.709 D] Navigation reached current destination. Within 30.84834
[05:02:51.776 D] Requesting path on 140 from <165.7457, 47.10412, -16.41587> to <157.7629, 17.53689, -12.89392>
[05:02:51.843 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0666588 ms
[05:02:51.974 D] Navigation reached current destination. Within 30.87164
[05:02:52.040 D] Requesting path on 140 from <165.8587, 47.1822, -16.52662> to <157.7629, 17.53689, -12.89392>
[05:02:52.107 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0663568 ms
[05:02:52.110 D] Navigation reached current destination. Within 31.02394
[05:02:52.176 D] Requesting path on 140 from <166.4719, 47.23936, -16.00495> to <157.7629, 17.53689, -12.89392>
[05:02:52.243 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0671673 ms
[05:02:52.376 D] Navigation reached current destination. Within 31.11208
[05:02:52.444 D] Requesting path on 140 from <166.3414, 47.12167, -15.79282> to <157.7629, 17.53689, -12.89392>
[05:02:52.510 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0661749 ms
[05:02:52.575 D] Navigation reached current destination. Within 30.60419
[05:02:52.643 D] Requesting path on 140 from <165.2332, 46.85997, -16.25039> to <157.7629, 17.53689, -12.89392>
[05:02:52.711 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0680403 ms
[05:02:52.908 D] Targeting Doomed Gigantoad 0x40054A31 0xFD3A340

Char ran to a full HP boss and targeted it then did nothing. Level sync option for the fate was flashing (sync not active).

 

[ZeeZee]

View attachment 185523
Fate: bubble trouble
Mob: Bubbly Bernie
Area: Horizon
Level requirements on: lv0, +5 current level
Engage Boss Fates: 5%

Noticed the char attempting to solo this boss after a few deaths.

Looks like someone started the FATE then abandoned:
In your log file:
[04:03:06.455 N] Current fate set to 37269DA0 Name:Bubble Trouble Id:353 Icon:Boss ObjectId:E0000000 Location:<-282.1446, 14.97494, -273.5949> TimeLeft:00:11:29.5446030 Radius:40 Progress:5 Level:13 MaxLevel:18 Status:ACTIVE

So as far as the bot's concerned it's met the min requirement of 5%

 

[scorpinot]

Same area, different problem:

[05:01:51.712 V] [Poi.Clear] Reason: Targeted unit is dead, clearing Poi and carrying on!
[05:01:51.779 D] [POI Set] Type: Kill, Name: Doomed Gigantoad, ObjectId: 40054A31, NpcId: 865, Location: <154.8638, 17.53689, -19.39423>
[05:01:51.846 D] Requesting path on 140 from <139.7253, 57.12996, 5.857985> to <154.8638, 17.53689, -19.39423>
[05:01:51.917 D] Generated path to <154.8638, 17.53689, -19.39423> in 00:00:00.0707408 ms
[05:01:53.961 N] [Ultima] Resting...
[05:02:12.043 D] Moving to next hop: <92.68665, 56.21912, -29.55578> (Kill Target) D: 1.954314
[05:02:12.244 D] Moving to next hop: <92.29829, 56.12321, -32.33616> (Kill Target) D: 3.517222
[05:02:12.710 D] Moving to next hop: <92.23725, 56.06081, -32.93808> (Kill Target) D: 1.313128
[05:02:12.843 D] Moving to next hop: <92.44958, 55.83264, -35.44931> (Kill Target) D: 3.030275
[05:02:13.244 D] Moving to next hop: <92.4749, 55.60654, -37.4992> (Kill Target) D: 2.680849
[05:02:13.510 D] Requesting path on 140 from <92.4537, 55.5877, -36.42564> to <153.5429, 17.53689, 
...
-12.89392>
[05:02:51.707 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0644852 ms
[05:02:51.709 D] Navigation reached current destination. Within 30.84834
[05:02:51.776 D] Requesting path on 140 from <165.7457, 47.10412, -16.41587> to <157.7629, 17.53689, -12.89392>
[05:02:51.843 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0666588 ms
[05:02:51.974 D] Navigation reached current destination. Within 30.87164
[05:02:52.040 D] Requesting path on 140 from <165.8587, 47.1822, -16.52662> to <157.7629, 17.53689, -12.89392>
[05:02:52.107 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0663568 ms
[05:02:52.110 D] Navigation reached current destination. Within 31.02394
[05:02:52.176 D] Requesting path on 140 from <166.4719, 47.23936, -16.00495> to <157.7629, 17.53689, -12.89392>
[05:02:52.243 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0671673 ms
[05:02:52.376 D] Navigation reached current destination. Within 31.11208
[05:02:52.444 D] Requesting path on 140 from <166.3414, 47.12167, -15.79282> to <157.7629, 17.53689, -12.89392>
[05:02:52.510 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0661749 ms
[05:02:52.575 D] Navigation reached current destination. Within 30.60419
[05:02:52.643 D] Requesting path on 140 from <165.2332, 46.85997, -16.25039> to <157.7629, 17.53689, -12.89392>
[05:02:52.711 D] Generated path to <157.7629, 17.53689, -12.89392> in 00:00:00.0680403 ms
[05:02:52.908 D] Targeting Doomed Gigantoad 0x40054A31 0xFD3A340

Char ran to a full HP boss and targeted it then did nothing. Level sync option for the fate was flashing (sync not active).

Blacklisting this fate (Doomed) doesn't prevent him from being targeted either and when others lower his HP the char still doesn't attack. This fate always results in a crash after it's finished due to the surrounding terrain and too many pathing requests.