17 replies to this topic

[Scrotch]

Hey guys, its my Ward Tracker and its Tracking Wards.

Download

 

Save this file to Common folder and Add require("WardTracker") to your testscript1.lua

 

This script needs DLib to work.

[Deftsu]

nice desctiption

[Scrotch]

nice desctiption

Thanks

[pleb]

we also have one inbuilt  

[Darkness]

well we have one inbuilt on GOS

[Scrotch]

i know there is a inbuilt one

[Darkness]

i know there is a inbuilt one

then why did you create this script o-o?

[Tiritto]

What's the point of the script that is already implemented in GoS itself?

[Kiara789]

What's the point of the script that is already implemented in GoS itself?

Farm Rep?

[Inferno]

Farm Rep?

What's the point of the script that is already implemented in GoS itself?

then why did you create this script o-o?

Honestly, there is effectively TWO ways of detecting wards, and GoS built-in uses only one.
Way 1 (GoS used):
OnCreateObject. If object is created, then mark it as 'Ward' and write all information about it. Everyone can implement it.
Pros: If we saw a ward, we will never forget about it.
Cons: If we haven't... >.<
Way 2 (GoS missed):
OnCastSpell. If enemyhero, that is visible, casts a spell called "TrinketTotem1" or something like that, we taking the end point of the cast, and marking a ward on this position.
Pros: We don't need to see a ward placement!
Cons: If we don't saw enemy champion, we will not see any wards.
Way 3 (???):
Whenever we see animation of ward placement (you know, this semi-transparent wave), we setting a big circle where newly placed ward can be (because, you know, anumation always the same, but ward position can be closer or further to enemy hero)
Pros: We know EVERY ward in game.
Cons: We don't know EXACT spots.

but... this script using only Way 1. So, agreed - farm rep

[Scrotch]

its first version i can update it to way 3

[Inferno]

its first version i can update it to way 3

If it will work (I mean, the Way 3, because I haven't tested it at all), then you will be hero of the day

[Tiritto]

Is the 3rd way even possible with current API?

[Inferno]

Is the 3rd way even possible with current API?

I guess so. This semitrasparent wave is a .troy object (as far as I can tell), and it should be captured by OnCreateObj.

[Deftsu]

What's the point of the script that is already implemented in GoS itself?

uh it's the same as what's the point creating Kalista script if we arleady have one ? well even if we have one in GoS, he still want to release it cause it's his own work..

[ZeDasCouves]

One picture no?

[Yun]

One picture no?

nice

[ilovesona]

Honestly, there is effectively TWO ways of detecting wards, and GoS built-in uses only one.
Way 1 (GoS used):
OnCreateObject. If object is created, then mark it as 'Ward' and write all information about it. Everyone can implement it.
Pros: If we saw a ward, we will never forget about it.
Cons: If we haven't... >.<
Way 2 (GoS missed):
OnCastSpell. If enemyhero, that is visible, casts a spell called "TrinketTotem1" or something like that, we taking the end point of the cast, and marking a ward on this position.
Pros: We don't need to see a ward placement!
Cons: If we don't saw enemy champion, we will not see any wards.
Way 3 (???):
Whenever we see animation of ward placement (you know, this semi-transparent wave), we setting a big circle where newly placed ward can be (because, you know, anumation always the same, but ward position can be closer or further to enemy hero)
Pros: We know EVERY ward in game.
Cons: We don't know EXACT spots.

but... this script using only Way 1. So, agreed - farm rep

nice explanation

 

hope some1 can read this post and implement it....