Dragonite config updates

package.json

@@ -27,5 +27,6 @@
   "devDependencies": {
     "@types/node": "18.11.10",
     "typescript": "^5.2.2"
-  }
+  },
+  "packageManager": "yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e"
 }

pages/docs/dragonite/config.mdx

@@ -50,14 +50,31 @@ enable = true
 # token_init_enabled = true
 # don't rely on remote auth and only use accounts with stored token - true by default
 # token_refresh_only = true
+
+[auth.nk]
+enable = false
+#login_delay = 20
+#token_init_enabled=true
+#token_refresh_only = true
 ```
 
-⚠ Additional config variables, but only put them if you know what you do ⚠
+⚠ Additional config variables.
+Do **NOT** change these unless you **REALLY** know what you are doing! ⚠
+
+Dragonite has sensible defaults for these options and changing them can lead to unexpected behavior!
 | Key | Default | Description |
 | :-- | :-- | :-- |
-| token_refresh_concurrency | 10 | define concurrency for the token background refresher |
-| token_init_concurrency | 1 | define concurrency for the token background initer |
-| token_init_interval_seconds | PTC: 1, NK: 180 | define the interval to request tokens |
+| `token_refresh_concurrency` | 10 | define concurrency for the token background refresher |
+| `token_init_concurrency` | 1 | define concurrency for the token background initer |
+| `token_init_interval_seconds` | PTC: 1, NK: 180 | define the interval to request tokens |
+| `token_init_start_delay_minutes` | 5 | define a delay for starting the token initer |
+| `remote_auth_timeout_seconds` | 60 | define a timeout for remote auth requests |
+| `remote_init_retry_delay_minutes` |  | define a delay for retrying remote auth requests |
+| `remote_auth_secret` | "" | define a secret for remote auth requests if needed |
+| `token_refresh_days` | PTC: 28, NK: 12 | define the days after which a token should be refreshed |
+| `token_refresh_start_delay_minutes` | 5 | define a delay for starting the token refresher |
+| `ip_ban_backoff_minutes` | 15 | define how to long to backoff an IP |
+| `token_valid_days` |  | define the days a token is valid |
 
 ## Koji section
 
@@ -87,22 +104,39 @@ bearer_token = "KOJI_SECRET"
 
 ```toml
 [tuning]
-#recycle_gmo_limit = 4900
-#recycle_encounter_limit = 9900
-#recycle_on_jail=false
+#recycle_gmo_limit = 4990
+#recycle_encounter_limit = 9975
+#recycle_invasion_limit = 900
 #minimum_account_reuse_hours = 169
-#location_delay = 0
+#scout_age_limit = 30
+#location_delay = 2500
 #fort_location_delay = 0
+
 ```
 
 | Key | Default | Description |
 | :-- | :-- | :-- |
-| `recycle_gmo_limit` | 4900 | (Advanced) Recommend keeping this value commented out. When the GMO limit is reached for a specific account it will be be rotated. |
-| `recycle_encounter_limit` | 9900 | (Advanced) Recommend keeping this value commented out. When an account has encountered this amount of pokemon it will be rotated. |
-| `recycle_on_jail` | false | Enabling this setting will utilize significantly more accounts. Currently five accounts are assigned to one worker and will rotate while the worker is running. |
-| `location_delay` | 0 | This value, in milliseconds, will add a slight wait period while a worker is moving to a new location. Adding a slight delay has proven to decrease empty GMO results and positively impact scans overall. Recommend starting with 100, 200, 300, etc and monitoring overall results. |
-| `fort_location_delay` | 0 | This value, in milliseconds, is the same as `location_delay` however it only impacts fort scans (gyms/pokestops). |
+| `recycle_gmo_limit` | 4990 | (Advanced) Recommend keeping this value commented out. When the GMO limit is reached for a specific account it will be be rotated. |
+| `recycle_encounter_limit` | 9975 | (Advanced) Recommend keeping this value commented out. When an account has encountered this amount of pokemon it will be rotated. |
+| `recycle_invasion_limit` | 900 | (Advanced) Recommend keeping this value commented out. When an account has encountered this amount of invasions it will be rotated. |
+| `location_delay` | 2500 | This value, in milliseconds, will add a slight wait period while a worker is moving to a new location. Adding a slight delay has proven to decrease empty GMO results and positively impact scans overall. Recommend starting with 2500+ and monitoring overall results. |
+| `fort_location_delay` | 0 | This value, in milliseconds, is the same as `location_delay` however it only impacts fort scans (gyms/pokestops). When not specified, it uses the same value as `location_delay` |
 | `minimum_account_reuse_hours` | 0 | This sets the amount of hours for accounts to "rest" until they can be reused. Recommended value is 169 hours (7 days). |
+| `scout_age_limit` | 30 | Configure age limit for scout queue entries |
+| `test_shadow_banned` | true | Automatically test accounts for being shadow banned and marked as banned in database. |
+| `quest_layer_swap` | false | This option for questing will hold on to AR Quests and try to move to 'ar only scans' over time. When set to 'true' it will try and drop ar quests if you have them as required, unless your account is marked as ar banned). |
+
+### Dynamic Location Delay
+Make `location_delay`(max) dynamic by tuning against `initial_gmo_success_rate`(percentage), limited by `minimum_location_delay`(min).
+
+This is applied per worker and resets to the max value(location_delay) after an account is rotated.
+Every 50 steps Dragonite checks the success rate of GMOs without retries and adjusts location delay accordingly.
+```toml
+#Example configuration
+location_delay = 7000
+initial_gmo_success_rate = 80
+minimum_location_delay = 3000 
+```
 
 ## Accounts section
 

yarn.lock

@@ -394,9 +394,9 @@ busboy@1.6.0:
     streamsearch "^1.1.0"
 
 caniuse-lite@^1.0.30001406:
-  version "1.0.30001555"
-  resolved "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001555.tgz"
-  integrity sha512-NzbUFKUnJ3DTcq6YyZB6+qqhfD112uR3uoEnkmfzm2wVzUNsFkU7AwBjKQ654Sp5cau0JxhFyRSn/tQZ+XfygA==
+  version "1.0.30001699"
+  resolved "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001699.tgz"
+  integrity sha512-b+uH5BakXZ9Do9iK+CkDmctUSEqZl+SP056vc5usa0PL+ev5OHw003rZXcnjNDv3L8P5j6rwT6C0BPKSikW08w==
 
 ccount@^2.0.0:
   version "2.0.1"