![]() ![]() But where this happens and how it works is a mystery to me. Since these methods have seemingly no logic in them for deciding which blocks to render, that gives me a suspicion that Sodium might make that decision somewhere else, before any of these methods are called. It could still cancel these methods, but it can't force them to render their block. +40 Geo damage bonus for 10 seconds after To become op, you. Step 2 and 3 have become pretty useless for X-Ray. hack a minecraft seUSE OP TOOL - Minecraft OP Forcer. So far I haven't been able to figure out what step 1 gets replaced with, I only know that the original BlockRenderManager.renderBlock() doesn't get called anymore. BlockModelRenderer.renderQuad() (also doesn't have boolean cull)Īs you can see, that seemingly leaves zero options for where to put the X-Ray logic.modified version of BlockModelRenderer.render() that doesn't have boolean cull.Now this is what happens if Sodium is installed: Currently X-Ray uses renderSmooth() / renderFlat(), but the other two would work just as well. In vanilla, that gives me three options for where to place the X-Ray logic. It does this by simply cancelling the method call. The other thing that X-Ray needs to do is to hide all of the non-ore blocks that would normally be rendered. ![]() This is how X-Ray can show ores that would normally be hidden. either BlockModelRenderer.renderSmooth() or BlockModelRenderer.renderFlat()Įach of these methods have a boolean cull parameter that, if set to false, causes the block to be rendered even when it's behind other blocks.Normally, when Minecraft decides whether or not to render a block, it calls the following methods in order: X-Ray works by overwriting Minecraft's decision of which blocks to render and which blocks to hide. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |