Jump to content

Recommended Posts

Posted

is there a way to control what an .obj model looks like in inventory?   all the .json dislay; GUI, firstperson etc  are in the .json model.  No way to put them into the .obj model

Posted

JSON models can point to *other* models....

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Posted

I tried :

      blockstate (partial) :

           "facing=north,style=s0": {"model": "yabm:yb_INT_slope", "y": 90 },

 

    yb_INT__slope :

{
    "parent": "yabm:block/wedge.obj",
    "textures": {
            "#Material1": "blocks/stonebrick",
            "#particle": "blocks/stonebrick"
    }
}

 

I get an error :

java.lang.IllegalStateException: vanilla model 'net.minecraft.client.renderer.block.model.ModelBlock@62cf8fda' can't have non-vanilla parent

 

not sure what to do, is there something else beside "parent" ?

Posted
On 4/14/2018 at 12:20 AM, Draco18s said:

JSON models can point to *other* models....

I was hoping 1.12   would help, but i still get the net.minecraft.client.renderer.block.model.ModelBlock@6dd1e22' can't have non-vanilla parent error

 

if i can't use "parent" how can i point to a diferent model

Posted (edited)

You can specify item transformations using Forge's blockstates format, but this requires them to be specified as TRSRTransformations (or one of Forge's built-in transformations: "forge:default-block", "forge:default-item" and "forge:default-tool") rather than the Vanilla ItemTransformVec3f format.

 

I explain how to do this here.

Edited by Choonster

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Posted

this almost works

{
	"forge_marker": 1,
	"variants":	{
	
    "facing=north,style=s0":{
        "model": "yabm:wedge.obj", "textures":{
            "#Material1": "blocks/stonebrick",
            "#particle": "blocks/stonebrick"},
        "y": 90,   
        "transform":{
            "gui":{
                "scale": [0.6 , 0.6, 0.6]
             }
        },                
        "custom": { "flip-v": true },	
        "uvlock": true
    },
...

 

except when the model is placed it  ignores the :y: 90.  I have also tried having the y: 90 in the model statement

"model": "yabm:wedge.obj" , "y": 90 , "textures":{

 

no difference the rotation is ignored

Posted

found it, put the model rotation inside the transform block

{
	"forge_marker": 1,
	"variants":	{
	
    "facing=south,style=s0":{
        "model": "yabm:wedge.obj", "textures":{
            "#Material1": "blocks/stonebrick",
            "#particle": "blocks/stonebrick"},
  
        "transform":{
            "gui":{
                "scale": [0.6 , 0.6, 0.6]
             },
             "rotation": [ {"y": 180} ]   //ROTATES THE MODEL
        },                
        "custom": { "flip-v": true },	
        "uvlock": true
        
    },

thanks for you help

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.