C2's Trick or Treater 2.3

[Venosa]

I did download the file as mentioned, it is the only way I download them, never copy and paste. I will try the mentioned troubleshooting steps above, and also try a different runebook. Thanks for the fast responses and help guys. Truly appreciated. Back to some more testing.

[Venosa]

Ugh, I have had no luck with this thing. The recall test sub didn't work for me. it seems like what happens, the moment I get teleported it doesn't recognize I have moved cords and doesn't even attempt to recall. *shrugs* I even tested different characters.

[_C2_]

Ugh, I have had no luck with this thing. The recall test sub didn't work for me. it seems like what happens, the moment I get teleported it doesn't recognize I have moved cords and doesn't even attempt to recall. *shrugs* I even tested different characters.

Sounds like it cannot find the runebook.  That is why it is just sitting there after a tele.  The recall subs don't see it.  Can you buy or make a brand new one and put the runes in it?  Also double chest to make sure nothing else has Halloween in its name.  I have never met someone with these issues.  You have something bugged for sure. 

[brianfreud]

Thanks for this.    Setup was a breeze, and it's been working for 15 min like a champ.  I commented out the teleporter delay, as I'm not using one, but I still see a few seconds extra delay doing nothing after it pathfinds and arrives at the secure.  Otherwise, I doubt this could be any smoother or faster.

Brian

[unisharp]

Script has been working perfectly except for one thing...  Every hour or two, my client will close and the script will stop.  Every time it does this, my character is standing at my door.

Anything wrong with my return code?

Code: [Select]

if #CHARPOSY >= %pathfindrangestart && #CHARPOSY <= %pathfindrangewindow
   {
   repeat
   event pathfind 2037 1271  ;x/y of first location (not recall point)
   until #charposx = 2037 && #charposy = 1271

  ;*** Add this in for doors!
   finditem FJC_HJC g_3
   set #lobjectid #findid
   event macro 17
   wait 10
   

 ;  wait 40 ; because of teleporter- take out if not using teleporter
   ;do not edit below-this is your original starting point
   repeat
   event pathfind %movedx %movedy
   until #charposx = %movedx && #charposy = %movedy
   }

[Venosa]

I think my luck is that I ping horribly to ATL, because I have tested many runebooks. I have had that problem in the past where certain scripts just don't work well to shards I ping very high to.

[_C2_]

I think my luck is that I ping horribly to ATL, because I have tested many runebooks. I have had that problem in the past where certain scripts just don't work well to shards I ping very high to.

yes,  it is the recall sub stopping the script when it cannot find the book.  i saw it happen to me two times last night on a lag spikes on an older computer.  I really cannot edit TMs recall code that is in my script.  i could possibly just make a default rune as part of the script for returning to the house.  since all the recall code is not mine... it limits me but it is def that section because i finally witnessed it after days and days of use.

[_C2_]

Script has been working perfectly except for one thing...  Every hour or two, my client will close and the script will stop.  Every time it does this, my character is standing at my door.

Anything wrong with my return code?

Code: [Select]

if #CHARPOSY >= %pathfindrangestart && #CHARPOSY <= %pathfindrangewindow
   {
   repeat
   event pathfind 2037 1271  ;x/y of first location (not recall point)
   until #charposx = 2037 && #charposy = 1271

  ;*** Add this in for doors!
   finditem FJC_HJC g_3
   set #lobjectid #findid
   event macro 17
   wait 10
   

 ;  wait 40 ; because of teleporter- take out if not using teleporter
   ;do not edit below-this is your original starting point
   repeat
   event pathfind %movedx %movedy
   until #charposx = %movedx && #charposy = %movedy
   }

Sibble,
  sometimes characters freeze while pathfinding after recalls if it is laggy and everythign isnt refreshed.  if this is the case, id add a wait after the recall for a bit to limit that.  other times, a character tries to run in while it is bleeding and it kicks back one tile after reaching your spot like a teleporter.  it then tries to pathfind to a spot no longer available.  i set up two spots to pathfind to before it goes through the teleporter for this reason and it has limited that rubberbanding from the bleed trick they pull on ya.  try making the other spot one spot away from the entry point.

[Venosa]

I think my luck is that I ping horribly to ATL, because I have tested many runebooks. I have had that problem in the past where certain scripts just don't work well to shards I ping very high to.

yes,  it is the recall sub stopping the script when it cannot find the book.  i saw it happen to me two times last night on a lag spikes on an older computer.  I really cannot edit TMs recall code that is in my script.  i could possibly just make a default rune as part of the script for returning to the house.  since all the recall code is not mine... it limits me but it is def that section because i finally witnessed it after days and days of use.

Ahh I see well at least I know I am not crazy lol. Thank you for checking into it C2

[_C2_]

I think my luck is that I ping horribly to ATL, because I have tested many runebooks. I have had that problem in the past where certain scripts just don't work well to shards I ping very high to.

yes,  it is the recall sub stopping the script when it cannot find the book.  i saw it happen to me two times last night on a lag spikes on an older computer.  I really cannot edit TMs recall code that is in my script.  i could possibly just make a default rune as part of the script for returning to the house.  since all the recall code is not mine... it limits me but it is def that section because i finally witnessed it after days and days of use.

i rebooted everything after leaving it shut down for a bit and now it has been blazing for 5 hours straight on a laggy shard for me.  interesting.  i think the only way to truly beat that behavior is for me to redo the recall routines for this particular script.  i dont see myself having a lot of time to do so.  maybe this weekend, maybe not though.  i thin we have it narrowed down but it seems to pick on only you for 99.9% of the time.  what a hater!


Ahh I see well at least I know I am not crazy lol. Thank you for checking into it C2

[NObama]

Are there any new items from T or T this year?

[gimlet]

Are there any new items from T or T this year?

[The Ghost]

Yes
11 Head on  spike

[NObama]

Wow, those are gruesome.  Guess I might have to fire this script up.

[unisharp]

I added a wait 20 in before the open door script, currently flawless.