Skip to content
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

1.12.2 Failed to open blockstate #87

Open
Stapleton opened this issue Sep 19, 2023 · 1 comment
Open

1.12.2 Failed to open blockstate #87

Stapleton opened this issue Sep 19, 2023 · 1 comment

Comments

@Stapleton
Copy link

Stapleton commented Sep 19, 2023

OS: Windows 10 Pro 19045.3324
Launcher: Multicraft Daemon
Modpack: Project Ozone 3 3.4.11F
Dynmap: Dynmap-3.6-forge-1.12.2.jar
DynmapBlockScan: DynmapBlockScan-3.6-forge-1.12.2.jar

First launch crashed the server since Dynmap does its usual thing of taking a really long time to process everything and causes the watchdog to kill it. I set max-tick-time to -1 in server.properties and started again. Second time was a successful boot. However both times i got a whole lot of the following

  • Invalid modellist patch for box X/X/X:X/X/X side X at line X
  • Failed to open blockstate
  • modelID=dynmapblockscan:block/forgemodelXXXXX has parent=modid:block/name.obj but no parentModel

Heres both latest.log and debug.log

Referencing: webbukkit/dynmap#2264, #86

@Stapleton
Copy link
Author

Stapleton commented Sep 28, 2023

Update with a clean client.

Launcher: GDLauncher
Minecraft: 1.12.2
Forge: 14.23.5.2860
Dynmap: 3.6
DynmapBlockScan: 3.7 Snapshot

Heres the latest.log

The errors given is now just one, which is

  • Failed to open blockstate

An interesting thing is that it also fails to open the vanilla concrete and concrete powder blockstates.
I will do some sleuthing and figure out if theres some sort of difference between the working and failing blockstates, using vanilla concrete and concrete powder as the control group. This can let me isolate what the concrete blockstates are doing different from the other vanilla blockstates. With that difference isolated, i can then use it to validate why the chisel blockstates are not working. Hopefully this will lead me to a proper answer to this issue.

Will update with more!

EDIT: Discovered that the erroring vanilla blockstates dont exist. Still gonna look around for possible solutions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant