Someone’s commission, they want a bot that can payout via Discord.
There is a module called robloxpy, it is written in their description that there is a feature to pay out via Code. But the classes are not there in the package, when I print there directories.
We’re currently in the process of rewriting ro.py, but we do plan to make our ill-faded “URL utility” extend to the entire library, which will allow you to simply replace the roblox.com URL with any proxy of your choice and even change the way the URL is laid out.
Don’t quote me, but:
If I recall correctly, group.join_requests contains a Pages object which you can use an async for to iterate through. You can then look at each JoinRequest object and call .accept or .deny on that request.
Uploading assets is something we’re thinking about implementing for the rewrite. Do you have a specific use case or a reason you want to upload audio in your code?
I am currently working with a website that makes music and we want to add a way to make a bot upload all the audio (to the company account) to Roblox as Roblox doesn’t support uploading non-local files. (files stored online) and keeping all the files on the device is too much storage and time consuming.
ro.py is still actively maintained and updated! We are now mainly offering support in the RoAPI Discord server: discord.gg/Jj8ZYBH4KU
Apologies for the lack of updates on this post - I’ve been maintaining the project independently for a couple months and I’m about to release a rewrite in 19 days.
If you’re using v1, you have to call get_member and check the .role.
If you’re using v2, you have to grab the user and call get_group_roles. You can then loop through the roles and check if that role.group.id is equal to the one you want. If it is, you know that’s the user’s role in that group, so you can use that role.
Hey everyone! Just want to let you all know that on 2021-12-05T05:00:00Z we’ll be celebrating ro.py’s 1st birthday. Wow!
For the past couple of months, we’ve been working on a complete refactor of the library including its documentation. On this date, we’ll be releasing the rewrite (hopefully) and publishing it to PyPI and GitHub.
If you want to see what we’ve been working on, check out the new GitHub: