Config

  1. Navigate to the config folder inside the Datenheim-Go directory on your desktop.

  2. If you're unsure where the folder is located, copy and paste the following path into your file explorer: C:\Users\%USERNAME%\Desktop\Datenheim-Go\config

  3. Open the config.json file in any text editor and adjust your config.

Field Explanation

Field
Description

LicenseKey

  • Enter your license key, which can be found on the Whop dashboard.

Webhook

  • Specify the Discord channel where the bot should send checkout notifications.

QueueItWebhook

  • Specify the Discord channel where the bot should send queue pass notifications.

CapMonsterKey

  • Your CapMonster API Key

  • A minimum of one Captcha provider is required.

AntiCaptchaKey

  • Your Anti Captcha API Key

  • A minimum of one Captcha provider is required.

2CaptchaKey

  • Your 2Captcha API Key

  • A minimum of one Captcha provider is required.

CapSolverKey

  • Your CapSolver API Key

  • This field is required for the TOS module.

  • Currently, CapSolver works exclusively with TOS.

CaptchaProvider

  • Define wich Captcha Solver the Bot should use.

  • Value can be CAPMONSTER or AntiCaptcha or 2Captcha

Full_Path_To_Chrome

  • Enter the full path to your Google Chrome installation. If Chrome is installed in the default location, use the following path: C:/Program Files/Google/Chrome/Application/chrome.exe

  • Important: Ensure the path uses forward slashes (/), as the bot will not function with backslashes (\).

Show_Proxy_in_Queue_It_Webhook

  • The value can be either true or false and determines whether queue pass notifications should include the proxy used.

TOS_Queue_It_Instances

  • Specifies the number of Queue-It tasks to launch when a queue is detected in the TOS module.

Enable_Wake_Lock

  • Determines if Datenheim.go should prevent your PC from going to sleep.

  • Important: Not required to be used on Servers

Start_in_new_window

  • Determined if the bot opens tasks in a new window

CF_Solver_Instances

  • Specifies the number of CF_Solving instances on task level.

  • Example: If CF_Solver_Instances is set to 5 , this means 5 cookies per Task are being created and 25 in total.

  • Recommndation: 3

CF_Solver_Concurrency_Limit

  • Specifies the limit of concurrent CF_Browsers.

  • Example: If CF_Solver_Instances is set to 5 and you are running 5 tasks - But the CF_Solver_Limit is set to 10 this means no more than 10 concurrent browser will be open at a time. Other CF Jobs will wait until a spot becomes free.

  • Recommndation: 10

Pushover_User_Key

  • Specifies the User Key for the Pushover integration

  • Can be grabbed from the account section on:

Pushover_Application_Key

  • Specifies the Application Name of the Pushover App

  • Can be grabbed from the account section on:

Pushover_Priority

  • Optional to supply

  • If set to 2 -> Notifications will be alerted once every minute for 15 minutes, even if your phone is on Do Not Disturb

Pushover_Sound

Telegram_Bot_Token

Telegram_Chat_Id

Show_Proxy_in_Webhook

  • The value can be either true or false and determines whether success notifications should include the proxy used.

Example (config.json)

Last updated

Was this helpful?