7 replies to this topic

[ReverseMisaya]

Post all of your patch 8.10 developer-related issues and/or suggestions here.

 

This is not the place to post stuff why your game doesn't work

Those issues should be posted here: http://gamingonstero...rum/41-support/

[ReverseMisaya]

GameObject.activeSpell.startTime is missing the unit's winduptime (can confirm for minions)

--same as patch 8.8 startTime (when everything was working fine)
local startTime = unit.activeSpell.startTime + unit.attackData.windUpTime

[sikaka]

Re stating request for two api improvements

#1: Give us a callback for when the bot re-caches game data (missiles, particles, game objects)

This will let us avoid re-scanning all game missiles every frame (or near to it) looking for ones added/created. Saves us doing workarounds and will give us more responsive, more efficient scripts.

#2: Give us a way to read the rotation of in game data

.dir has been unreliable for ages and does not work with things such as Taliyah W push direction. Being able to read rotation directly from in game memory vs a unreliable direction vector would be very useful for a number of things. The game has to have the info in order to render it properly so while I understand it may take some digging with their spaghetti code it should certainly be possible with the existing bot framework.

[Kiara789]

In particle.pos i'm getting for example: x = 3489 and y = 90, what is wrong here? im just printchat xy pos

[ReverseMisaya]

In particle.pos i'm getting for example: x = 3489 and y = 90, what is wrong here? im just printchat xy pos

 

.pos returns an x,y,z-table

.pos2D returns an x,y-table

[Kiara789]

.pos returns an x,y,z-table

.pos2D returns an x,y-table

yes, but when i printchat .pos y gives low numer, but x and z return map pos correctly, example: x 3489 y 60 z 4620 something like that

pos2d return screenpos

[ReverseMisaya]

yes, but when i printchat .pos y gives low numer, but x and z return map pos correctly, example: x 3489 y 60 z 4620 something like that
pos2d return screenpos

.pos contains 3D-coordinates. So the y-coordinate is correct
 

[RMAN]

.pos contains 3D-coordinates. So the y-coordinate is correct
 

That img is kinda misleading since league uses x and z as the main plane xd
y is a low value because it's the height of a particle (should be close to 0 when lying on the floor).

I wanna say "Lets use this post for bugreporting only" but.. How is the orb coming along?