-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add current x and y position for cursor in the API #278
Comments
No, I won't be adding that, it would potentially signify that the repository forks would be used for bad purposes, which I don't want for osu! I am willing to consider such functionality for big tournaments for a fee and a promise not to use the software outside N tournament, however for normal use - this api is dangerous :( (an example of such api can be found in gameosu https://www.twitch.tv/videos/510135434). I advise you to use other analysis tools such as: CircleGuard, replay analyzer by AG, built-in osu! lazer replay viewer |
Thank you for your surprisingly fast response, I honestly wasn't aware it could be used with malicious intention, however, for the project I am working on, I still need cursor data live, not on replay:( could you help me at least get a hint on how or where can I get the memory address for x and y position of the cursor? or refer to places to learn about how to get it? I don't have much experience with low level programming, but I am still learning. If it makes it any better, I won't be making public that part of the project (also it's a school project, lol), as thankfully, most of the data is read from the tosu API or the beatmap file |
Check this pr from rosu-memory 486c/rosu-memory#29 |
I can implement this, but as normal non precise data, it shouldn't damage the game in theory |
I will think on days about all concerns, if I convince myself it can't be used for cheats, I'll do one |
Thanks, I'll check it out, dw, if it turns out it can be used for cheats don't do it, better to keep the game integrity intact |
It would be useful to have access to the current x and y position of the cursor within the API. This feature would allow analysis of cursor movement live, it would make sense to add it in "/json/v2/precise".
The text was updated successfully, but these errors were encountered: