From a5740e83f48be9d2460c7e23a6c850e09b73d633 Mon Sep 17 00:00:00 2001 From: Schuyler Cebulskie Date: Wed, 1 Mar 2017 04:51:46 -0500 Subject: [PATCH] Change burst mode warning --- src/util/Constants.js | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/util/Constants.js b/src/util/Constants.js index e05668a81..56369024a 100644 --- a/src/util/Constants.js +++ b/src/util/Constants.js @@ -5,9 +5,8 @@ exports.Package = require('../../package.json'); * @typedef {Object} ClientOptions * @property {string} [apiRequestMethod='sequential'] One of `sequential` or `burst`. The sequential handler executes * all requests in the order they are triggered, whereas the burst handler runs multiple in parallel, and doesn't - * provide the guarantee of any particular order. - * Burst mode is more likely to hit a 429 ratelimit by its nature, - * be advised if you are very unlucky you could be IP banned + * provide the guarantee of any particular order. Burst mode is more likely to hit a 429 ratelimit error by its nature, + * and is therefore slightly riskier to use. * @property {number} [shardId=0] ID of the shard to run * @property {number} [shardCount=0] Total number of shards * @property {number} [messageCacheMaxSize=200] Maximum number of messages to cache per channel