-
-
Notifications
You must be signed in to change notification settings - Fork 940
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
writeBook() function seems to be buggy/broken #3204
Comments
So I have downgraded to version 1.16 and it appears to work, I suppose this is just an issue with 1.19.3 not being supported yet. |
dont leave us hanging |
can confirm in 1.20.1 |
I have this error on 1.20.2 |
Tested in 1.20 as well using the provided book.js example verbatim. The bot disconnects and I get the below pasted error in the console. I'm trying to fill chiseled bookcase library with all of the books from Skyrim, but unfortunately my project is blocked by this. I hope it can be prioritized by the maintainers.
|
* Added support for new edit book packet (#3204) * Ran linter * Pass the slot to editBook * Change slot to different parameter to work with old hand value * Update book.js use new feature --------- Co-authored-by: extremeheat <extreme@protonmail.ch>
Versions
Detailed description of a problem
When utilizing the writeBook API call, an error message seems to pop up that happens regardless of the pages I input. The current code is here:
The error message that always pops up is this:
What did you try yet?
Looking at the error messages, it does not seem to be linked to anything in my code. However, I tried anyway, thinking this may have happened too deep in the code for it to print out.
The following is what I have tried, all of which have failed to solve the problem:
[]
instead of the function, so that it would bewriteBook(book.slot, [])
.["abcdefg"]
)book.slot
but instead used some other test slot that I knew would be empty during my testing. This produced a more sane error that did go into the catch statement, but it did tell me that I was indeed correct with my usage ofbook.slot
It is also worth mentioning that it is certain
book
is an actual item in the inventory, and the pages array is indeed an array of strings.Expected behavior
I expected for the book to be written and for the code to continue as usual, or for it to atleast enter the catch portion like a normal error.
The text was updated successfully, but these errors were encountered: