Post by tosin on Feb 25, 2023 12:55:26 GMT
Hello
I have issue with targeting.
I play on BlazeraOT. It have creatures with levels and they will spawns with skulls.
I turn on cavebot and targeting.
Once in a while the targeting stops targeting the creatures. Targeting is ON but character just following the waypoints on cavebot and wont stop to kill creatures. After running a while the targetinf starts work correctly.
What have I done so far:
Turend targeting on/off - did not work
Turend cavebot on/off - did not work
Started fresh targeting script just 1 characther there "others" - did not work
Changed hunting spot with another creatures - did not work
Had a script:
auto 100 | dontlist | foreach 'newmessages' $msg if [$msg.content ? 'minekoju'] {stopattack | settargeting off | gotolabel HOME}
changed it to:
auto 2000 | dontlist | foreach 'newmessages' $msg if [$msg.content ? 'minekoju'] {stopattack | settargeting off | gotolabel HOME} - did not work
What I have noticed:
Creature levels messing things up when I use creature names on targeting.
Example:
I make Targeting character "Cyclops Drone" but in game thy have other names as "Cyclops Drone[L.51]" so it wont targeti it. The fix here is simple I use "!togglemonsterlevels off" and now I see normal creature names.
Creature skulls is not the reason. As I had one place where this happend I was running around and noticed that targeting was starting to work after some creatures was not on my screen. I was running around and when targeting started I killed the creature that targeting was attacking. Finaly I was left with one creature. He had no skull. Targeting was not attacking it. All the time when this creature was on my screen the targeting ignored all the other creatures aswell.
After I run PZ, relog and run back there than targeting was working correctly on this last creature aswell.
I had my PC running like more than a week. I did restart it today. Now the thing is happening not so often but still sometimes.
Is there anybody who have been facing this kind of problem aswell?
Is it possible that this problem is afected by my PC?
I have issue with targeting.
I play on BlazeraOT. It have creatures with levels and they will spawns with skulls.
I turn on cavebot and targeting.
Once in a while the targeting stops targeting the creatures. Targeting is ON but character just following the waypoints on cavebot and wont stop to kill creatures. After running a while the targetinf starts work correctly.
What have I done so far:
Turend targeting on/off - did not work
Turend cavebot on/off - did not work
Started fresh targeting script just 1 characther there "others" - did not work
Changed hunting spot with another creatures - did not work
Had a script:
auto 100 | dontlist | foreach 'newmessages' $msg if [$msg.content ? 'minekoju'] {stopattack | settargeting off | gotolabel HOME}
changed it to:
auto 2000 | dontlist | foreach 'newmessages' $msg if [$msg.content ? 'minekoju'] {stopattack | settargeting off | gotolabel HOME} - did not work
What I have noticed:
Creature levels messing things up when I use creature names on targeting.
Example:
I make Targeting character "Cyclops Drone" but in game thy have other names as "Cyclops Drone[L.51]" so it wont targeti it. The fix here is simple I use "!togglemonsterlevels off" and now I see normal creature names.
Creature skulls is not the reason. As I had one place where this happend I was running around and noticed that targeting was starting to work after some creatures was not on my screen. I was running around and when targeting started I killed the creature that targeting was attacking. Finaly I was left with one creature. He had no skull. Targeting was not attacking it. All the time when this creature was on my screen the targeting ignored all the other creatures aswell.
After I run PZ, relog and run back there than targeting was working correctly on this last creature aswell.
I had my PC running like more than a week. I did restart it today. Now the thing is happening not so often but still sometimes.
Is there anybody who have been facing this kind of problem aswell?
Is it possible that this problem is afected by my PC?