You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 12, 2019. It is now read-only.
Deck tracker does not work for you at all? There is an existing issue for this. Look over there, do not create a new issue.
Does it crash? Provide a full exception message or a screenshot and what exactly did you do right before that.
Some specific feature doesn't work as expected? Read a reporting problems section and provide debug logs.
In all cases, please provide a detailed step-by-step instructions on how to reproduce your issue. Nobody except you knows specifics of your computer and software you running on it. The less details you provide, the smaller is the chance that your report will be properly investigated.
The text was updated successfully, but these errors were encountered:
I play TESL a lot and now I have so many cards I can't keep track of them all. I want to upload my deck to your site, but I'm having the classical can't connect to 127.0.0.1 on port 50001 issue. I can't install the fix as it will mess up my Office I use for work. Any ideas? I've started the game and UDT as Admin. I've made exceptions in my firewall. I've uninstalled several times. I know you can't code for every software combination out there, and I appreciate your ambition and hard work. Thanks, if you can get this to working with Access Pro 2017 or other versions. It's a great tool!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How to report a bug
In all cases, please provide a detailed step-by-step instructions on how to reproduce your issue. Nobody except you knows specifics of your computer and software you running on it. The less details you provide, the smaller is the chance that your report will be properly investigated.
The text was updated successfully, but these errors were encountered: