That's why you should be using version control with branches ;)Quote:
Originally Posted by DarkstaR
Printable View
That's why you should be using version control with branches ;)Quote:
Originally Posted by DarkstaR
I am using Mercurial but didn't think to branch off as I wasn't expecting an update any time soon, haha. Also, I did have to add/change quite a few constants and modify a lot of the same files, so it would have been merge HELL.Quote:
Originally Posted by diofeher
Some items seems to be considered as walkable since this update (ex. some borders on this roof).
http://i.imgur.com/GdkBH.jpg
Perfect. I'll look into it, thanks.Quote:
Originally Posted by sirmate
@DarkstaR
If a scarab dies and a larva dies on same spot, then the bot just stands there forever because it can't reach the loot, and i fully understand thats what you updated, but would be cool with a option "Ignore loot if not reachable"?
I actually did not change anything having to do with this. In the past did it do this? Nothing I changed should effect this.Quote:
Originally Posted by Kingdom
Found ID's for them: 995-999 and 1004-1005.
EDIT:
After adding those ID's into blocking section in Items.xml file I ran into such situation (those borders seems to be walkable only when some walkable item is below it):
http://i.imgur.com/0nNtg.jpg
then xeno be update or need new scripts? becose i dont understund that.
working beautifully, no problems what so ever with waypoints.
working suck on my perfect script for 300k. perfect becose after uptade working great
Got the same problem with walker stuck. Im botting Yalahar sunken quara´s. Maybe that also got something to do with the pathfinding you changed? Before the update it worked well and now it isnt.
yea sometimes the script just get stuck , before update i never had that with 4-5 scripts
xeno going down. sometime ago i was think to change xeno for ibot. maybe now i gonna do this
Bitching about your scripts won't help if you don't post the scripts you're using.Quote:
Originally Posted by Koksik22
+1 ~~Quote:
Originally Posted by Syntax
Tonight, I will entirely replace the new pathfinding with the older pathfinder. Anyone who bitches about it can suck me.
++2 lolQuote:
Originally Posted by maicoln
Nooo :( it worked so good, for me atleast, not 1 script is malfunctioningQuote:
Originally Posted by DarkstaR
Quote:
Originally Posted by DarkstaR
well , was working fine with me the new pathfinding , maybe ppl is lazy for redo his scripts , and test it again o.o
gl anyway
Calm down baby, we love uQuote:
Originally Posted by DarkstaR
hmmm, I used setWalkerEnabled(false) to logout my char , if he has not enough pots to move on, now I cant use this anymore..it's weird :S
That wont work from one-liners but should work from label callbacks. To do it from a one-liner, just use
Code:while (true) do wait(200) end
Hope you dont go back to the old path finder. the new one has some bugs but they can be worked out. I have no problem with any of my scripts.
So, what is going on? Changing back or Staying with what's now? I rather not look into my scripts before I know ^^
@DarkstaR
Regardless you wont have too. If I fix the problems, the problems are fucking fixed.Quote:
Originally Posted by Jakob Miller
Darkstar, is that so hard to make Setting in targeting like "only if trapped", it would help alot for lots of scripters to make 100% afk not every shit monster on targeting. please do something in this way :)
Glad to hear! You are doing a good job mate, I respect your programming skills!Quote:
Originally Posted by DarkstaR
Bot now tries to walk into some1 house, and go down or upstairs often. ;/
Hilarious, @for the ppl who says "noo please stay with this version" u guys only dont have to download the new version with the past pathfinder cause the new one is working fine for u, so stop crying ¬¬
http://i49.tinypic.com/3534cns.jpg
Well in response to you for the crystal spiders, Heres the cliffs that are considered walkable, sorry for not posting a picture before.
I sent you a pm asking if you wanted one, then I realized that was stupid of me. Also my post wasn't very helpful before, so in regards to that Ill give as much info as possible.
Map clicks works fine, I just cant use them with my current script because of the route it takes, But for the walker it trys to run onto those cliffs (Looter and targetter too) Allowing me to get stuck and beat on.
So I currently use no path finding options, With mapclicks it works pretty well but like I said, looter and targetting still may get stuck.. I hope this gives you a better idea.
And for feedback, The walker overall is much faster and nicer, It does an amazing job. But with any new code... THERE WILL BE BUGS, So ignore the retards Darkstar.
Thanks for the wonderful bot, and all the work that went into that coding.
That last 1% is the hardest % there is.
-Sunrah
I'm having issues with .lua functions, ex. every time bot hits a check way point it decides to leave the spawn with plenty of supplies never happened before. Not sayin its due to this update, just a new and unusual observation
@Sunrah @sirmate
What you're rediscovering is an old bug I fixed back when @Tala found it in Yalahar minos. The problem is that there is no item on that tile that is actually blocking. Instead, it's just missing a "tile" which in turn makes it blocking. Essentially, while there nothing to make it block, there's nothing to make it Walkable, and the pathfinder only considers the first possibility.
The easy fix was this at the time:
Essentially, if the first item isn't a ground tile, we say it's blocking. I accidentally changed that code to this (No clue how this happened).Code:if (stack == 0) if (!itemData::isGround(id)) return false;
Effectively re-introducing the bug. Thanks for the reports, it will be fixed.Code:if (stack == 0xFF) if (!itemData::isGround(id)) return false;
I also had this problem with lua file as above, before it went smooth, today after patch it actully jumps right past em. Maybe you removed delayWalker and setWalkerEnabled from the lua reader aswell by mistake? Just tryign to give some ideas since like some of my functions are fucked up that used to work before... Example is
setWalkerEnabled(false)
delayWalker(6000)
Self.Say("hi")
wait(900, 1200)
Self.Say("pass")
wait(900, 1400)
Self.Say("sunken")
wait(500, 800)
setWalkerEnabled(true)
Today it just said hi and then started to walk away trying to find a way around the gate resulting in walker stuck after it reached the shore.
Anyways just trying to help you locate the problem or so, perhaps you'll find the source to it since ur the b0ss @DarkstaR
/Stusse
I'll look into the label issue but it's weird because they work for me. delayWalker(), setWalkerEnabled(), etc all work. Might be some of my delays, I'll look at it.
i have almost all script from xongiver is not cheap and most of all have problems becose bot was update
I preferred the old walker, just my opinion, found this one to be a bit... well... weird lol seems to take "long" routes to a waypoint. Also messed up some of my scripts, dont know how, so had to clear them and start again, quite a pain but not a majorly big deal. But yea all in all I thought the old walker system worked a lot smoother.
darkstar i have after ss mass walker stuck- poison and my char no go (brimstone bugs)
I've experienced problems with the bot skipping labels it did not skip earlier.
Like this levitate script.
[code=lua] elseif (labelName == "LevitateUp") then
setBotEnabled(false)
Self.Cast("exani hur up", 50)
wait(1000,2000)
setBotEnabled(true) [/code]
I know you said you were gonna look into it above. Just thought I'd add it incase it could help in any way;)
Same problem here. WALKER STUCK. every 10 minutes, its just like playin manualy XD