PrismarineJS / PrismarineJS/node-minecraft-protocol
Error: Failed to obtain profile data for X, does the account own minecraft?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
[ ] The FAQ doesn't contain a resolution to my issue
Versions
- minecraft-protocol: 1.47.0
- server: paper 1.19.4
- node: v18.17.1
Detailed description of a problem
Error: Failed to obtain profile data for redated@redated.com, does the account own minecraft?
at Object.authenticate (/redated/redatedt/node_modules/minecraft-protocol/src/client/microsoftAuth.js:31:40)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Using microsoft account to login after a few days of using the bot I get the error that the account doesn't own the game, the only temporary (and not 100% of the time) fix is deleting the .minecraft/npm-cache files, stoping and starting the script doesn't fix.
Additional context
Only happens on one of the accounts, the migrated/old one doesn't have that problem.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at src/client/microsoftAuth.js:31 and reproduce with minecraft-protocol 1.47.0, Node v18.17.1, and Paper 1.19.4, comparing the affected account with the working account. Check the reported .minecraft/npm-cache workaround; done means profile retrieval works reliably without manually deleting cache files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100