Welcome to TRiBot Forums

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

iFluffee

Moderator
  • Content count

    1,919
  • Joined

  • Last visited

  • Days Won

    10
  • Feedback

    100%

Everything posted by iFluffee

  1. You have VIP, there are no VIP scripts though, which would explain that
  2. When you're trying to open what exactly?
  3. I post quite a bit, and I've never had that happen :/
  4. Check your firewall settings in Windows Firewall, see this post or post back if you need more instruction:
  5. As far as I know it should, yes You could always proxify a .jar, like OSBuddy, instead of FIrefox
  6. How to Run Most Applications Through a Proxy on both Windows and Linux Windows Instructions Note: Chrome and Firefox portable do not work with WideCap. 1. Download WideCap from here (http://widecap.ru/en/download/) 2. Run through the installer, and launch WideCap, you should see this screen. 3.Go ahead and click on Settings (First option under the Widecap section on the left hand side). Then uncheck the box that says Run with system startup. 4. Now go ahead and click on New proxy (First option under the proxies section on the left hand side). 5.You should see this screen, in the top field enter the IP address and port (IP:Port format). Confirm that the protocol is set to SOCKS v5 (which is the default), and tick the box for Authentication if necessary. If using an authenticated proxy, enter your username in the login field, and obviously your password in the password field. Then hit the Create New button, next to Chain, and type in a name for your Proxy, then Hit OK 6. Now that you're back to the main screen, click on the Proxy List section (Second option under the proxies section on the left hand side). Right click on your newly added proxy, and click check selected, to make sure you entered all the information correctly. If the status field rolls over to OK, you're good to go, and can move on to the next step 7. Find WideCap in your System tray, right click, and uncheck the box that says Enable Widecap. 8. Click on View Programs (Second option under the Programs section on the left hand side). Then drag and drop the icon for the application you want to proxify (run behind a proxy) into WideCap. WideCap supports the proxifying of both .exe and .jar files! 9. Right Click on your newly added program, and click on Modify Application, you should see a similar screen depending on what you added. Then click on Create New... (to create a new rule) 10. In the Chain tab, select the Proxy Chain you created earlier, then under the Main tab, give your new rule a name and hit OK. Then Hit OK again on the modify Application screen. 11. Hit Apply and OK in the main window of WideCap, and then find it in your System Tray again, but this time click the box to Enable Widecap 12.Open your Proxified application, and check to see if the proxy worked! If your IP is changed, congrats, you've got WideCap working! Linux Instructions (Based off of a Debian Installation) 1. Open a new terminal and run this command sudo apt-get update && sudo apt-get install -y proxychains 2. Now that proxychains is installed, we're going to go ahead and create a user specific configuration file. To do this, we'll make a directory, then copy the standard proxychains configuration file to it and change the ownership of the configuration file to your user. Run the command below as your user. mkdir ~/.proxychains && cp /etc/proxychains.conf ~/.proxychains/proxychains.conf && sudo chown ${USER:=$(/usr/bin/id -run)} proxychains.conf && sudo chgrp ${USER:=$(/usr/bin/id -run)} proxychains.conf 3. Once the command is finished, open the proxychains config file in your favorite Linux text editor, for ease of use, I'm going to use nano. To install nano run this command sudo apt-get install -y nano To edit the proxychains config file, with nano, run this command nano ~/.proxychains/proxychains.conf 4. Now, what you'll want to do is scroll all the way down to the bottom, and you should see something like this That last line that says socks4 127.0.0.1 9050 That's the line we'll be editing. Firstly, we'll go ahead and erase everything on that line, don't worry we'll put it back. The format for the configuration file is Proxy Type(lowercase) (tab) IP address (tab) Port (tab) Username (tab) Password Therefore if your proxy was a Socks5 proxy, with an IP of 192.168.1.1, a port of 1080, a username of Fluffee and a password of TRiBot, your final line would look like this: socks5 192.168.1.1 1080 Fluffee TRiBot So, go ahead and modify your last line to fit your own proxy and then hit Control+X to exit, and then hit Y to save (instructions are based off of using nano to edit the file). 5. Proxychains is now setup, but how do you use it? Go ahead and VNC into your Server and open a terminal, or open a Terminal inside your Desktop Environment (if using Linux installed on a PC). From there run the command proxychains followed by the application you would like to run, or the path to the application. For example, try running, if you have Firefox installed: proxychains firefox Then navigate to an IP checking website, and see if your proxy worked! That concludes the tutorial on how to use a proxy with Oldschool or any browser, on both Linux and Windows. If you have any questions feel free to post in the comments!
  7. Can you post a picture of your bot/client debug in full?
  8. Try setting up your server with this guide:
  9. You must open TRiBot_Loader.jar with Java for it to work properly. The latest Java Development Kit (x86, 32 Bit version) is recommended for optimal use with TRiBot which can be downloaded from this link Java Development Kit Downloads. After that has been completed, try running this program to fix the .jar file associations and allow TRiBot to run with the latest java http://johann.loefflmann.net/en/software/jarfix/index.html Alternatively, follow the steps in this thread to manually associate the proper java version with .jar files, and as a result, enable TRiBot to run properly. [PC] How To: Open the TRiBot_Loader.JAR file w/ Java [Pics]
  10. I've noticed this, but that's just my anecdotal evidence and not at all a fact. But I think it depends on what you're botting and how bot-like it is!
  11. You can actually do it with a free domain! I have a tutorial written for it; I just didn't think interest was there!
  12. Did you enter the proxy details correctly? Did the proxy work on something outside TRiBot? For example, an internet browser?
  13. Try lowering your resolution, that may fix the issue!
  14. You have VIP
  15. Open OldSchool in a regular client (i.e. official client, OSBuddy, RuneLoader, etc.) then change your ingame screen size settings to fixed. Then restart TRiBot and the error should be gone! See the .gif below for instructions:
  16. Head to this page (https://tribot.org/repository/user_panel/vip/) and click Get Started under the VIP option of your choosing!
  17. What script did you attempt to activate?
  18. I believe that issue is related to an outdated Java version, so try updating that. Alternatively follow this tutorial step-by-step, your problem should be fixed: [Mac] How To: Resolve Most Problems With TRiBot [Pics]
  19. Happy new year!
  20. This works ^
  21. When you activate a script it should appear in the client after clicking Run Script, not in the scripts folder
  22. The script doesn't work well with Debian 8. I have an updated version written, but I haven't put the finishing touches on it yet!
  23. Notes: I have only been able to test this setup procedure, on Debian 6.0, 7.9 and 8.1 (as they are all DigitalOcean provides). I can assume if it works on those, it will work on the other distributions in that set, but there are no guarantees. Secondly, this script requires root privileges to run, do not try and run without root or you will encounter issues Thirdly, this script and tutorial, will guide you through the process of disabling root logins on your server, creating a new account which you will use with root privileges, and changing the default ssh port. If for some reason you feel those are not good things to do (they are, leaving root logins enabled opens you to a world of issues) then you can edit this script yourself, or skip those steps in the guide. Do not post here complaining you can't login as root, you should never ssh as root after you setup the server, and I refuse to promote that terrible practice. Lastly, there are some redundant commands in the script, however they do no harm so I'm not concerned with them at the moment Step 1. Acquire a non-setup Debian VPS (Recommended Debian 7 x86) (http://www.waveride.at is a personal favorite) Step 2. Download PuTTY (PuTTY Homepage) Step 3. Download a VNC Viewer (TightVNC is my personal recommendation, use whatever you prefer) Step 4. SSH into your server, and get to a root prompt (SSH in this case means to connect via PuTTY) (NOTE: YOU MUST BE ROOT) Step 4a) Open PuTTy, you should see a screen like this Step 4b) Enter your Server IP Address into the box that says Host Name (Or IP Address) Step 4c) Enter your server login details and you're done Step 5. If you don't care to learn anything, and you really just want the server setup and done with, go ahead and run this command (32 Bit) apt-get update && apt-get install -y sudo wget && wget --no-check-cert 'https://dl.dropboxusercontent.com/u/81527571/Debian%207%20(32%20Bit)/install32.sh'&& chmod +x install32.sh && ./install32.sh (64 Bit) apt-get update && apt-get install -y sudo wget && wget --no-check-cert 'https://dl.dropboxusercontent.com/u/81527571/Debian%207%20(64%20bit)/install64.sh'&& chmod +x install64.sh && ./install64.sh The command above installs sudo and wget (Installed by default in Debian 7.0+), downloads the install bash script from my Dropbox, gives the script run permissions, and then runs the script. If you'd like to view the script before running it (which you should): 32 Bit 64 Bit Step 6. When the script starts, it will prompt you for the following information: Hit enter after entering your information for each question What would you like your user account to be named? Must be lowercase This is going to be the name of the account you will be using from now on, as root logins will be disabled (over ssh, you can connect as this account and then switch to root afterwards, just not directly connect as root). Just type in the name of your account in all lowercase, for example bots What port would you like to use to ssh to your server? This port is the port used when you use PuTTy to access your server, the default is 22, please change it from 22 to make your server more secure. I recommend something kinda random, such as 6754. Again, just type in your port number of choice What port would you like to use to vnc to your server? The default port for this is 5901, if you want to continue with that port type in 5901 or type in any other port of your choice. What would you like your ssh password to be? This is the password of the new account the script will create, type in whatever you want your password to be, you must enter a value What would you like your vnc password to be? This is the password used when you vnc to your server, it can be anything but you must enter a value Step 7. Now that the information is entered you can sit back and relax, and the script will do the rest. When it finishes, you can go ahead and VNC into your server and run your favorite botting client For anyone you doesn't care what the script does, this tutorial is finished! Please feel free to spread some love for the time I spent writing this tutorial, and perfecting the script For the advanced users, or anyone who isn't just going to run something that I claim is safe, read on and I'll walk you through every command, well most of 'em Command Explanation apt-get update - This command checks the repositories included, for any updates to the Debian software, and updates them automatically apt-get -y install sudo wget nano - This command is slightly redundant, and I just noticed it. Anyways, I'm not fixing it because there's no harm here, but this command installs: sudo (Allows other users to run things as root) wget (allows you to download things from the internet, via bash) nano (A nice bash text editor, which is merely my preferred option over vi [the default bash editor]) sed -i "s/Port 22/Port $sshport/g" /etc/ssh/sshd_config - Replaces the phrase Port 22 with the port inputted at the beginning of the tutorial, if you're running this by copying and pasting each command, replace $sshport with your port of choice. Or, use nano or vi to edit the file /etc/ssh/sshd_config and change the port there echo "AllowUsers $name" >> /etc/ssh/sshd_config - Adds the user account inputted in the being to the list of users allowed to connect via ssh replace $name with your user account name, if you're doing this yourself sed -i "s/PermitRootLogin no/PermitRootLogin yes/g" /etc/ssh/sshd_config - Turns root logins off by replacing the line, skip this if you don't want to turn off root logins chmod 600 sshd_config - Assigns the correct permissions to sshd_config, this command is also unnecessary as of now. service ssh restart - Restarts the ssh service to make the changes take effect, this will not close your connection apt-get -y install xorg lxde tightvncserver - Installs Xorg a LXDE component, LXDE a lightweight desktop environment and TightVNC Server, which will allow you to use VNC to connect to your server sudo adduser $name --gecos "First Last,RoomNumber,WorkPhone,HomePhone" --disabled-password - Adds a user account without a password, if doing this yourself, replaces $name with your desired name echo "$name:$sshpassword" | sudo chpasswd - Changes the password of the account just created, replace $name with the account name, and $sshpassword with the desired password sudo adduser $name sudo - Adds the created user to the sudo user group, which will allow it to run commands as root, replace $name with your desired account name mkdir /home/$name/.vnc - Creates the .vnc directory echo $vncpassword >/home/$name/.vnc/file - Writes the vncpassword to a file, change $vncpassword with the desired password vncpasswd -f </home/$name/.vnc/file >/home/$name/.vnc/passwd - Creates the password file used by the vnc server, and writes the password chown $name /home/$name/.vnc - Changes ownership of file to the user you created chgrp $name /home/$name/.vnc - Changes the group of the file to the user you created su - $name -c "vncserver" - Runs vncserver as the created user su - $name -c "vncserver -kill :1" - Kills the vncserver process as the created user All the curl and wget commands are used to download the popular botting clients, and OSBuddy, places them in a created folder echo deb commands are used to add repositories to Debian to download java (Google Debian JDK8 webupd8 for more details) apt-key gives the server the proper key to connect to the repositories echo oracle allows the script to auto accept the java license agreement chmod 777 /usr/lib/jvm/java-8-oracle/jre/lib/security/java.policy - Gives permission to policy file for LG The rest of the commands install firefox, allow the Java Runtime to be seen, create the tightvnc service (so it autostarts) and modify the vncport. If you genuinely have questions, hit me up on Skype: HiFluffee Update January 19th, 2016: Updated both sh files to disable root logins properly, had a mistake in the code. The script also converts any capital letters in the account name to lowercase. If capitals are present the account doesn't get created. Update February 29th, 2016: Fixed the sh files to allow automatically allow connections via VNC to a custom port on reboot of the server. Update: March 2nd, 2016: Now automates keyboard, character and encoding selection Update: March 6th, 2016: Automatically picks Java to open Jar files, and removes Screensaver Update August 20th, 2016: The script now installs TightVNC 1.3.9.10 which fixes the VNC crashing error when too many programs are opened at once.
  24. Please post an account recovery for your account in the Account Recovery Section be sure to follow the Account Recovery Format when posting your thread. This will speed up the process and hopefully have you back on your account in no time!