Steam bot that accepts all types of trades that are being overpaid. (Not just CS:GO)
Switch branches/tags
Nothing to show
Clone or download
1
Latest commit f11237a Apr 7, 2017
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
resources Change `InvalidApp` message Mar 13, 2017
.eslintrc.json Changes Mar 21, 2017
.gitignore Add vscode ignore Mar 13, 2017
ISSUE_TEMPLATE Create ISSUE_TEMPLATE Mar 17, 2017
LICENSE License Mar 15, 2017
README.md Edit README Mar 15, 2017
bot.js Fixes #6 Apr 7, 2017
config.js Bot files Mar 13, 2017
package.json Package.json Mar 13, 2017

README.md

Steam overpay bot

dependencies npm steam paypal

Steam bot that accepts all types of trades that are being overpaid. (Not just CS:GO) This script is not fully tested so use with caution, like with any open-source script I suggest looking through the code first to see how it works.

Setup

cd <directory of files>
npm i

To start the bot you have two choices.

  • node bot.js - This means the script will run until you close the terminal or CTRL + C which exits the script.
  • pm2 start bot.js -n "SteamOverpay" - This will keep the script running forever, when an error occurs it will restart it.

To use the pm2 method install it first npm i -g pm2

Configuration

All of the options that are configurable are in config.js - all of the options are commented. The trade messages, except the success message, are available and editable in resources/TradeMessages.js.

Contributing

Issues

  • If you're reporting a bug, please include all relevant details.

    • A descriptive title helps for one. Titles of just "Error" or "It doesn't work" really don't help.
    • Please describe what you're trying to do, what actually happens, and what you can do to reproduce the problem.
    • If you have an error message or a crash, please include the full text of the error message and the stack trace.
    • Include the relevant snippet of your code. Wrap it in ```js /* code */ ``` and GitHub [will format it nicely for you]
  • If you're requesting a feature, please be descriptive and understanding.

    • A good title makes a difference. Please briefly describe what you're requesting in the title.
    • Be descriptive in the issue body, too. Say what you want to do, and ideally what the method should be named.
    • Be understanding if I don't think that your feature request falls within the scope of this module.

Pull requests

  • Please follow the existing code style. I have included .eslintrc.json file with this package, follow the rules.
  • Please include a brief description of your change in the pull request if it's not immediately apparent from the code.
  • Be understanding if I don't think that your change falls within the scope of this module.