AliaWaite

It is honestly impressive how such a tiny naming discrepancy can bring an entire project to a standstill without a single error message to point the way. That silent failure is probably the most frustrating part of Minecraft modding because the game assumes you intentionally pointed the blockstate toward a model that just happens to be missing. Your point about the registry name versus the file names is a classic trap that almost every developer falls into at least once. It is especially tricky because your brain tends to autocorrect the typos while you are proofreading the code, making the mismatch invisible until you step away for a bit. The fact that Forge or Fabric stays quiet about this is a double edged sword. While it keeps the logs clean, it leaves you hunting through folders for an hour just to realize you missed a single underscore or used a capital letter by mistake. Most people focus on the Java side of the registry and forget that the assets follow their own strict set of rules for the resource manager. Sharing this breakdown is definitely going to save someone from a lot of unnecessary stress. It serves as a great reminder that when the game logic works but the visuals fail, the answer is usually buried in a JSON path or a simple file name. Are you planning to add any special properties to this block now that the rendering is fixed, or was this just a simple decorative addition?