Separate names with a comma.
Discussion in 'Guides' started by AnEnchilada, Jun 10, 2019.
isn't anti afk not alowed to use?
its fine as long as you don't use it to create a spam bot. Beeing afk is fine and this mainly improves your alt login times and helps you out if the server gets random restarts or the auto reconnect bugs out.
Ok thanks, do you know what I can do about autorelog in case my internet crashes for a sec?
I still try to figure that out. But you can certainly do that.
Ok, I'll also look in to it I'll let you know if I figure it out
K I think i kinda made a configuration that allow you to afk 24/7 with many alts just by one click, it includes the autorelog and the ant afk that you posted, so far it still a beta and I need you guys to send me kick messages that you get in the server, so no matter what reason you get kicked for you will auto rejoin me mineheroes.net and the server you where in. When everything is set i'll make a txt tutorial about how to configure it for your self
for automatic relogging, use autorelog. you have to give it a text file with sample messages to look for kicks. this is what my Autorelog section in mainscripts.ini looks like
retries=3 #-1 = unlimited
This requires a kickmessages.txt file, which contains this:
Connection has been lost
Server is restarting
Server is full
Too Many people
for logging in, use a bat script for each character. do this by creating a text file called (username).bat containing this:
MinecraftClient.exe [email protected] password mineheroes.net
this will open a client signed in to that user, and connect to mineheroes.net
next, under ScriptScheduler in MinecraftClient.ini, set enabled=true and taskfile=mainscript.ini
mainscript.ini is where you call the scripts that actually do stuff. all i actually use right now is a script to tell the client how to get into skyblock. this is mainscript.ini:
notice it calls login.txt. that file looks like this:
send /server skyblock
this script waits long enough to get to hub, then does the minechat command to enable other commands. then waits for the server to respond before sending the command to go to sb1. after this, it waits longer to give the skyblock login and welcome message enough time to go through, then sends the minechat command again which is necessary if you want to use auto tpa. you could also add a "tpa username" right after it, so if you're loading the bot and want it to go straight to you, all you have to do is click the bat script and do /tpaccept
For auto teleporting, you can set the bot to only work for you by defining a botowner file. you do this by naming a file (i use botowners.txt) in the Main section of MinecraftClient.ini with this setting
this is what my botowners.txt looks like
nicknamed characters DO need their nicknames listed, and the tilde ~. this file is cached and not update live, so you need to close out all instances of MCC to be able to add owners to this file.
So i tried to use this and it keeps saying failed to connect and asking for a server version, any ideas?
It could be either of those 2 problems.
1. You try to connect with an not supported minecraft version. You can check the line
"mcversion=1.8.9 #use 'auto' or '1.X.X' values"
2. You use an outdated version of console client. v1.9.0 works for me. You can check your console client version in the MinecraftClient config file. It should be stated on the very top.
I tried to use 1.9.0 which is an outdated version and still didnt work. Now i'm running into time out error.
"Thread was being aborted. A timeout has occurred while connecting to this IP."
I also have the MC version to auto. I've tried using 1.7.9, 1.8.9, 1.15.2, and 1.12.9 as the versions.
I'm getting Login failed: Failed to check session.
This occurs after loging into minecraft.net and connecting to the server successfully, but it doesn't seem to not let me login? Any ideas?
I don't think you (or the other people above) are allowed to continue posting on a thread that was "dead" for almost a year.
To answer your question anyways though, update your console client by going to the appveyor website or whatever its called and get the latest update/patch on it. Usually fixes it