[BUG] Restaurant cannot choose fuel/food
Ruane001 opened this issue ยท 6 comments
Is there an existing issue for this?
- I have searched the existing issues
Are you using the latest MineColonies Verison?
- I am running the latest alpha version of MineColonies for my Minecraft version.
Did you check on the Wiki? or ask on Discord?
- I checked the MineColonies Wiki and made sure my issue is not covered there. Or I was sent from discord to open an issue here.
Minecraft Version
1.19.3
MineColonies Version
1.19.4-1.0.1342
Structurize Version
1.19.4-1.0.489
Related Mods and their Versions
Forge 45.0.29
blockuiu 1.19.4-0.0.73
Domum Ornamentum domum_ornamentum-1.19.4-1.0.88
Multi-Piston 1.19.3-1.2.26
Current Behavior
On the Fuel and food tabs there is only the black square to type. there is no list of items that can be chosen for use. ex. charcoal
Can't enter a fuel type so cook will constantly just ask for me to choose fuel. Even if given raw food and fuel, or cooked food they will not do anything. will not feed people.
Expected Behavior
Be able to select fuel types/food types. Should fix the cook just standing there doing nothing
Reproduction Steps
build restaurant
hire cook
check fuel tab
check food tab
Logs
https://gist.github.com/Ruane001/c9dd4f9e43f1586e518eabdb8030d89d
Anything else?
- Add a thumbs-up to the bug report if you are also affected. This helps the bug report become more visible to the team and doesn't clutter the comments.
- Add a comme
nt if you have any insights or background information that isn't already part of the conversation.
Similar problem yes, because the way minecraft allows doing it in 1.19.4 is flimsy
I'd just like to add that I have also this issue with the same mod versions.
I'm running with a personal dedicated server and the same happens if disconnected for a while. If I log in and it's empty, I have to disconnect and reconnect and it's fixed, until the next day that I reconnect, the same issue happens.
Try logging in to a single player game before you log into the server (just a simple log in/log out) cos it sounds like an old bug that was fixed in 1.18/1.19.2 and that was the easiest temporary solution! No guarantees, but it does sound like the same thing!