Raidbots

@raidbots

Run SimulationCraft in the cloud! For support, please email support@raidbots.com

The Internet
Joined December 2016

Tweets

You blocked @raidbots

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @raidbots

  1. Feb 12

    Sims on the site seem to be OK again for now. The Discord bot is still having issues.

    Undo
  2. Feb 12
    Show this thread
    Undo
  3. Feb 12

    Free sims are remaining in queue much longer than usual. I'm investigating right now - at first glance it looks like an issue with Google Cloud Platform.

    Show this thread
    Undo
  4. Feb 2

    Raidbots is updated for the class tuning changes that hit NA today.

    Undo
  5. Jan 30

    Usual note about tuning/hotfixes - by default, Raidbots/SimC will not be updated with the changes until they are live on NA servers.

    Undo
  6. Jan 28

    Top Gear and Droptimizer now properly show covenant-specific weapons from Nathria weapon tokens and Conquest rewards.

    Undo
  7. Jan 27

    If you have manually set these in Custom APL and SimC Options, those will override these settings. So if you want to use the nice ones, clear those lines out from that section.

    Show this thread
    Undo
  8. Jan 27

    A few trinket options have been added to "Simulation Options" to enable some finer-grained control over how they are simmed.

    Show this thread
    Undo
  9. Jan 20

    I'm rolling out a fix for this, there was a bug in soulbind parsing/combinations that was screwing up Dreamweaver sims.

    Undo
  10. Jan 19

    This will work as expected once you have slotted something into the conduit socket (and unchecked "Unlock All Soulbinds"). There are some limitations that make it difficult to detect slots that are unlocked but are currently empty.

    Undo
  11. Jan 12

    Raidbots is updated to the latest version of SimC which contains the tuning changes for this week.

    Undo
  12. Retweeted
    Jan 10

    I have recently fixed a bug I caused in SimC. This is a really unfortunate mistake and I'm sorry for letting folks down. Hopefully this post answers most of your questions: As usual more sims in progress so stay tuned. Time to embrace Talbadar's!

    Undo
  13. Jan 8

    Usual note about tuning/hotfixes - by default, Raidbots/SimC will not be updated with the changes until they are live on NA server on Jan 12th.

    Undo
  14. 22 Dec 2020

    I just deployed a fix that was causing some soulbinds to not properly detect and sim all conduits - this was definitely happening consistently with Dreamweaver and possibly some others. Reload the site and it should be handled correctly.

    Undo
  15. 16 Dec 2020

    Weapon tokens from the Great Vault should now work as expected in Top Gear when using the latest version of the SimC addon (9.0.2-15).

    Undo
  16. Retweeted
    15 Dec 2020

    With the first Great Vault loot of Shadowlands, players will inevitably ask themselves "What item should I choose?". To help in this dilemma, players can use Raidbots in conjunction with the SimulationCraft addon.

    Undo
  17. 15 Dec 2020

    Another heads up - looks like Gmail is having problems today: If you aren't getting emails to your gmail account because of this, either wait until Gmail fixes it or you contact me in the Raidbots Discord.

    Undo
  18. 15 Dec 2020

    Both Nightly and Weekly SimC Versions on Raidbots have been rebuilt to include the latest Dec 15th hotfixes.

    Undo
  19. 15 Dec 2020

    /simc and Top Gear do not currently handle weapon tokens from the raid. I'm working on this but it's likely going to take some time (at least a few hours, possibly a day or two - and that all assumes the site doesn't crash from the traffic)

    Undo
  20. 15 Dec 2020

    Blizzard appears to have fixed the Armory API issue. In most cases, the Discord bot and "Load from Armory" on the website will now know about your covenant and soulbind. If covenant/soulbind are not showing up, login/logout with that character to try to force an Armory API update

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·