Skip to content
This repository was archived by the owner on Aug 10, 2022. It is now read-only.

2.3.0 - GabenForPresident (testing)

Pre-release
Pre-release

Choose a tag to compare

@Efreak Efreak released this 26 Sep 02:32
· 108 commits to development since this release

WE NEED TESTING

Also, don't use this on your live/main bots, it's not considered stable.

I'm fairly sure the sentry logic is broken, but cba testing it myself. I'm like that. Most of the default file locations have been moved to the bot.name folder*. However, the sentry logic has been almost entirely removed in favor of simplicity of just having bot.name.sentry in the current bot.username folder. This means that you'll have to either move the file or redo steamguard. On the first run you'll get a notification of this, after which the bot will exit to give you a chance to move the file--and then it won't show up again.

  • github webhook is fixed
  • new weather trigger
  • new antispam trigger (needs testing)
  • We've moved to an organization. This setup makes it easier if I decide to give up control of the project to someone else--they don't have to see the repo url move again, as that person can just be added to the project.
    • @dragonbanshee's .NET port of the bot is also in the organization, but hasn't gotten quite as much development yet.
  • I'm not actually sure when I did this, but you don't need to put username and password as separate arguments in the constructor anymore; they can be specified in the options object instead.
  • There's no info on antispamTrigger or weatherTrigger in the website; maybe someone else wants to help?
  • It'd also be nice to get some testing done on the WebUI branch, which is currently separate from (and possibly slightly behind) the development branch. Please see the earlier pre-release for more info.

* bot.name replaces bot.username for privacy everywhere except login, and it defaults to bot.username if you don't set it manually

I repeat, WE NEED TESTING

We'd like to get someone to test the bot for us, but we're not gonna wait for that.

If we don't get any feedback in the next week or so, we're going to release it anyways.