Notice:
I don’t want a bot, all lua if possible
I’m trying to figure out how to make and lua script login into a account with the name and password said into the script and then access the groups profits and do a payout to my devs.
I’m trying to make that, I’m. Making this so that if my devs can get paired per player. (There friends working for free but I’m. Being nice and don’t want to manually do it each time and want something to do it auto)
you can pay them with group % if thats what you’re looking for.
I know that but I don’t. Want to do that I perfer per player
You can’t make automated payouts without a bot. The only way to do so would be the % payments towards members.
I believe you would need to use this api: https://groups.roblox.com/docs#!/Revenue/post_v1_groups_groupId_payouts
This documentation gives a ‘template’ of what the PostAsync would look like.
Note that you’d need to be logging in as the owner. And if you’re not directly using ROBLOSECURITY, your requests may be blocked by FunCAPTCHA.
Why would you need to be logging in as the owner?
EDIT: If only the group owner can payout, then you could make a group with your bot account as the owner (or transfer ownership of a current group) and use this to payout.
Only the owner of a group can use the payout feature. Spend group funds is for advertisements, badges etc.
Try using GitHub - noblox/noblox.js-server: A RESTful API using noblox.js and Koa. and use the tutorial to set it up to give out funds, you will need the cookie of your account in order for payout to work.
Bots can be easily compromised.
So you tell me each robux a user spends, the bot will automatically pay them paired? Like if it’s 200 robux it will pair it exactly then?
That’s a general misconception, and I fully understand your cause for believing this. Many people think that using bots are insecure, simply because others have said so. More often than not, this is certainly not the case!
When developing a bot for Roblox, you need to take additional security measures in order to protect your system from getting breached. As Roblox doesn’t allow us to use API keys, we’re forced to use an account, which is extremely insecure, if someone gets a hold of the authorization cookie, almost anyone can get almost full access to account features.
But, the chances of someone randomly guessing your authorization is extremely low, and by extremely low, I mean seriously low. For someone to properly access your account they’d need (at minimum) to attempt more than 600^35 combinations! The reason for the bots’ undeserved reputation is that the ones creating the bot accounts are (either):
As long as you’re following proper security standards, both for coding and for your account, you shouldn’t really have an issue with this.
That is a general misconception, however I would advise against it strongly.
You should NOT be running any bots on your own personal account. That is a bad idea and will 100% end badly.
I’ve been running bots on my accounts to do general stuff like update many assets at one time and upload tons decals and stuff for years now. When it comes to bots, they’re safe. Especially when it comes to ones that you create your self and can view the source of.
Of course a file such as legit_group_bot.exe shouldn’t be trusted at all.
Unless running on your own device, that is unsafe. This is the same reason Rojo suggests you use a machine user for it’s automated Roblox tools (even though it’s on your device).
It seems to be like you don’t have a solid understanding how bots work. All bots are ran on your own device or on a server that you own. Bots just emulate requests to perform tasks, there is nothing un-safe about them.
That is not correct.
That does not make them secure.
This is turning into spam, please move this to private messages.
All you’re doing is putting your cookie into to the script so it can run through the account, it’s only as insecure as you would be if someone accessed your computer, or your clicked on a malicious website.
If it’s your own code, and you keep the cookie safe, you’re fine.