scholtzm / vapor Goto Github PK

https://github.com/scholtzm/vapor/blob/master/lib/vapor.js#L212

Should be _steamUser.

Hello scholtzm,
Is it possible to using steam-user with vapor ? Please give me a hint. Thanks

Handling cookies is not trivial, they do become invalid from time to time.

Because of the way plugins work, it's important that each plugin is using the same set of cookies, otherwise they might invalidate each other.

Since node-steam v1.0.0 is just around the corner, I'll be waiting holding off any changes and I'll be implementing a proper cookie handling later on.

In the meanwhile, you can just call webLogOn method although this might to be counter-productive if you run multiple plugins that use cookies.

I got this error today, the internal function keeps calling _webLogon so the bot was punished by Steam. This happened only when Steam is totally down. How can i stop this function to be called? Thanks for your help.

2018-04-13 07:06:44 - info: [x] Received new Steam server list.
2018-04-13 07:06:47 - warn: [x] Received status 503 in "webLogOn". Retrying...
2018-04-13 07:06:47 - warn: [x] Received status 503 in "webLogOn". Retrying...
2018-04-13 07:07:20 - warn: [x] Received status 429 in "webLogOn". Retrying...
2018-04-13 07:08:06 - warn: [x] Received status 429 in "webLogOn". Retrying...
2018-04-13 07:08:57 - warn: [x] Received status 429 in "webLogOn". Retrying...
2018-04-13 07:08:57 - warn: [x] Received status 403 in "webLogOn". Retrying...
2018-04-13 07:08:58 - warn: [x] Received status 403 in "webLogOn". Retrying...
2018-04-13 07:08:58 - warn: [x] Received status 403 in "webLogOn". Retrying...
2018-04-13 07:08:58 - warn: [x] Received status 403 in "webLogOn". Retrying...
2018-04-13 07:08:58 - warn: [x] Received status 403 in "webLogOn". Retrying...
2018-04-13 07:08:59 - warn: [x] Received status 403 in "webLogOn". Retrying...
2018-04-13 07:08:59 - warn: [x] Received status 403 in "webLogOn". Retrying...
2018-04-13 07:08:59 - warn: [x] Received status 403 in "webLogOn". Retrying...
2018-04-13 07:08:59 - warn: [x] Received status 403 in "webLogOn". Retrying...
2018-04-13 07:09:00 - warn: [x] Received status 403 in "webLogOn". Retrying...
2018-04-13 07:09:00 - warn: [x] Received status 403 in "webLogOn". Retrying...

Hello scholtzm,
I'm trying to listen to event 'tradeOffers' of Steam.SteamUser(); like this but failed, the log wouldn't populate when I received new items. Please help

bot.use({
name: 'test-steam-user',
plugin: function(VaporAPI) {
VaporAPI.registerHandler({
emitter: 'steamUser',
event: 'tradeOffers'
}, function(count) {
log.info("New items in our inventory: " + count);
});
}
});

When using vapor in a production environment with electron. I am getting this error when trying to do
require('vapor').

All new instantiations of API reference the first instance of Vapor created. This clashes heavily when multiple bots are created.

For instance if I create two Vapor clients like so

plugin = {
  name: 'testplugin',
  plugin: function(VaporAPI) {
    var log = VaporAPI.getLogger()

    VaporAPI.registerHandler({
      emitter: 'client',
      event: 'logOnResponse'
    },
    function(logOnResponse) {
      log.info(VaporAPI.getClient().steamID) // These will output the same SteamID
      log.info(VaporAPI.getConfig().username) // Even though we are in the handler for two separate bots.
    })
  }
}


config = {/* unique config options */}
anotherConfig = {/* different config options */}

var bot = vapor();
bot.init(config);
bot.use(plugin);
bot.connect();

var anotherBot = vapor();
anotherBot.init(anotherConfig);
anotherBot.use(plugin);
anotherBot.connect();

When the logOnResponse is received, it will output twice (for each bot) but will show only the steamID for the first bot that was created (using var config).

Sorry if this is intended behaviour but it makes implementing self-aware plugins a bit tricky?

Also please excuse any JS syntax issues as I mainly use CoffeeScript.

Since 2 days my bot stuck at:
"Connecting to Steam network"

what can I do? :(

I believe it could be a possibility to automatically re-login when the session expires.

I know with node-steamcommunity, an event is emitted when the session fails. I do not believe the same is found within node-steam.

I'm looking into including this feature locally, so if I find a good way to implement it I'll submit a PR.