Thanks for getting back to me!
I'm actually at a loss for what could be causing this. Would you mind sending me the error log?
You can find it at:
~/Library/Logs/Fishlicka/Juice Galaxy/Player.log
and send it to:
JuiceGalaxyBugs@gmail.com
to access the Library folder, you may have to hold the Option key while using the Go menu in Finder.
I've uploaded a test build that may fix this issue--
If you wouldn't mind running it and letting me know if it works, I'd appreciate it!
https://fishlicka.itch.io/juice-galaxy-test / password: plswork
When I clicked on the link, I couldn't download the test build and there is an error.
Error.JSON:RPC error 12000: itch.io API error (400):/games/623823: invalid game
Edit: figured I should try online instead of app, I could download it and opened it.
The menu is still invisible, I will send you the errorlog.
Let me know if you need anything else, also I am wondering if something is wrong with my mac.
Edit-2: Having trouble finding error log.
It's alright, I don't need the error log anymore.
Darn, I was really confident I'd fixed it. I changed a lot with the main menu last update, so I was kind of expecting there to be new issues. There have been other reports of issues with the GUI, so hopefully I can figure it out soon.
I will give this another shot within the next couple days, thank you for getting back to me so quickly!
All right, one more try if you don't mind!
I've upgraded from Unity 2019 to Unity 2021, and fiddled with the menu system a bit more. If this doesn't fix it, idk what will.
The link to the test build is the same as before:
https://fishlicka.itch.io/juice-galaxy-test / password: plswork
Sure! You can install an older version using the itch.io app and most likely one of them will work.
1. Install itch.io app here: Download App - itch.io
2. Install Juice Galaxy
3. Right click the game and select 'Manage'
4. Click the 'Manage' button that appears (redundant I know)
5. Click 'Switch to another version...'
I'd recommend trying the oldest first just to ensure that it works, and then working your way up. This issue was first reported during update 0.2.3, so I'll bet 0.2.2 will work. Best of luck and if you get a version to work, let me know so I can have more of a clue how to fix this pesky bug.
