Jump to content

[1.8] Tile entity sometimes null


SnowyEgret

Recommended Posts

I have a block which provides a tile entity and is rendered by an ISmartBlockModel.

 

Method handleBlockState() is overidden to lookup a model given an IBlockState which is read from an unlisted property which is in turn set from a field on the block's tile entity. This is all based on TheGreyGhost's Minecraft by Example MBE04, and works fine, most of the time.

 

Here is my block:

 

public class BlockSelected extends Block implements ITileEntityProvider {

public static final PrevStateProperty prevStateProperty = new PrevStateProperty();

public BlockSelected() {
	super(Material.clay);
}

@Override
public boolean isOpaqueCube() {
	return false;
}

@SideOnly(Side.CLIENT)
public EnumWorldBlockLayer getBlockLayer() {
	return EnumWorldBlockLayer.CUTOUT_MIPPED;
}

@Override
protected BlockState createBlockState() {
	return new ExtendedBlockState(this, new IProperty[0], new IUnlistedProperty[] { prevStateProperty });
}

@Override
public IBlockState getExtendedState(IBlockState state, IBlockAccess world, BlockPos pos) {
	PrevStateTileEntity tileEntity = (PrevStateTileEntity) world.getTileEntity(pos);
	IBlockState prevState = null;
	if (tileEntity != null) {
		prevState = tileEntity.getPrevState();
	} else {
		System.out.println("tileEntity=" + tileEntity);
	}
	return ((IExtendedBlockState) state).withProperty(prevStateProperty, prevState);
}

@Override
public TileEntity createNewTileEntity(World worldIn, int meta) {
	return new PrevStateTileEntity();
}

}

 

and here is the ISmartBlockModel's relevent code:

 

public class BlockSelectedModel implements ISmartBlockModel {

private IBakedModel model;

@Override
public IBakedModel handleBlockState(IBlockState state) {
	IBlockState s = ((IExtendedBlockState) state).getValue(BlockSelected.prevStateProperty);
	model = Minecraft.getMinecraft().getBlockRendererDispatcher().getBlockModelShapes().getModelForState(s);
	return this;
}
}

 

Here is my tile entity with its IBlockState field:

 

public class PrevStateTileEntity extends TileEntity {

private IBlockState prevState;
private final String PREV_STATE_KEY = "b";

public IBlockState getPrevState() {
	return prevState;
}

public void setPrevState(IBlockState state) {
	prevState = state;
}

@Override
public void writeToNBT(NBTTagCompound tag) {
	tag.setInteger(PREV_STATE_KEY, Block.getStateId(prevState));
	super.writeToNBT(tag);
}

@Override
public void readFromNBT(NBTTagCompound tag) {
	prevState = Block.getStateById(tag.getInteger(PREV_STATE_KEY));
	super.readFromNBT(tag);
}

@Override
public Packet getDescriptionPacket() {
	NBTTagCompound tag = new NBTTagCompound();
	writeToNBT(tag);
	super.writeToNBT(tag);
	return new S35PacketUpdateTileEntity(pos, this.getBlockMetadata(), tag);
}

@Override
public void onDataPacket(NetworkManager net, S35PacketUpdateTileEntity pkt) {
	readFromNBT(pkt.getNbtCompound());
	super.readFromNBT(pkt.getNbtCompound());
}

}

 

I am placing the block in the world like this:

 

	world.setBlockState(pos, state, 1);
	world.markBlockForUpdate(pos);
	PrevStateTileEntity tileEntity = (PrevStateTileEntity) world.getTileEntity(pos);
	tileEntity.setPrevState(prevState);

 

The problem occurs when the tile entity in getExtendedState() occasionally comes up null during rendering. Without the tile entity, I can not set the unlisted property and the block can't render. This always happens when I set a range of blocks, and then set another adjacent range. The first range renders properly after being set, but then their tile entities come back null after the adjacent range is set. I know the tile entity is null, because I get the println in getExtendedState().

 

If I set the first range, then walk away into another chunk before coming back and setting the second range, things are ok, and world.getTileEntity(pos) comes back with a valid tile entity.

 

Here is an image of the problem. The outermost ring of blocks are the new setBlockStates. The inner blocks were rendering properly before the outer ring was added. I am guessing they cross a chunk boundary which would explain why some of the inner ones are rendering properly:

 

width=701 height=4702pjOA5N.png?1 [/img]

 

 

Link to comment
Share on other sites

I can't remember why, but i got in the habit of a null check anytime I grab and instance of a tile.

 

If it only happens in a rare tick, skipping the render for the null isn't going to matter much.

 

 

On your end, have you tried error trapping it or using the debug to see what is going on? 

Long time Bukkit & Forge Programmer

Happy to try and help

Link to comment
Share on other sites

I have placed this line with a breakpoint after the test for a null tile entity (just gets the tile entity again)

 

		
world.getTileEntity(pos);

 

it takes me here in class RegionRenderCache:

 

		
    public TileEntity getTileEntity(BlockPos pos)
    {
        int i = (pos.getX() >> 4) - this.chunkX;
        int j = (pos.getZ() >> 4) - this.chunkZ;
        return this.chunkArray[i][j].getTileEntity(pos, Chunk.EnumCreateEntityType.QUEUED);
    }

 

to here in class Chunk:

    public TileEntity getTileEntity(BlockPos pos, Chunk.EnumCreateEntityType p_177424_2_)
    {
        TileEntity tileentity = (TileEntity)this.chunkTileEntityMap.get(pos);

        if (tileentity != null && tileentity.isInvalid())
        {
            chunkTileEntityMap.remove(pos);
            tileentity = null;
        }

        if (tileentity == null)
        {
            if (p_177424_2_ == Chunk.EnumCreateEntityType.IMMEDIATE)
            {
                tileentity = this.createNewTileEntity(pos);
                this.worldObj.setTileEntity(pos, tileentity);
            }
            else if (p_177424_2_ == Chunk.EnumCreateEntityType.QUEUED)
            {
                this.field_177447_w.add(pos);
            }
        }

        return tileentity;
    }

 

tileentity comes back null from chunkTileEntityMap then when p_177424_2_ == Chunk.EnumCreateEntityType.QUEUED, the position is added to field_177447_w which is of type ConcurrentLinkedQueue.

 

 

Link to comment
Share on other sites

Something looks odd with your tile entity, but I don't have access to anything right now, so can't figure it out.

 

Why are you doing this?

 

 

world.setBlockState(pos, state, 1);

world.markBlockForUpdate(pos);

PrevStateTileEntity tileEntity = (PrevStateTileEntity) world.getTileEntity(pos);

tileEntity.setPrevState(prevState);

 

 

 

Did you get that from someone as an example?

 

 

 

Long time Bukkit & Forge Programmer

Happy to try and help

Link to comment
Share on other sites

After I set my block (BTW, world.setBlock(pos, state, 3) without marking the position for update seems to behave identically) I need to set field prevState (type IBlockState) on the tile entity. When the tile entity is created by my block, field prevState is uninitialized:

 

@Override
public TileEntity createNewTileEntity(World worldIn, int meta) {
	return new PrevStateTileEntity();
}

 

 

 

Link to comment
Share on other sites

I'm going to have to let someone else chime in that has set a block/tile in 1.8 via java.  I have working blocks, but I'm always setting them with the player.

Long time Bukkit & Forge Programmer

Happy to try and help

Link to comment
Share on other sites

Something else that may be relevant. I sometimes get this warning in the console when the tile entity is coming up null:

 

[12:47:43] [Client thread/WARN]: Needed to grow BufferBuilder buffer: Old size 524288 bytes, new size 2621440 bytes.

 

Does anyone know which class is printing this warning?

Link to comment
Share on other sites

Ok, I have found a fix for my problem, but I have no idea of it's consequences, nor do I understand why it's working. Poking around in Chunk.setBlockState() I came across this block of code which removes tile entities:

 

                if (!this.worldObj.isRemote)
                {
                    if (iblockstate1.getBlock() != state.getBlock()) //Only fire block breaks when the block changes.
                    block1.breakBlock(this.worldObj, pos, iblockstate1);
                    TileEntity te = this.getTileEntity(pos, Chunk.EnumCreateEntityType.CHECK);
                    if (te != null && te.shouldRefresh(this.worldObj, pos, iblockstate1, state)) this.worldObj.removeTileEntity(pos);
                }
                else if (block1.hasTileEntity(iblockstate1))
                {
                    TileEntity te = this.getTileEntity(pos, Chunk.EnumCreateEntityType.CHECK);
                    if (te != null && te.shouldRefresh(this.worldObj, pos, iblockstate1, state))
                    this.worldObj.removeTileEntity(pos);
                }

 

TileEntity.shouldRefresh() looks like this:

 

    /**
     * Called from Chunk.setBlockIDWithMetadata, determines if this tile entity should be re-created when the ID, or Metadata changes.
     * Use with caution as this will leave straggler TileEntities, or create conflicts with other TileEntities if not used properly.
     *
     * @param world Current world
     * @param pos Tile's world position
     * @param oldID The old ID of the block
     * @param newID The new ID of the block (May be the same)
     * @return True to remove the old tile entity, false to keep it in tact {and create a new one if the new values specify to}
     */
    public boolean shouldRefresh(World world, BlockPos pos, IBlockState oldState, IBlockState newSate)
    {
        return !isVanilla || (oldState.getBlock() != newSate.getBlock());
    }

 

In my tile entity class I have overidden it leaving out the test for isVanilla:

 

@Override
public boolean shouldRefresh(World world, BlockPos pos, IBlockState oldState, IBlockState newSate) {
	return oldState.getBlock() != newSate.getBlock();
}

 

and my problem (and it has been a problem for weeks - I have tried everything) has gone away. :)

 

Please, if anyone has some insight, please share it. I am wary of the caution in the javadoc comment.

 

Link to comment
Share on other sites

I put these printlns in my tile entity's shouldRefresh():

 

@Override
public boolean shouldRefresh(World world, BlockPos pos, IBlockState oldState, IBlockState newSate) {
	System.out.println("oldState="+oldState);
	System.out.println("newSate="+newSate);
	new Throwable().printStackTrace();
	return oldState.getBlock() != newSate.getBlock();
}

 

and get this in the console:

 

[16:26:44] [Client thread/INFO] [sTDOUT]: [org.snowyegret.mojo.block.PrevStateTileEntity:shouldRefresh:30]: oldState=mojo:block_selected
[16:26:44] [Client thread/INFO] [sTDOUT]: [org.snowyegret.mojo.block.PrevStateTileEntity:shouldRefresh:31]: newSate=mojo:block_selected
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: java.lang.Throwable
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at org.snowyegret.mojo.block.PrevStateTileEntity.shouldRefresh(PrevStateTileEntity.java:32)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraft.world.chunk.Chunk.fillChunk(Chunk.java:1425)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraft.client.network.NetHandlerPlayClient.handleChunkData(NetHandlerPlayClient.java:763)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraft.network.play.server.S21PacketChunkData.processPacket(S21PacketChunkData.java:64)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraft.network.play.server.S21PacketChunkData.processPacket(S21PacketChunkData.java:152)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraft.network.PacketThreadUtil$1.run(PacketThreadUtil.java:24)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraftforge.fml.common.FMLCommonHandler.callFuture(FMLCommonHandler.java:714)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraft.client.Minecraft.runGameLoop(Minecraft.java:1078)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraft.client.Minecraft.run(Minecraft.java:376)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraft.client.main.Main.main(Main.java:117)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at java.lang.reflect.Method.invoke(Method.java:497)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
[16:26:44] [Client thread/INFO] [sTDERR]: [java.lang.Throwable$WrappedPrintStream:println:748]: 	at net.minecraft.launchwrapper.Launch.main(Launch.java:28)

 

As it turns out, it is this block of code in Chunk.fillChunk() that is calling shouldRefresh():

 

        while (iterator.hasNext())
        {
            TileEntity tileentity = (TileEntity)iterator.next();
            if (tileentity.shouldRefresh(this.worldObj, tileentity.getPos(), tileentity.getBlockType().getStateFromMeta(tileentity.getBlockMetadata()), getBlockState(tileentity.getPos())))
                invalidList.add(tileentity);
            tileentity.updateContainingBlockInfo();
        }

        for (TileEntity te : invalidList) te.invalidate();

 

This must be where minecraft performs a sort of garbage collection by invalidating tile entities which are no longer "referenced" by a block at that position. When the block changes to one that has no new tile entity to overwite it, you don't want it left in the world. I am not sure why this decision is delegated to the tile entity, and why its default implementation returns true if the tile entity is not vanilla (from class TileEntity):

    private boolean isVanilla = getClass().getName().startsWith("net.minecraft.");

 

but my guess is that the I should be keeping the check for oldState.getBlock() != newSate.getBlock() or I will be populating the world with unused tile entities.

Link to comment
Share on other sites

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.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
    • When I came across the 'Exit Code: I got a 1 error in my Minecraft mods, so I decided to figure out what was wrong. First, I took a look at the logs. In the mods folder (usually where you'd find logs or crash reports), I found the latest.log file or the corresponding crash report. I read it through carefully, looking for any lines with errors or warnings. Then I checked the Minecraft Forge support site, where you can often find info on what causes errors and how to fix them. I then disabled half of my mods and tried running the game. If the error disappeared, it meant that the problem was with the disabled mod. I repeated this several times to find the problem mod.
    • I have no idea - switch to a pre-configured modpack and use it as working base    
  • Topics

  • Who's Online (See full list)

×
×
  • Create New...

Important Information

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