Login and Authentication Problems: Resetting and Managing Access

Many director headaches start at the login screen. Common symptoms include forgotten passwords, two-factor authentication failures, locked accounts, and staff members who can’t access admin features. First, have a clear account recovery policy: ensure the email tied to the director account is current and that at least two trusted staffers have owner or admin roles in TourneyKing to avoid a single point of failure. If a password reset link doesn’t arrive, verify spam folders and mail filters, and whitelist mail.tourneyking.com. If an organization uses SSO, coordinate with your identity provider (Google Workspace, Microsoft Azure AD) to check SAML/OAuth configurations; mismatches in redirect URIs or expired certificates are common culprits.

For two-factor issues, instruct users to check time synchronization on their authenticator app devices (a clock drift can invalidate codes). If an account is locked due to repeated failed attempts, use the emergency contact method or contact TourneyKing support with the account email and event details to expedite unlocking. Maintain a secondary admin account with 2FA configured but stored securely so multiple people can recover access if the primary admin is unavailable. For browser-related access problems, clear cookies and cache, try an incognito window, or switch to a supported browser (Chrome or Firefox are typically best). If staff report missing admin features, confirm their role in the event settings — role changes sometimes don’t propagate until the user logs out and back in. Finally, document your access procedures and run a test login before every event to catch issues early.

Event Setup Errors: Brackets, Divisions, and Scheduling Fixes

Incorrect brackets, mis-seeded players, or missing divisions are disruptive and often traced to data entry or configuration mistakes during event setup. Begin by double-checking your event template and rules before creating the live bracket. Use the preview or sandbox mode, if available, to simulate bracket generation. When seeding looks wrong, verify the seeding method selected (random, manual, ranking-based) and confirm that all participants were imported into the correct division and bracket size. Off-by-one errors commonly happen when import files have header rows or extra blank lines; validate CSV imports using a text editor to ensure the column headers match TourneyKing’s import schema.

For scheduling conflicts, use the built-in conflict detection tools and ensure your time zones are consistent — mismatched timezone settings between your organization profile and event configuration will shift match times. When swaps or late additions occur, leverage the bracket’s manual adjustment features: move players between slots and then run a consistency check (if provided) to ensure subsequent rounds update correctly. If a bracket becomes corrupted or rounds are misaligned after edits, export the current participant list and reimport into a new bracket to rebuild cleanly; most directors maintain a backup export before major edits.

Document special-case rules (e.g., byes, consolation rounds, double-elimination winners brackets) to avoid manual corrections during play. Finally, communicate clearly with players about bracket updates — a concise change log posted in the event’s announcement area reduces disputes and saves time.

Registration and Payment Issues: Tracking, Refunds, and Duplicate Entries

Handling registration and payment problems quickly preserves trust with players. Frequent issues include duplicate registrations, failed payments, chargebacks, and missing refunds. Start with a reconciled daily report: export your registration and payment CSVs from TourneyKing and cross-check them with your payment processor (Stripe, PayPal, etc.). For duplicates caused by multiple form submissions, use the participant email or unique player ID to identify and merge records. Many platforms allow you to mark duplicates and merge histories; if not, export, clean the data offline, and reimport or manually correct entries.

When payments fail or are pending, check the payment processor dashboard first — failed authorization, expired cards, or insufficient funds are common reasons. Set a cutoff policy for pending payments (e.g., reservation holds expire after 24-48 hours) and automate reminders. For refunds and chargebacks, follow both TourneyKing’s refund process and your payment processor’s requirements. Keep clear notes attached to the registration record stating reason and approval for refunds so volunteers can verify quickly at check-in. If a refund is authorized in the payment gateway but still shows as paid in TourneyKing, reconcile using the exported transaction IDs and request a manual status refresh or support intervention.

For large events, implement automated confirmation emails with payment receipts and registration summaries. That reduces confusion and provides a timestamp for disputes. Train staff on refund authority levels so approvals don’t bottleneck operations. Lastly, maintain a small contingency fund or a clear policy for late cancellations so you can respond consistently without financial surprises.

Real-time Scoring and Streaming Problems: Syncing, Overlays, and Latency

Real-time scoring and live streaming are where technical issues become very visible to participants and viewers. Common problems include delayed score updates, overlay mismatches, and poor stream quality. First, verify network stability: wired Ethernet connections are strongly preferred for PCs running scoring or OBS; Wi-Fi is acceptable only with enterprise-grade access points and strong signal. If score submissions are delayed, check for browser console errors, blocked WebSocket connections, or corporate firewalls blocking necessary ports. Many real-time features rely on persistent WebSocket connections; ensure these aren’t being terminated by aggressive firewall or proxy settings.

For overlays and stream graphics, ensure you’re using the latest version of the overlay instructions provided by TourneyKing and test them in a local OBS scene before going live. Mismatched scene resolution or incorrect browser source dimensions often cause stretched or cut-off graphics. If overlays fail to load, check that the overlay URL is correct and accessible from the streaming machine; local ad blockers or privacy extensions can prevent URL-based overlays from rendering. Use the browser source refresh feature or set OBS to refresh browser sources automatically when scenes switch.

Latency issues on streams often stem from encoder settings. Balance bitrate with resolution: on limited upload bandwidth, lower resolution (720p) at a reasonable bitrate will reduce buffering. Consider using hardware encoders (NVENC, AMF) to offload CPU. If viewers report score discrepancies, confirm that the scoring PC’s clock is synchronized with NTP — timestamp mismatches can cause out-of-order updates. When integrating volunteer-run score inputs, use a single point-of-truth interface and restrict direct edits to trained staff to prevent conflicting updates. In persistent or complex cases, capture logs from the scoring machine and OBS, then submit them to TourneyKing support with exact timestamps and reproducer steps so engineers can diagnose connection or API issues.

Bolabet Glory