6 replies to this topic

[Psycophsez]

I came from L# and I know they code in C# but I have no idea how people make configs and how the program reads them 

Just a new user with questions 

[pleb]

no scripts yet as we dont have an api yet ,but it will be c# and maybe even lua in the future

[Cat]

I came from L$ and I know they code in C# but I have no idea how people make configs and how the program reads them 

Just a new user with questions 

configs are just a little help if you really don't know how to handle with the menu.

 

You dont need to install configs.You can configure it urself ingame just F7 

[Psycophsez]

Ah ok that makes sense.

But how is the program coded? I mean, for example kalista's q used in harrass there has to be some logic/prediction put into that. 

Yet e calculations to kill enemies/objectives are still lacking. 

[kirrra]

Ah ok that makes sense.

But how is the program coded? I mean, for example kalista's q used in harrass there has to be some logic/prediction put into that. 

Yet e calculations to kill enemies/objectives are still lacking.

bro we wait the API still no logic. well let's w8 m8 i'm from L# too

[Akama]

Ah ok that makes sense.

But how is the program coded? I mean, for example kalista's q used in harrass there has to be some logic/prediction put into that. 

Yet e calculations to kill enemies/objectives are still lacking. 

The program is a single AIO atm, with no API released. This means no custom/specific assemblies.

 

The several configurations you see around are simple settings people have tinkered with to maximize a champion's potential. No code involved.

 

As for the prediction itself, it uses general projectile data for almost everything. That's the reason skillshots work somewhat fine - and the same one that some special/channeled/different skillshots fail to function.

[Mirabelle]

there's no logic atm