Current transfer process relies on IP-based matching between TS3 and TS6 clients. While convenient, this approach can be unsafe in shared-network environments, where multiple users may appear under the same public IP.
This proposal introduces an additional authorization step: a confirmation request sent via private message to the detected TS3 client before allowing the rank transfer to proceed.
Proposed Solution
Introduce an optional verification step requiring explicit confirmation from the matched TS3 client.
Workflow
- User initiates the transfer process
- Bot sends a private message to the matched TS3 client
- Message asks for confirmation (e.g. "Are you attempting to transfer your server groups to TS6? Reply with y/n")
- System waits for response:
y → proceed with transfern or no response (timeout) → abort transfer -> add cooldown for this IP
Optional Enhancements
- Configurable response timeout
- Custom confirmation keywords (
yes/no, y/n, etc.)
- Config flag to enable/disable the feature
- Logging of attempts and outcomes
Current transfer process relies on IP-based matching between TS3 and TS6 clients. While convenient, this approach can be unsafe in shared-network environments, where multiple users may appear under the same public IP.
This proposal introduces an additional authorization step: a confirmation request sent via private message to the detected TS3 client before allowing the rank transfer to proceed.
Proposed Solution
Introduce an optional verification step requiring explicit confirmation from the matched TS3 client.
Workflow
y→ proceed with transfernor no response (timeout) → abort transfer -> add cooldown for this IPOptional Enhancements
yes/no,y/n, etc.)