56 replies to this topic

[Ghoultard]

Its missing in the github repository.

Unless u hacked the repository u did not :-)
 

xD

I thought I can delete it on script directly but I can not

[Tweetieshy]

u can delete it on yourpersonal script copy, but u cant on the official github version... unless u hack it and even then i have the same issue on my local copies too.

 

its easily fixed, but i made some more changes i wanna test before giving out an update.

[Ghoultard]

Tell everyone when u update it

[Tweetieshy]

i am currently testing it... i dunno its broken as fuk atm. doesnt has to do with my changes since i tested it without my changes and it still breaks whole GoS.

 

will need some more time to investigate.

 

Edit.:

Script updated and cleaned up

 

Crashes are gone for me now, hope for you guys too.

 

btw: if you encounter this nil value errorr, it says its located in ICs Orbwalker script, dunno what i shall fix there

[Marty]

just tested and works a lot better now!

 

my notes (so far)  

• tower-attacking doesnt work (maybe something with the autoattack-range and the holdzone: substract the holdzone-range from the aa-range? or try another orbwalker)
• sometimes buying failed and it is waiting for enough gold instead of walking back to lane
• pathfinding could be improved (walking mid is really buggy you have to circumnavigate the nexus)
• randomize the champion movement on lane (for example while farming and standing on lane the bot is very obvious)
• randomize the recall-feature (recalling under tower and recalling in bushes in different positions)

[Tweetieshy]

the tower attacking was invented for no enemy minions around to farm.... didnt do much effort in it to actually hit the tower down since hard pushing is a way to win too...

that buying issue is new... sometimes it fails buying, thats ok sometimes.. bc then he hasnt enough money for next item and should go back to lane immediately.

 

pathfinding could be improved... but hell pathfinding is ugly to code ....

 

randomizing movement is also very difficult.

 

recall feature is made to be at the safest position possible... not counted in intelligance...

 

 

all in all beside if anything of that doesnt break the script i would accept them as "features" :-P
But if im feeling for it... i maybe improve something of that.
 

 

thanks for report anyway.

[Ghoultard]

i am currently testing it... i dunno its broken as fuk atm. doesnt has to do with my changes since i tested it without my changes and it still breaks whole GoS.

 

will need some more time to investigate.

 

Edit.:

Script updated and cleaned up

 

Crashes are gone for me now, hope for you guys too.

 

btw: if you encounter this nil value errorr, it says its located in ICs Orbwalker script, dunno what i shall fix there

Like you said, got just Ics Orb Error, and he just don't AA turret. Sometimes he AA Ennemy under tower and die
I think u need to use other Orb like Gamsteron Orb (pm him to see if he can do that with you)

[Tweetieshy]

Reworked post:

 

I will definitely bring updates to make the bot more believable as well fix functionalities back that are currently broken... like spellcasting, using summoners.

 

Currently working on its decisionmaking and playing safer vs. enemys that are close and more in numbers (it will try stay away in a 3vs2).

 

Fleeing was broken too, so i'm fixing this.

 

It will not go for kills if he is outnumbered. It may happen tho some more that enemy goes away with 10 hp... but well... happens everyone.

 

Some minor bugs like walking to own minions when they where between me and startpoint are fixed too.

 

After all im trying to improve more things. maybe i can get a movement randomizer working... at least a simple one...

 

I did an update today.

 

 

Old Post:

 

there is imho no logical reason to use another orbwalker... i first didnt even plan to use an orbwalker at all...

it doesnt break the script, if turret attacking doesnt work its a minor error that i can fix from time to time... not important imo...

 

and anyway, the attack tower is not handled by the orbwalker anyway, this is handled by the script "manually".

Edit:
It need some tweaks tho... i failed while refactoring the script... need to reenable some core features... XD
Spellcasting doesnt work as intended anymore too

[chinflip]

Hi,

Im loving this stuff. Im trying to get accounts to bronze 5 so this has been amazing. The only thing that would be nice is that i could configure to stay away from enemies if alone and always flee from them if attacked. All of this of course options you could turn on and off. I tried to look the code and maybe figure it out myself but im not really a lua expert.. I did only change some basic variables but this is way out of my league XD and if you can do this I can make a little donation   and the flee range wouldn't be insanely high just so It stays few dots away from enemy AA range 

