Improve getBallPosition()

[olehmisar]

Ball radius is not always fixed. Map makers can change ball size. Could you add/replace getBallPosition() function with getBall() function which returns x, y, and radius? Hope for that.

[Leo-MapCreator]

What about getBall(): x, y, radius, speedx, speedy?

[olehmisar]

Yeah, great idea. And to be consistent basro should change getPlayerList() function which will return array of objects of this type: { id, name, team, admin, position: { x, y, speedx, speedy } }

[Leo-MapCreator]

honestly, getPlayersList does not need that, you can get the other things easily with just the id

[olehmisar]

No, it needs because you cannot get player speed anywhere

[Leo-MapCreator]

Then improve getPlayerPosition instead of getPlayerList

[olehmisar]

There is no getPlayerPosition() function

[FrescoPL]

Since the ball radius is coded inside the stadium file, maybe something like getStadium could be added as an extension of this idea.

[olehmisar]

@basro, modify onStadiumChange() to accept stadium contents as second argument.

[Leo-MapCreator]

@olegmisar PlayerObject position : {"x": float, "y": float} The player's position in the field, if the player is not in the field the value will be null.

[olehmisar]

Omg, leo, read our conversation again, you don't understand what is going on.

[Leo-MapCreator]

You that does not understand it, im showing you the command you said it didnt exist, even though the name isnt the same because i didnt remember the name of the command the first time and i didnt want to expend time looking for that

[saviola777]

@Leo-MapCreator You get the PlayerObject from the getPlayerList() function, so that's the function that has to be changed, and that's exactly what @olegmisar suggested.