if you make it syphon faster after it has done a monster, or the storm dissapeared it would be a epic script!
Blood wraith does not get identified as blood wraith
Blood wraith is identified correctly but other items match "blood wraith"
Blood wraith is identified correctly with no false hits but is slow
Blood wraith is identified correctly and has no false matches and is very fast
if you make it syphon faster after it has done a monster, or the storm dissapeared it would be a epic script!
I am working on new multicolor models so that i can then discover location based on overlapping TPAs.
Problem using TPAs in their ordinary form is that you just get bunch of disparate points that match the search, the trick is to sift through them to figure out which are noise and which are not. But that still will not allow you to pinpoint with very high degree of accuracy whether you are siphoning earth essling or clicking on stone edge on 1st floor runespan
that's where my multicolor overlapping model search will come in handy.
stay tuned.
Although initially i am working on Blood and Death esswraiths as proof of concept of multicolor area search/identify
last thing i want to do is to wait for uptext when trying to get new target, waiting for uptext while already siphoning is ok.
bot is clicking on mini-map like it tries to go to another island....
This is something you may have never seen before :P
i know none of the scripts that i looked at implement it
idea is simple - multi color matching with density search
what can it do?
extremely high accuracy near real time target detection
wanna proof? :P
wait for next version ;-)
oh and by the way - i was waiting 0.1 second between every test, else my screen would be all green
nice i haven't seen that in any script either
Over 8 hours, took the picture right after it logged.![]()
add souls in 2 plox?![]()
i am taking my time releasing next version because i'm trying to add everything with the new tracking models that i created
current status (if you don't see it, it was already done)
hounds
air NOT YET DONE
mind NOT YET DONE
water NOT YET DONE
fire NOT YET DONE
body NOT YET DONE
m:
cosmic NOT YET DONE
chaos NOT YET TESTED
astral NOT YET DONE
nature NOT YET DONE
soul NOT YET DONE
nodes
Cyclone NOT YET DONE
Mind storm NOT YET DONE
water pool NOT YET DONE
rock fragment NOT YET DONE
fireball NOT YET TESTED
vine NOT YET DONE
fire storm NOT YET DONE
fleshy growth NOT YET DONE
m:
chaotic cloud NOT YET DONE
nebula NOT YET DONE
jumper NOT YET DONE
skulls NOT YET TESTED
bloody skulls NOT YET DONE
undead soul NOT YET TESTED
Some things like undead soul are done but not tested, why? because by the time i coded the new model, the target was long gone :P
I'm running it now, I should a a proggy in the morning!![]()
Ok for a short time but has lots of problem on long run. Moreover, the priority function could be updated because it does air esslings for me all the time when there are hundreds of higher level around it.
Might be it is not finding the DTMs, could you please add TPA finding also?
Version 18 seems faster exp then Version 20?
Here is a 2 hour proggy going good so far got 80 crafting so now i can buy wicked top
![]()
This is working extremely well. Thanks again! Supported!
I keep getting
as it is already siphoning the runes?Simba Code:The following DTMs were not freed: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 32]
I'm on the 3rd floor and I want it to do death wraith's but it seems to just ignore the death wraith on the island and instead siphons out of the cosmic hound.
Hi zmon, I just tried the script and I ran into an issue, the bot doesn't siphon the highest thing possible. I'm on the 3rd floor and tried several platforms, but the bot starts siphoning regular Esswraiths instead of stuff like skulls etc, which are far better XP.
Maybe this is a bug in the latest version? Just thought I'd let you know.
the models are not complete yet, i know that skulls in the release were not tested, but i did get a screenshot of skulls recently so i'll model them
basically the models rely on overlapping tolerant tpas so i need to find few colors that are good representation
the difference between using single color with very low tolerance and several with slightly higher tolerance is that if you chose the colors wisely, you should be able to eliminate almost all false positives, problem is that i don't know if there is an extension that would scan area of image and compare colors to the whole screen to come up with few relatively unique colors to use
i will search for it today and if i won't find it, i'll have to write it myself
i just remembered -if you are using release prior to 22, which does include 21, there is a problem sometimes reading inventory amount of essences, so in one of the most recent version, i got the call to SRL replaced by my own function
it's not that srl doesn't do it right, it's that srl expects non-tolerant DTMs for inventory and it gets confused, or something like that, whereas the DTMs for essences that i have, they all have built in tolerance
why is essence level important?
well in order to prevent essence drain, if you are under 100 essences, all searches for better target are suspended, if you are siphoning a creature. That is because upon destruction of creature, you get bunch of essences.
if the essences are under 100 and you are siphoning node, the main loop will start looking for creatures only, so that it can lock onto them
============Rough Stats etc...============
Time Running: 8 Hours, 3 Seconds
XP Earned: -3726340, per hour: -18504
Points Earned: 1057, per hour: 132
Preempted Counter: 45, clicks: 29
Current Target: HOUND - NATURE, 43.5xp, level 44
Current Runecrafting Level: 53
Essences Available: 1121
Current Floor: We are not in RuneSpan
I left it on while i was at school and abit longer![]()
ok after profiling the code i have found out that some models just are very slow to evaluate, for example the currently disabled fire essling on first floor generates thousands of matches in one of the color, but if another color is not present at all, i still do process the data, this of course is not so great to do in script so i will change the density discovery to, rather than locate and calculate all matches within each overlay, will test existence per look up location in all color channels and will process data only if possible match found
the call to discover if tpa color with tolerance matches on given region is much faster than evaluating all matches, and if we fail to match all color overlays, we will not even need to evaluate anything
if the procedure gets stuck processing vast number of matches, the result is that it becomes unresponsive to new nodes popping up in timely manner, plus it eats cpu when it probably doesn't even need to
working on new density search now
There are currently 1 users browsing this thread. (0 members and 1 guests)