rDB (short for resource database)

Description

Free, but required, companion software that serves as a resource management database for keys/proxies.
  • All my apps (that connect to battle.net) require this to be running in the background.
  • Allows 16/26‚Äźdigit keys. Allows SOCKS4/SOCKS5/HTTPS proxies.
  • Handles cooldowns on keys/proxies.
  • Supports local or remote usage via TCP sockets (so you could have my apps on different machines, but all connecting to an rDB instance on 1 machine).

How To

Important

rDB must be left open at all times if you want it to supply the other apps with keys and proxies. If rDB gets closed, it's not a huge deal, but it means that the current state is lost and when you start it back up, it might give out keys and proxies that were already provisioned.

Also, try to avoid leaving rDB resource lists in a sorted state. This can lead to increased CPU usage and a laggy interface.

Importing Keys

Keys can be separated by any of the following: =, newlines, tabs, spaces, commas, ;, <, >, ", /. Any dashes will be stripped out. rDB will automatically detect classic and expansion keys from the input.
Examples:
  • abcd-efgh-ijkl-mnop
  • ABCDEFGHIJKLMNOP

Importing Proxies

Proxies can be separated by any of the following: =, <, >, /, newlines, tabs, commas, spaces. Credentials may be appended inline with @username:password or they can be added in bulk after importing just the server and port.
Examples:
  • 123.123.123.123:1234
  • 123.123.123.123:1234@username:password
  • [12ab:23cd:45ef:67ab:89cd:12ef:34ab:56cd]:1234
  • [12ab:23cd:45ef:67ab:89cd:12ef:34ab:56cd]:1234@username:password

Testing Proxies

Select one or more proxies, right-click, select Test:
You can also change the testing type by going to the rDB configuration:
Type Description Results
Slim Simple connection check to battle.net Stored in Testing.log in the same folder as rDB
Full Complete login to lobby (creates and logs into an account, then creates and selects a character, the credentials are cached for later use) Stored in a sub-folder named rDB-Logs\[session timestamp]\

No Proxy

There is a proxy type of None that lets you connect normally, without a proxy, to battle.net:

Limits

Limits are a feature implemented to force an app, or even a particular module type from an app, to use a particular subset of your resources. By default the Limit ID is set to 0 for all resources, this is a reserved ID meant to be a sort of global/shared space.

Limiting an Entire App

To limit an app (eg. PermIt) to use a subset of your resources, check the rDB ID (defaults to the app name):

In rDB, add an entry to the Limits tab with that ID as the Program Name and give it a number above 0:

Now in your resources you can edit the Limit ID to that number:

Now PermIt will only use 234.234.234.234:1234. Any incoming resource requests for an ID not listed in the Limits will receive a resource from the global space (ID 0).

Limiting a Particular Module Type

To limit a particular module type from an app to use a subset of your resources, configure an arbitrary ID (eg. iDB-Dropper):

In rDB add an entry to the Limits tab with that ID as the Program Name and give it a number above 0:

Now in your resources you can edit the Limit ID to that number:

Now iDB droppers will only use 321.321.321.321:1234. Any incoming resource requests for an ID not listed in the Limits will receive a resource from the global space (ID 0).

Changelog

2020-06-23: v1.0.0.118

  • ADD Added Check True IP for proxies

2020-06-05: v1.0.0.117

  • FIX Fixed bug where OK button wasn't enabled for editing keys

2020-02-18: v1.0.0.112

  • UPD Re-enabled AllowSimultaneousCDKeyUseOnDifferentRealms and AllowSimultaneousProxyUseOnDifferentRealms

2020-02-05: v1.0.0.111

  • UPD Unhid Statistics property