-
Notifications
You must be signed in to change notification settings - Fork 9
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
Few remaining issues at v1.0.0 #1
Comments
@Cervator: I can't seem to able to replicate any of the issues you mentioned. I've looked at the code and tested it out and the page turning appears to work as expected. The current page resets on close and there's no crash of any sort when leaving one book on the last page and opening another. I also didn't face the issue where the click sound was played, but the bookcase didn't open. Instead, I'm actually facing the issue where As with chests, a reliable way of replicating this issue is opening the bookcase and then closing it using How strange... I'm very curious as to what changes were made that caused this issue to resurface since you mentioned that you managed to fix this issue before. I'll try to look into this. |
Oh I just noticed @Waterpicker submitted another commit 3 days after I entered that issue. So if it is fixed then cool! That's one item out of the way :-) I think the click eating issue has two sides to it
|
@Cervator Just saw your comment right after I submitted a PR for it in the main repo 🙂. This should mean that all the issues here are fixed. |
Awesome, thanks! Checking back in later, leaving the house for a while now |
Closing as complete :-) |
Did some testing! Still a few issues to look for
e
clicks. Try placing a chest when you spawn, without even having requested any book-related stuff via console. Firste
click does nothing (almost like it is being caught by something else / consumed early) then the second click opens the cheste
click issue?~~~Quite possibly some of these predate the recent overhaul by @Waterpicker. I just fixed a JSON formatting issue and put
-SNAPSHOT
back on the version number in module.txt (source should always be SNAPSHOT and Jenkins / release management handles the non-snaphots, lest things go boom). Also fixed some tabs -> spaces and a waaay outdated "craftPlace" thingActually, that appears to have fixed the
e
eating. Yay! I fixed something :-)Crash log:
The text was updated successfully, but these errors were encountered: