Jump to content

Recommended Posts

Posted

 Hi,

in the documentation of forge (1.16.x) I've found this quote:

"If you are placing a Block, call Block#getDefaultState() to get the “default” state(...)"

Now when I try to use code such as below:

BlockState newBlockState = Blocks.DIRT.getDefaultState();

I get this error:

/home/poison64/dev/mc-forge/first/src/main/java/com/example/examplemod/MyModEventHandler.java:23: error: cannot find symbol
        BlockState newBlockState = Blocks.DIRT.getDefaultState();
                                              ^
  symbol:   method getDefaultState()
  location: variable DIRT of type Block
1 error

Is the documentation wrong or I just don't know something?

I've played around with other stuff, and they work just fine, for example, this one works as expected:

    @SubscribeEvent
    public void pickupItem(EntityItemPickupEvent event) {
        ItemStack stack = event.getItem().getItem();
        stack.setCount(stack.getCount()*2);         
    }

 

  • 1 year later...
Posted
On 4/4/2021 at 12:06 PM, diesieben07 said:

Most documentation has not been updated for the recent switch to Mojang names. The method is now called defaultBlockState.

Please help, how called method .with

public class RotateBlockModel extends HorizontalBlock {
    public RotateBlockModel(Properties builder) {
        super(builder);
    }
    
    public void fillStateContainer(StateContainer.Builder<Block, BlockState> builder){
        builder.add(FACING);
    }

    @Nullable
    @Override
    public BlockState getStateForPlacement(BlockItemUseContext context) {
        return this.getBlock().defaultBlockState().with;
    }
}
C:\Users\������\OneDrive\������� ����\����\mod\src\main\java\com\dipcrai\mymod\block\custom\RotateBlockModel.java:23: error: cannot find symbol
        return this.getBlock().defaultBlockState().with();
                                                  ^

 

  • Guest locked this topic
Guest
This topic is now closed to further replies.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Hello, Recently I have been hosting an RLcraft server on Minecraft Forge Version 1.12.2 - 14.23.5.2860 I originally had lag issues and I chalked it up to playing on less than perfect hardware so I moved the server to better hardware(i9-9900k with 64GB of RAM for 1 player.) After lots of troubleshooting I discovered a couple of things. World saving was causing the MSPT to spike to over 2000Miliseconds and was happening every minute. This kind of makes sense as the world was pre-generated and is over 100GB. I learned that I could turn off world saving and just schedule that and that resolved that issue. After that issue was resolved I discovered another issue. It appears that when exploring chunks, any chunks explored stay loaded. They persist. I was originally thinking that this had to be a mod issue, but it didn't seem like anyone was talking about it. This isn't really a problem on packs with few worldgen mods or just few mods in general, but on beefier packs it becomes a problem. I went through forge changelogs and found this line. Build: 1.12.2-14.23.5.2841 - Thu Aug 29 01:58:50 GMT 2019 bs2609: Improve performance of persistent chunk checks (#5706) Is this a related item to what I am dealing with or just something else?   I went ahead and created a new dedicated server with Just Forge 14.23.5.2860, spark reforged, and it's core mods. I was able to replicate the issue and log it with spark. Hopefully you're able to see this spark profile. It basically shows that as I explored the chunk loading persisted(2000 chunks loaded over 10 minutes with one player)The view distance is set to 10 so that should be 200 chunks per player. If I don't move the loaded chunks are 200. I was however able to fix the persistent chunk issue if I save the world more frequently. My question is, is this intended function of the game or is this a bug? Everywhere I read seems to indicate Minecraft servers save every 5 minutes and not every minute. Can chunks not unload if the world does not autosave. Additionally. Autosave specifically appears to fix this issue. Manually running save-all does not resolve the issue.   I realize this is kind of a log one, sorry. Please let me know if you require further information. Thanks in advance for your time. https://spark.lucko.me/NvlMtC39Yt https://imgur.com/a/K0oyukx https://pastebin.com/z0qGu1Vh  
    • Thank you so much, I had originally tried to allocate 16 gb of ram but still had the same issue with the lag, 12 was perfect.
    • Something related to shaders - check the config file of this mod - maybe you can disable shaders there
    • Add -Dfml.earlyprogresswindow=false to your JVM args
  • Topics

×
×
  • Create New...

Important Information

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