Yes with latest version... Is the account verfied or not? but i think its a bot bug, because my second-main account is 100% verfied(ptc login), but the bot say not verfied and exit ^^ looks like a bug from bots
All the accounts are automatically verified.
Facing problems with your bot? Check out this thread for possible solutions:
Can someone tell me why every bot keeps saying ptc account not verified?
Originally Posted by rebeliu
It is asking for account verification. How can I do this? Thanks for the creator!
Originally Posted by tata01
Same here.
Originally Posted by kingchenc
Yes with latest version... Is the account verfied or not? but i think its a bot bug, because my second-main account is 100% verfied(ptc login), but the bot say not verfied and exit ^^ looks like a bug from bots
I have been with headache for days with that... When using the bot and writing PTCUsername and PTCPassword, look well at WHAT ARE YOU WRITING...
I mean, in text file generated it's PTCuser : PTCpassword and in config file for bots its PTCPassword : PTCUser
just stumbled across this tool and I'm wondering what the accounts are named and which emails are used in the progress.
Would be awesome to specify the account names in a template which the tool uses afterwards to create the accounts
just stumbled across this tool and I'm wondering what the accounts are named and which emails are used in the progress.
Would be awesome to specify the account names in a template which the tool uses afterwards to create the accounts
just stumbled across this tool and I'm wondering what the accounts are named and which emails are used in the progress.
Would be awesome to specify the account names in a template which the tool uses afterwards to create the accounts
If you download the executable, the usernames will be a random string of characters, up to 12 chars in length, the email address is the username generated @divismail.ru but you don't need to worry about the email, it's a temporary box used to activate, then it's gone.
You CAN specify what sort of usernames you would like, it has been discussed earlier on in this thread, albeit you will have to download the source code and edit it yourself.
It's not a very difficult task, unless you over complicate things, the hardest part of editing this is actually installing the required repositories needed to run the program (ruby, gem, bundlers, nokogiri, etc.)
Once you're set up though, it's an amazing program, very easy to work with and no issues so far! All 150 of my accounts were activated and have been running fine for ~12 hours so far.
These are the ones, dont know which you have to install, but just try with all, if not working with one continue!
now open up the cmd in the gem.exe folder Or if you set up PATH then it doesnt matter where.
Ok INSTALLATION :
type gem install nokogiri
press enter
wait
rinse and repeat
then start the rb file
have fun.
By the way, is it just my internet (or my laptop) or why is it like creating an account in 1 minute?
And it always spits out : PTC Account Creator Started
Unknown key: Max-Age = 31449600
Unknown key: Max-Age = 7200
Unknown key: Max-Age = 31449600
Unknown key: Max-Age = 0
Unknown key: Max-Age = 31449600
Unknown key: Max-Age = 31449600
Unknown key: Max-Age = 31449600
Unknown key: Max-Age = 31449600
[Try: 0] 1 Accounts created
Somethings not working? It takes too long and sometimes it stops. Probably mail server shitty or something
Ignore the unknown key output, it spits that out but it works fine.
The reason it takes like a minute to create is due to mail server load, and one thing I've noticed about the OP's code (not trying to insult/offend) is that he loops the "while !email_received" method, without sleeping unless it errors, which is causing a HUGE load on the server alone, just imagine what it'll do with many users doing this.
If you tried this in off-peak times, it would be a little faster for you.
As for the repositories to install, you don't do all of them.
You need to install Ruby installer for windows (easier than manually doing it)
Then once you have that installed, gem will be installed automatically.
Use the command stated above, "gem install nokogiri" without the quotes.
Once that is installed, you should be good to run the program by double clicking the rb file.
If the program is instantly closing when trying to run it, open up a command prompt and CD into your account creator source file, then run the command "bundlers exec ruby account_creator.rb"
This will use the gem installed repositories and hopefully get things running for you.
Just a heads up, Ruby does not need compiling, to edit the source you just edit the .rb file, save it and run it again.
It works fine but it's not creating each account in descending order. Say I have accounts.txt and inside Acc1, Acc2, Acc3, etc, it will just pick a random name instead of doing it in order. Is it something to do with this?
Code:
lines = File.readlines("custom_names.txt")
username = lines[rand(lines.length)].tr("\n","")
while(username.length < 12)
begin
username = "#{lines[rand(lines.length)].tr("\n","")}#{username.tr("\n","")}"
end
end
while(username.length > 15)
begin
username = "#{username[0,15]}"
end
end
For you to have it in ascending/descending order without an entire username text file, you would need to declare a variable that can be used inside and outside of blocks, such as a global variable (but not a static) that holds the integer of 0, then have a counter (or use the one already coded) do +=1 each loop, then concatenate that into the username string.
Ruby, however, doesn't like this at all and it would be WAY more hard work for you than you realise.
What may be easier, is just writing code to call the one line rather than lines[rand(lines.length)] but this MAY result in a higher ban rate, but do not take my word for that, it's just my opinion.
Let me play around with the code some, I'll see if I can write up what you need as it'll be useful for many others too.
EDIT
As for the program hanging, it does that from time to time due to server load, it sends a request and it'll just sit and wait for it for as long as the server will let it, which in this case seems like an eternity haha.
Restarting the program sends a new request, hence fixing it.
Maybe add a timeout value to the !mail_received method, causing it to time out, sleep for a few seconds then request said email again.
Not sure how viable this method would be though, I've not really given it much thought.