Dubtrackr: Reliability Fixes I'm Prioritizing

I've identified several issues affecting Dubtrackr's reliability, particularly with Fortnite connections, screen reading, and session tracking. I'm making these fixes a priority before moving on to additional features.

I want to be transparent about what's happening and what I'm working on.

I'm a team of one, and I'm learning a lot of this as I go. I won't get everything right the first time. I know these problems affect your experience, and it's my responsibility to fix them and be clear about where things stand.

🔌 Fortnite Connection & Position Detection

I've found a major issue where Dubtrackr fails to reconnect to Fortnite's position data after the game restarts. This can leave players stuck in a loop of restart and rejoin instructions.

I'm also fixing:

• Incorrect alerts claiming Dubtrackr was opened after Fortnite.
• Outdated position data being carried into a new island visit.
• Restart instructions appearing in the lobby.
• "Join the island" prompts appearing when you're already there.

📊 Screen Reading & Accuracy

I want you to be able to trust the numbers Dubtrackr displays.

• Readings will show how recently they were updated.
• Dubtrackr will notify you in-game when it can't see your resource bar.
• Crashes affecting 4K users are being addressed.
• Black screen captures will no longer be treated as successful readings.
• Readers will no longer get stuck on "Reading" indefinitely.

🔔 Alerts & Window Behavior

Alerts should be helpful without interrupting your game.

• Critical alerts will be easier to see, even with the message center hidden.
• Instructions will match the actual buttons and options you see.
• Alerts will no longer blink.
• Dubtrackr will stop popping in front of Fortnite when you join an island or return to the game.

📈 Sessions & Data Consistency

I'm also correcting several issues with session tracking:

• Home and Sessions will display consistent session times.
• Older sessions recorded before your most recent PC link will be restored.
• Droidex additions will be counted correctly.
• Session reports will explain why resources couldn't be read, such as when the Nova Shop blocks the resource bar.

What's Next?

These are active priorities, not fixes that have already been released.

Some of these issues were identified in the first few 1.7.2 installations, and I'm treating them seriously. My focus right now is making Dubtrackr more dependable, keeping its information accurate, and making sure its instructions actually help you resolve problems.

Thank you to everyone reporting bugs, sharing screenshots, and providing feedback. Your reports are helping me find and address issues faster.

You should be able to trust what Dubtrackr tells you. That's the standard I'm working toward.