[BOT] NosBota by WarlossGreat

[Panda~]

Originally Posted by NosBusters

Thats not completelly true.
GMs have some more Options, how to look if you active.
They could also port you on different map, go to your map or send you a massage.

Mostly, they send you a message, when you don't Reply, they will teleport to your map, and afterwards they will teleport you on a complete different map.

yup, they check first if u reply then they teleport u into their 'office'

[WalrossGreat]

Bot should for the newest NosTale version right now. (This is not the update with new features)

[Panda~]

@

Item Usage every X Seconds only works one time, after that it won't be used anymore.

[WalrossGreat]

Can you record a video or something like this? For me it is working great.

[Scyra99]

Originally Posted by Panda~

@

Item Usage every X Seconds only works one time, after that it won't be used anymore.

try setting cooldown on +1 second extra

[Panda~]

working fine now, prolly PEBCAK issue.

[chun19990530]

The bot always stops walking somehow, without any reason. Wired

[WalrossGreat]

@
What do you mean by stop walking? Does it stops respecting waypoints? Or does it stuck in wall or maybe the whole bot stops walking and attacking?

[chun19990530]

Originally Posted by WalrossGreat

@
What do you mean by stop walking? Does it stops respecting waypoints? Or does it stuck in wall or maybe the whole bot stops walking and attacking?

it just stops going to next waypoint and stands there targeting itself.

[Panda~]

sometimes also if the bot want to attack a enemy behind a wall or waypoint behind a wall it stucks there.

[Scyra99]

i've only experianced this with item dropps

[WalrossGreat]

@ Yes, this is known issue, however it's more likely caused by NosTale walking algorithm, as the bot uses it. The not obvious solution for it is reducing the attacking radius while recording a route or so.
@
Strange. I have never experienced such issue. Does it happen on the end of route? Are there any specific logs? What is the setting to do after route? Go to first waypoint?

BTW. As I said that I will try to release the new func by the end of the weekend, however I meet strange issues as I updated from Windows 7 to Windows 10, to be more specific some mp3 files won't be played, and the NosTale window can't be flashed on the taskbar.

So far I did:
-Custom NosTale resolution embedded in bot (so you can set the fps limit and custom window size from the bot menu)
-Invitation request filter, so the bot will automatically deny party/friend requests etc after a delay
-Player control, so the bot will warn you when someone enter the map, or when other player is near you.

However as the features rely on the flashing and playing music functionality i think I need to dig more to try to fix those issues before releasing the features.

[chun19990530]

Originally Posted by WalrossGreat

@ Yes, this is known issue, however it's more likely caused by NosTale walking algorithm, as the bot uses it. The not obvious solution for it is reducing the attacking radius while recording a route or so.
@
Strange. I have never experienced such issue. Does it happen on the end of route? Are there any specific logs? What is the setting to do after route? Go to first waypoint?

BTW. As I said that I will try to release the new func by the end of the weekend, however I meet strange issues as I updated from Windows 7 to Windows 10, to be more specific some mp3 files won't be played, and the NosTale window can't be flashed on the taskbar.

So far I did:
-Custom NosTale resolution embedded in bot (so you can set the fps limit and custom window size from the bot menu)
-Invitation request filter, so the bot will automatically deny party/friend requests etc after a delay
-Player control, so the bot will warn you when someone enter the map, or when other player is near you.

However as the features rely on the flashing and playing music functionality i think I need to dig more to try to fix those issues before releasing the features.

I did reverse route for that. It stops in different point, just purely stopped to walk.

[GraczzPolski2]

Originally Posted by WalrossGreat

@ Yes, this is known issue, however it's more likely caused by NosTale walking algorithm, as the bot uses it. The not obvious solution for it is reducing the attacking radius while recording a route or so.
@
Strange. I have never experienced such issue. Does it happen on the end of route? Are there any specific logs? What is the setting to do after route? Go to first waypoint?

BTW. As I said that I will try to release the new func by the end of the weekend, however I meet strange issues as I updated from Windows 7 to Windows 10, to be more specific some mp3 files won't be played, and the NosTale window can't be flashed on the taskbar.

So far I did:
-Custom NosTale resolution embedded in bot (so you can set the fps limit and custom window size from the bot menu)
-Invitation request filter, so the bot will automatically deny party/friend requests etc after a delay
-Player control, so the bot will warn you when someone enter the map, or when other player is near you.

However as the features rely on the flashing and playing music functionality i think I need to dig more to try to fix those issues before releasing the features.

Can you add with these features autojoin instant battle?

[Scyra99]

cant wait for Player Control, thank you @ !
have you by chance looked at the return amulet bug? sonetimes the bot wont use the return amulet for some reason.