[neurowend]

No update ? ?

[Tweetieshy]

Hm, the main problem about this, if it stays from enemy too far (from human ones) thats spotted really fast and you cant farm anymore properly. in the end it wont help much because there are gapcloser that make your keeping distance not that useful as you may think.

and staying "just a few dots out of enemy range" is technically not possible because of lag, movementspeed, fps etc it needs a bit a larger "offset" if it want to keep away fro enemys AA range. this doesnt count for spells tho.
It just cant react/move that fast to stay out of AA range completely if he is always on edge.

But it is possible to give it more space so enemys have a harder time to get the champ. Even though this can be abused if you never fight back (zoning) denying your bot all farm easily.

@neuro, what update u mean?

[Tweetieshy]

Just made an Update of the Bot script:

 

 

Fixed attack tower logic

 

Reworked spellcasting

Added HPred

 

Configurable Safe/Flee Zones (as requested, please read the comments on how to config)

 

Bugfixing of Wrong Item Buy value (typo)

 

Breaking Recall channel on buy to prevent double recall (happened occasionally)

 

Reworked internal functions for lil bit more performance

 

 

[chinflip]

Just made an Update of the Bot script:

 

 

Fixed attack tower logic

 

Reworked spellcasting

Added HPred

 

Configurable Safe/Flee Zones (as requested, please read the comments on how to config)

 

Bugfixing of Wrong Item Buy value (typo)

 

Breaking Recall channel on buy to prevent double recall (happened occasionally)

 

Reworked internal functions for lil bit more performance

 

Worked really nice!! thanks a lot

[Marty]

Hm, the main problem about this, if it stays from enemy too far (from human ones) thats spotted really fast and you cant farm anymore properly. in the end it wont help much because there are gapcloser that make your keeping distance not that useful as you may think.

and staying "just a few dots out of enemy range" is technically not possible because of lag, movementspeed, fps etc it needs a bit a larger "offset" if it want to keep away fro enemys AA range. this doesnt count for spells tho.
It just cant react/move that fast to stay out of AA range completely if he is always on edge.

But it is possible to give it more space so enemys have a harder time to get the champ. Even though this can be abused if you never fight back (zoning) denying your bot all farm easily.

this would make the bot really more humanlike...

you  could add healthpercent calculation and near ally/enemy champions check for the dangerzone of the bot, to allow to go in aa-range if health of bot > enemy/50 percent or number of ally champions > enemy champions

[Tweetieshy]

its not that easy Marty, but i tried my best during the weekend programming almost 15 hours on Kalista and the Bot Script.

Unfortunately i could not improve this kind of logic very much.

 

I added some manual range configuration possibilties as mentioned instead. There is a codepart (currently inactive) which tried to implement following allies to a teamfight (instead of continue farming XD) but it didnt work good enough, ending up dying much more since bot players are bitches and let u die after you follow them XD

[Gaeas]

tested with ashe 10 minutes.. its working - BUT my ashe isnt using any spells... but its activated in script options,.. how to fix that? 

edit: she used summonerspells... but still no q. w. e. r

[Tweetieshy]

ashe is actually a bit broken with it but its not rly the scripts fault, its the HPred fault.

HPred does not ever give a valid cast position for Ashes W, so it almost never casts... it only casts when it hits enemys and no minions are hit, actually.

I had to choose between better spellhitting for all other champs by using the hpred, but some champs like ashe only use it very rarely or spamming spells forever and never hitting anything with it.

But actually the aiming logic is not final, if sikakas doesnt fix her minioncollision, especially on multitarget spells like ashes W i may overwrite the prediction logic again.

This is still beta and i will still work on it when i find the time.

[Gaeas]

yeah, pls work on it if you find the time.

i'll still use the beta

 

~300 EXP/hour vs intermediate bots = 3 games

~330 EXP/hour vs beginner bots = 4 games

[chinflip]

 

this started happening to me.

I have ICS orbwalker and HPrediction. And ics orbwalker works just fine if i dont try to load tweetiebot. I reinstalled GOS. But still >*

[cemrehan]

this started happening to me.
I have ICS orbwalker and HPrediction. And ics orbwalker works just fine if i dont try to load tweetiebot. I reinstalled GOS. But still >*

I have the same mistake