What's new
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Nesox seriously, still no telport stuck fix ?

Status
Not open for further replies.

Bertrand

Active Member
Joined
Aug 8, 2012
Messages
1,249
Reaction score
9
I know i am getting boring and i know i can earn an infringement for calling out on developers like this, but what frustrates me is that there is still no reply in the old thread regarding this issue, and even more so that this issue was fixed in a version prior to 1.5 release. There is a plugin that reloads profile based on gold pickup but that can get you in so much trouble if current profile is cydea or azmodan or a previous profile (gangnam style, where no check for cydea is made in arreat core profile) that you can be recreating game every 5 secs...

So once again, humbly, whatever you did in patch prior to 1.5 db version that fixed that tp stuck implement it again, it hurts a lot watching your bot sitting and trying to tp until game disconnects (30 mins or more) and after that you get to reload the current profile...
 
damn u wait 30min? i wait few mins peace
never getting stuck again
but yeah they should hire a person to code
 
Bertrand - AFIK u can setup start profile in this gold pickup plugin so it wont recreate curret profile but the one u config (example: _start_here)
 
No solokazama, there are other issues with that, i.e. if i have 6 folders of different profiles, and i want 6 bots to load each folder for different type of profiles/paths. Now the plugin can be set to only one profile to start, that means whenever the bot get stuck it will load one and one only profile. As soon as all of my bots experience a stuck they will load the profiles from only one folder. Only way around this is for the plugin to read the first profile loaded by db, i mean at least can we get an answer from nesox on how to do that? What pisses me off is the fact that this issue was fixed prior 1.5 and the same issue is recurring again. I understand if you don't have an idea how to fix this and all, but it was solved, just needs to be implemented again...
 
Last edited:
its fixed on beta build


try it

closed
 
Status
Not open for further replies.
Back
Top